メニュー
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | executing-plans |
| description | Use when you have a written implementation plan to execute in a separate session with review checkpoints |
Related skills: Need an isolated workspace?
/skill:using-git-worktrees. Verify each task with/skill:verification-before-completion. Done?/skill:finishing-a-development-branch.
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."
plan_tracker tool and proceedDefault: First 3 tasks
For each task:
plan_tracker toolplan_tracker toolWhen batch complete:
Based on feedback:
After all tasks complete and verified:
/skill:finishing-a-development-branchSTOP executing immediately when:
Ask for clarification rather than guessing.
Return to Review (Step 1) when:
Don't force through blockers - stop and ask.
Required workflow skills:
/skill:using-git-worktrees - REQUIRED: Set up isolated workspace before starting/skill:writing-plans - Creates the plan this skill executes/skill:finishing-a-development-branch - Complete development after all tasksUse when creating new skills, editing existing skills, or verifying skills work before deployment
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies