Execute tasks from a track's implementation plan following TDD workflow
npxskills add sickn33/antigravity-awesome-skills--skill conductor-implementLoading…
Execute tasks from a track's implementation plan, following the workflow rules defined in conductor/workflow.md.
resources/implementation-playbook.md.Verify Conductor is initialized:
conductor/product.md existsconductor/workflow.md existsconductor/tracks.md exists/conductor:setup firstLoad workflow configuration:
conductor/workflow.mdconductor/tracks/{argument}/plan.mdRead conductor/tracks.md
Parse for incomplete tracks (status [ ] or [~])
Display selection menu:
Select a track to implement:
In Progress:
1. [~] auth_20250115 - User Authentication (Phase 2, Task 3)
Pending:
2. [ ] nav-fix_20250114 - Navigation Bug Fix
3. [ ] dashboard_20250113 - Dashboard Feature
Enter number or track ID:
Load all relevant context for implementation:
Track documents:
conductor/tracks/{trackId}/spec.md - Requirementsconductor/tracks/{trackId}/plan.md - Task listconductor/tracks/{trackId}/metadata.json - Progress stateProject context:
conductor/product.md - Product understandingconductor/tech-stack.md - Technical constraintsconductor/workflow.md - Process rulesCode style (if exists):
conductor/code_styleguides/{language}.mdUpdate track to in-progress:
In conductor/tracks.md:
[ ] to [~] for this trackIn conductor/tracks/{trackId}/metadata.json:
status: "in_progress"updated timestampFor each incomplete task in plan.md (marked with [ ]):
Parse plan.md to find next incomplete task:
- [ ] Task X.Y: {description}Mark task as in-progress:
[ ] to [~] for current taskRed Phase - Write Failing Test:
Following TDD workflow for Task X.Y...
Step 1: Writing failing test
Green Phase - Implement:
Step 2: Implementing minimal code to pass test
Refactor Phase:
Step 3: Refactoring while keeping tests green
Commit changes (following commit strategy from workflow.md):
git add -A
git commit -m "{commit_prefix}: {task description} ({trackId})"
Update plan.md:
[~] to [x] for completed taskgit add conductor/tracks/{trackId}/plan.md
git commit -m "chore: mark task X.Y complete ({trackId})"
Update metadata.json:
tasks.completedupdated timestampAfter each task, check if phase is complete:
[x]:Run phase verification:
Phase {N} complete. Running verification...
npm test / pytest / etc.Report and wait for approval:
Phase {N} Verification Results:
- All phase tasks: Complete
- Tests: {passing/failing}
- Verification: {pass/fail}
Approve to continue to Phase {N+1}?
1. Yes, continue
2. No, there are issues to fix
3. Pause implementation
CRITICAL: Wait for explicit user approval before proceeding to next phase.
ERROR: {tool} failed with: {error message}
Options:
1. Retry the operation
2. Skip this task and continue
3. Pause implementation
4. Revert current task changes
TESTS FAILING after Task X.Y
Failed tests:
- {test name}: {failure reason}
Options:
1. Attempt to fix
2. Rollback task changes
3. Pause for manual intervention
GIT ERROR: {error message}
This may indicate:
- Uncommitted changes from outside Conductor
- Merge conflicts
- Permission issues
Options:
1. Show git status
2. Attempt to resolve
3. Pause for manual intervention
When all phases and tasks are complete:
All tasks complete. Running final verification...
In conductor/tracks.md:
[~] to [x] for this trackIn conductor/tracks/{trackId}/metadata.json:
status: "complete"phases.completed to totaltasks.completed to totalupdated timestampIn conductor/tracks/{trackId}/plan.md:
[x] CompleteTrack complete! Would you like to sync documentation?
This will update:
- conductor/product.md (if new features added)
- conductor/tech-stack.md (if new dependencies added)
- README.md (if applicable)
1. Yes, sync documentation
2. No, skip
Track {trackId} is complete.
Cleanup options:
1. Archive - Move to conductor/tracks/_archive/
2. Delete - Remove track directory
3. Keep - Leave as-is
Track Complete: {track title}
Summary:
- Track ID: {trackId}
- Phases completed: {N}/{N}
- Tasks completed: {M}/{M}
- Commits created: {count}
- Tests: All passing
Next steps:
- Run /conductor:status to see project progress
- Run /conductor:new-track for next feature
Maintain progress in metadata.json throughout:
{
"id": "auth_20250115",
"title": "User Authentication",
"type": "feature",
"status": "in_progress",
"created": "2025-01-15T10:00:00Z",
"updated": "2025-01-15T14:30:00Z",
"current_phase": 2,
"current_task": "2.3",
"phases": {
"total": 3,
"completed": 1
},
"tasks": {
"total": 12,
"completed": 7
},
"commits": [
"abc1234: feat: add login form (auth_20250115)",
"def5678: feat: add password validation (auth_20250115)"
]
}
If implementation is paused and resumed:
Load metadata.json for current state
Find current task from current_task field
Check if task is [~] in plan.md
Ask user:
Resuming track: {title}
Last task in progress: Task {X.Y}: {description}
Options:
1. Continue from where we left off
2. Restart current task
3. Show progress summary first
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).