بنقرة واحدة
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Execute tasks from a track's implementation plan following TDD workflow
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Analyze a project's past Codex sessions, memory files, and existing local skills to recommend the highest-value skills to create or update. Use when a user asks what skills a project needs, wants skill ideas grounded in real project history, wants an audit of current project-local skills, or wants recommendations for updating stale or incomplete skills instead of creating duplicates.
Apply treys-swarm-planner to the PT Study System by grounding in repo canon, the active execution board, Conductor tracks, planner APIs, and the `study_tasks` schema. Use when planning significant work in this repo and then executing it end-to-end with a backward-built wave/task graph until the goal is complete, unless the user explicitly asks for plan-only or review-only output.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Manage track lifecycle: archive, restore, delete, rename, and cleanup
Create a new track with specification and phased implementation plan
Git-aware undo by logical work unit (track, phase, or task)
| name | conductor-implement |
| description | Execute tasks from a track's implementation plan following TDD workflow |
| metadata | {"argument-hint":"[track-id] [--task X.Y] [--phase N]"} |
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}/index.md - Track status/navigationconductor/tracks/{trackId}/metadata.json - Legacy progress state only if presentProject 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 trackIf conductor/tracks/{trackId}/metadata.json exists:
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})"
If metadata.json exists, update it:
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 trackIf conductor/tracks/{trackId}/metadata.json exists:
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 canonical docs (if applicable) and ensure README links to them (if README isn't canonical):
- conductor/product.md (if new features added)
- conductor/tech-stack.md (if new dependencies added)
- README.md (as an index; only add/refresh links unless README is canonical)
- Run any doc drift check scripts (if the repo has them)
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
If metadata.json exists, maintain legacy progress fields there. Otherwise keep progress in plan.md and index.md:
{
"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 if it exists; otherwise infer state from plan.md and index.md
Find current task from current_task or the first [~] / next [ ] task in plan.md
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
index.md or the final completion summary