Help us improve
Share bugs, ideas, or general feedback.
From cobrew
Executes approved implementation plans with strict adherence to scope, sequence, and verification. Supports batch and interactive modes, phase tracking, and final reporting.
npx claudepluginhub buiducnhat/cobrew --plugin cobrewHow this skill is triggered — by the user, by Claude, or both
Slash command
/cobrew:execute-plan [plan path, e.g. docs/plans/YYMMDD-HHmm-<plan-slug>/SUMMARY.md][plan path, e.g. docs/plans/YYMMDD-HHmm-<plan-slug>/SUMMARY.md]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Execute a pre-approved plan with strict adherence to scope, sequence, and verification. Treat the plan as a living document that records progress, findings, decisions, and outcomes as execution proceeds.
Implements approved technical plans from a configured plans directory phase-by-phase, verifying each phase with success criteria checks and user review before proceeding.
Executes written implementation plans in controlled batches with review checkpoints, verification, and feedback. Use when a plan exists needing strict adherence and regression prevention.
Executes written implementation plans in batches with review checkpoints between batches. Useful when you have a plan file to follow step-by-step.
Share bugs, ideas, or general feedback.
Execute a pre-approved plan with strict adherence to scope, sequence, and verification. Treat the plan as a living document that records progress, findings, decisions, and outcomes as execution proceeds.
The input is typically: execute-plan docs/plans/YYMMDD-HHmm-<plan-slug>/SUMMARY.md
Do not redesign the plan during execution. If ambiguity or blockers appear, stop and ask.
Locate Plan
SUMMARY.md inside it.Load Execution Context
docs/SUMMARY.md exists, read it first.Code Standard docs for implementation conventions.Progress, Surprises & Discoveries, Decision Log, Outcomes & Retrospective), add those sections before execution when the plan is otherwise clear.Select Execution Mode (Explicit Rule)
Find Next Pending Phase
[ ] phase[-] phaseCritical Plan Sanity Check
For each phase in order:
Skip Completed
[x], continue to next phase.Mark In Progress
[-] before making changes.Progress entry in SUMMARY.md describing the phase start.Execute Exactly
Surprises & Discoveries in SUMMARY.md.Decision Log before continuing.Verify Phase
SUMMARY.md under Progress or the phase's requested evidence location.Handle Failures
Mark Complete
[x] only after verification passes.Progress entry with the verification result and changed files for that phase.Progress Report
After all phases are complete:
Project-Wide Validation
Stabilize
Manual Validation Checkpoint
Verified to acceptUpdate Outcomes
Outcomes & Retrospective in SUMMARY.md with final result, verification summary, approved deviations, and follow-ups.Documentation Sync
docs artifacts.Create Execution Report
docs/plans/YYMMDD-HHmm-<plan-slug>/EXECUTION-REPORT.mdPrepare Final Gate
Need verify, and execution must continue against the same plan path.After completion artifacts are done, ask the user for a final confirmation using the input/question with exactly these options:
Confirm: End sessionConfirm and Auto commit gitNeed verifyHandle the selected option as follows:
Confirm: End session
docs/plans/archived/.Execution complete. Report archived at docs/plans/archived/YYMMDD-HHmm-<plan-slug>/EXECUTION-REPORT.md.Confirm and Auto commit git
docs/plans/archived/.Execution complete. Report archived at docs/plans/archived/YYMMDD-HHmm-<plan-slug>/EXECUTION-REPORT.md.git-commit skill and complete an automatic commit flow.Need verify
EXECUTION-REPORT.md must use the following template: references/execution-report-template.md
docs/ and related project docs.SUMMARY.md as execution proceeds. Do not rely on chat history for important execution state.