Menu
Implement from an active plan or ExecPlan while keeping it up to date. Use when an agent needs to implement the active plan, continue plan-driven work, resume the current plan, or carry out an existing ExecPlan.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create or revise Markdown `description` frontmatter so `docgarden match` routes agents to the right repository documents. Use when adding a new routed Markdown document, updating existing frontmatter, fixing noisy or missing match results, tuning skills or docs discovery, or making descriptions more query-aligned without loading document bodies.
Guide for writing ast-grep rules to perform structural code search, analysis, and bulk rewrites/refactors. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, perform complex code queries that go beyond simple text search, or carry out structural refactors and code transformations across many files. This skill should be used when users ask to search for code patterns, find specific language constructs, locate code with particular structural characteristics, or rewrite/refactor/migrate code structurally (e.g., renaming an API across all callers, replacing a deprecated pattern, migrating call signatures) instead of reaching for sed, custom Python scripts, or one-off regex replacements.
Review the current branch, PR, or worktree against the plan or ExecPlan and record findings. Use when an agent needs a code review with findings for changes associated with an active plan.
Create, update, revise, reopen, or rescope a plan or ExecPlan using `PLANS.md`. Use when an agent needs to create a plan, plan a change, update the plan with new requirements, or rewrite an active ExecPlan.
| name | generator-execplan |
| description | Implement from an active plan or ExecPlan while keeping it up to date. Use when an agent needs to implement the active plan, continue plan-driven work, resume the current plan, or carry out an existing ExecPlan. |
Use this skill when the plan already exists and the task is to execute from it without losing the thread.
MUST READ before implementing:
docs/PLANS.mdPLANS.md defines the required ExecPlan structure, lifecycle, and maintenance rules.
As generator, you own:
You do not own:
completed/) or completion reviewUse the generator when the plan already exists and the task is to implement from it while keeping the living document current according to PLANS.md.
Update the ExecPlan as you go. Do not wait until the end of a long run to write progress back into the plan, and do not leave user-driven requirement changes only in chat context.
At every meaningful stopping point, leave the plan in a state that a fresh contributor can resume from after a crash, interruption, or handoff.
If requirements or success criteria change in a way that changes what the plan is asking for, stop and hand the plan back to planner-execplan before continuing.
When implementation is complete, you MUST check off the Generator items in the Definition of Done section and hand off to evaluator-execplan by spawning a subagent. If you cannot invoke subagents, STOP and ask the user to proceed with review. NEVER close the plan yourself.
If the evaluator returns findings, address them and spawn a fresh evaluator subagent. Repeat until the evaluator completes a clean pass. Never check off Evaluator DoD items yourself.