execute-plan
Execute Plan
Overview
Execute a pre-approved plan with strict adherence to scope, sequence, and verification.
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.
Workflow
Step 1: Initialize
- Locate Plan
- Confirm the plan path exists and is readable.
- If a directory is provided, locate
SUMMARY.mdinside it.
More from buiducnhat/agent-skills
write-plan
Create detailed, execution-ready implementation plans for complex or high-risk changes without coding. Use when scope is large, requirements are mostly known, and work should be broken into validated phases before execution.
385brainstorm
Collaborative discovery and design framing for ambiguous or high-risk work. Use when requirements are unclear, multiple approaches are possible, or you need to turn an idea into a validated design brief before planning or coding.
349docs
Create or refresh project documentation in `docs/`. Use when a project needs docs initialized or existing docs synced to the current codebase.
340quick-implement
Rapid implementation for small, low-risk, well-defined changes. Use when the task is narrow in scope, has clear acceptance criteria, and can be completed safely without a formal multi-phase plan.
337ask
Structured clarification and requirements gathering through focused dialogue. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed.
193bootstrap
Initialize and scaffold a new project with structured requirements gathering. Use when starting a project from scratch, after running a framework initializer (npm init, create-next-app, etc.), or when an existing minimal project needs proper structure, documentation, and conventions. Triggers on: 'bootstrap project', 'start new project', 'scaffold project', 'initialize project', 'setup new project', or when the user wants to go from zero to a well-structured project foundation.
191