execute-plan
Batch-execute tasks from the active epic capsule sequentially, with a human checkpoint after each step. Use when user has an approved plan and wants step-by-step oversight.
danielvm-git · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add danielvm-git/bigpowers --skill execute-plan技能说明
name: execute-plan model: haiku description: "Batch-execute tasks from the active epic capsule sequentially, with a human checkpoint after each step. Use when user has an approved plan and wants step-by-step oversight."
Execute Plan
Execute tasks from the active epic (specs/epics/eNN-slug/epic.yaml story tasks[]) one at a time, showing evidence after each step before proceeding.
HARD GATE — Do NOT proceed if on
mainormaster. Runkickoff-branchfirst.HARD GATE — Active epic must exist with runnable
verifyon each task. If missing, runplan-releasethenplan-workorbuild-epic.
Process
1. Read the plan
Read specs/state.yaml (active_epic, active_story) and the matching specs/epics/*/epic.yaml. Parse depends-on in task descriptions for execution waves.
CONTEXT ISOLATION — Spawn each skill with a fresh context window. Pass decisions only through
specs/state.yamlhandoff— never rely on prior chat history.
Confirm with the user: step count, skip/reorder, stop-after step.
2. Execute step by step
For each task in the active story:
a. Announce — task desc and verify command.
b. Execute — code or delegate-task / dispatch-agents for waves.
c. Run verify — must be green before advancing.
d. Log — non-obvious decisions in specs/state.yaml under decisions[] or handoff block.
e. Checkpoint — ask to proceed unless autonomous mode requested.
f. Story UAT — after last task, run manual verification script from story notes or verify-work.
On verify failure: fix and re-run; never advance on red.
Update specs/execution-status.yaml when a story/epic completes (bash scripts/sync-status-from-epics.sh or direct edit).
3. Blockers
Report blocker; ask skip/adapt/stop; update epic capsule if plan changes.
4. Final report
Suggest: verify-work → run-evals → audit-code → simulate-agents → commit-message → release-branch
Rules
- Loop until behavioral correctness is verified: if a verify command passes but the observed behavior is still wrong, return to step 1 and run the execution cycle again.