conductor-implement by sickn33/antigravity-awesome-skills
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill conductor-implement执行跟踪实施计划中的任务,遵循 conductor/workflow.md 中定义的工作流规则。
resources/implementation-playbook.md。conductor/product.md 是否存在conductor/workflow.md 是否存在conductor/tracks.md 是否存在广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
/conductor:setupconductor/workflow.mdconductor/tracks/{argument}/plan.md读取 conductor/tracks.md
解析未完成的跟踪(状态为 [ ] 或 [~])
显示选择菜单:
选择要实施的跟踪:
进行中:
1. [~] auth_20250115 - 用户认证(第 2 阶段,任务 3)
待处理:
2. [ ] nav-fix_20250114 - 导航错误修复
3. [ ] dashboard_20250113 - 仪表板功能
输入编号或跟踪 ID:
加载实施所需的所有相关上下文:
conductor/tracks/{trackId}/spec.md - 需求conductor/tracks/{trackId}/plan.md - 任务列表conductor/tracks/{trackId}/metadata.json - 进度状态conductor/product.md - 产品理解conductor/tech-stack.md - 技术约束conductor/workflow.md - 流程规则conductor/code_styleguides/{language}.md将跟踪更新为进行中状态:
conductor/tracks.md 中:
[ ] 更改为 [~]conductor/tracks/{trackId}/metadata.json 中:
status: "in_progress"updated 时间戳对于 plan.md 中每个未完成的任务(标记为 [ ]):
解析 plan.md 以找到下一个未完成的任务:
- [ ] Task X.Y: {description} 的行将任务标记为进行中:
[ ] 更改为 [~]红色阶段 - 编写失败测试:
Following TDD workflow for Task X.Y...
Step 1: Writing failing test
绿色阶段 - 实施:
Step 2: Implementing minimal code to pass test
重构阶段:
Step 3: Refactoring while keeping tests green
提交更改(遵循 workflow.md 中的提交策略):
git add -A
git commit -m "{commit_prefix}: {task description} ({trackId})"
更新 plan.md:
将已完成任务的 [~] 更改为 [x]
提交计划更新:
git add conductor/tracks/{trackId}/plan.md
git commit -m "chore: mark task X.Y complete ({trackId})"
更新 metadata.json:
tasks.completedupdated 时间戳每个任务完成后,检查阶段是否完成:
[x]:运行阶段验证:
Phase {N} complete. Running verification...
npm test / pytest / 等。报告并等待批准:
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
关键:在进入下一阶段之前,必须等待用户的明确批准。
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
当所有阶段和任务都完成时:
All tasks complete. Running final verification...
在 conductor/tracks.md 中:
[~] 更改为 [x]在 conductor/tracks/{trackId}/metadata.json 中:
status: "complete"phases.completed 设置为总数tasks.completed 设置为总数updated 时间戳在 conductor/tracks/{trackId}/plan.md 中:
[x] Complete Track 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
在整个过程中,在 metadata.json 中维护进度:
{
"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)"
]
}
如果实施被暂停并恢复:
加载 metadata.json 以获取当前状态
从 current_task 字段查找当前任务
检查 plan.md 中任务是否为 [~]
询问用户:
恢复跟踪:{title}
最后进行中的任务:Task {X.Y}: {description}
选项:
1. Continue from where we left off
2. Restart current task
3. Show progress summary first
每周安装量
114
仓库
GitHub 星标数
27.4K
首次出现
2026年1月28日
安全审计
安装于
gemini-cli105
opencode104
codex103
github-copilot100
cursor99
antigravity97
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:
Change [~] to [x] for completed task
Commit plan update:
git 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
Weekly Installs
114
Repository
GitHub Stars
27.4K
First Seen
Jan 28, 2026
Security Audits
Gen Agent Trust HubWarnSocketPassSnykPass
Installed on
gemini-cli105
opencode104
codex103
github-copilot100
cursor99
antigravity97
通过 LiteLLM 代理让 Claude Code 对接 GitHub Copilot 运行 | 高级变通方案指南
40,000 周安装
项目文件夹结构蓝图生成器 - 自动生成多技术栈项目结构文档,提升代码组织一致性
7,800 周安装
Fluent UI Blazor 使用指南:Microsoft.FluentUI.AspNetCore.Components 4 版本完整教程
7,800 周安装
finalize-agent-prompt:AI智能体提示词优化工具,提升GitHub Copilot提示词质量与效率
7,700 周安装
Debian Linux 问题排查指南:使用 systemctl、journalctl、apt 诊断与修复系统故障
7,800 周安装
NUnit 单元测试最佳实践指南:C# 数据驱动测试与断言方法详解
7,700 周安装
技术调研文档创建指南:结构化模板与最佳实践
7,700 周安装