// Execute an implementation plan. Implements every task, runs validation, commits, and opens a PR. Use when the user asks to execute, implement, or run a plan file.
Create a GitHub release and publish to NPM.
Commit staged work, push the branch, and open a PR. Use when wrapping up changes that need to ship.
Draft an implementation plan for a feature in .agents/plans. Does not execute the plan. Use when the user asks to plan, design, or scope a feature without building it.
Triage and fix dependency vulnerabilities in an npm project. Use when the user asks to fix, address, or patch dependency/dependabot/npm audit vulnerabilities.
Prepare a release PR by bumping package versions (patch, minor, or major).
Analyze past Claude Code session(s) for mistakes and propose targeted improvements. Use when the user asks for a retrospective, post-mortem, or session review. Outputs concise findings plus suggested edits to CLAUDE.md (general lessons) or new/updated skills (specific workflows).
| name | execute-plan |
| description | Execute an implementation plan. Implements every task, runs validation, commits, and opens a PR. Use when the user asks to execute, implement, or run a plan file. |
| argument-hint | path to plan file |
Implement a plan end-to-end: code the tasks, validate, commit, and open a PR.
Read the plan file passed in $ARGUMENTS. If no path is given, list .agents/plans/ and ask which one. Re-read the plan whenever you need to refresh context — do not paraphrase from memory.
Never commit to main. Check the current branch:
main, create a new branch named after the plan slug (e.g., <slug> from YYYY-MM-DD-<slug>.md).Use TaskCreate to mirror every item from the plan's "Tasks" section as a todo, in order. The final todo must be "Run validation steps" (this should already be the last task in the plan). Do not skip, merge, or reorder tasks.
Work through todos one at a time. Mark each completed as soon as it is done — do not batch. If you discover the plan is wrong or incomplete, stop and ask the user before diverging.
Use the validate skill.
Use the commit skill. Stage only plan-related files. Default base is main (see memory).
One or two sentences: what shipped, PR link, anything the user should know (skipped items, open questions, follow-ups).