executing-plans
💡 摘要
一项让AI代理能够分批次执行预先编写的实施计划,并包含人工审核检查点的技能。
🎯 适合人群
🤖 AI 吐槽: “这不过是个美化的待办事项管理器,终于教会了AI代理在自信地开进沟里之前先问问路。”
该技能协调执行来自计划文件的任意任务,属于高风险操作。它可能调用其他技能/工具(如shell、文件操作),但未对计划中的命令进行内在验证。缓解措施:在执行任何操作之前,实施计划验证和清理步骤(例如,使用允许的操作白名单)。
name: executing-plans description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
Executing Plans
Overview
Load plan, review critically, execute tasks in batches, report for review between batches.
Core principle: Batch execution with checkpoints for architect review.
Announce at start: "I'm using the executing-plans skill to implement this plan."
The Process
Step 1: Load and Review Plan
- Read plan file
- Review critically - identify any questions or concerns about the plan
- If concerns: Raise them with your human partner before starting
- If no concerns: Create TodoWrite and proceed
Step 2: Execute Batch
Default: First 3 tasks
For each task:
- Mark as in_progress
- Follow each step exactly (plan has bite-sized steps)
- Run verifications as specified
- Mark as completed
Step 3: Report
When batch complete:
- Show what was implemented
- Show verification output
- Say: "Ready for feedback."
Step 4: Continue
Based on feedback:
- Apply changes if needed
- Execute next batch
- Repeat until complete
Step 5: Complete Development
After all tasks complete and verified:
- Announce: "I'm using the finishing-a-development-branch skill to complete this work."
- REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branch
- Follow that skill to verify tests, present options, execute choice
When to Stop and Ask for Help
STOP executing immediately when:
- Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
- Plan has critical gaps preventing starting
- You don't understand an instruction
- Verification fails repeatedly
Ask for clarification rather than guessing.
When to Revisit Earlier Steps
Return to Review (Step 1) when:
- Partner updates the plan based on your feedback
- Fundamental approach needs rethinking
Don't force through blockers - stop and ask.
Remember
- Review plan critically first
- Follow plan steps exactly
- Don't skip verifications
- Reference skills when plan says to
- Between batches: just report and wait
- Stop when blocked, don't guess
优点
- 强制结构化、可审查的执行流程,减少错误。
- 促进安全的批次处理和清晰的人机协作。
- 通过强制验证步骤提高可靠性。
缺点
- 严重依赖预先编写计划的质量。
- 僵化的批次大小(3个任务)可能不适合所有场景。
- 为简单或已充分理解的任务增加了开销。
相关技能
免责声明:本内容来源于 GitHub 开源项目,仅供展示和评分分析使用。
版权归原作者所有 obra.
