ExecPlan Authoring
Required inputs
- •The user must provide a PRD, RFC, or a detailed problem statement. If missing or unclear, ask for clarification before writing the plan.
Source of truth
- •Read
{baseDir}/PLANS.mdin full before drafting. - •If
{baseDir}/PLANS.mdis missing, copy this skill'sPLANS.mdto{baseDir}/.agent/PLANS.md, then read that copy as the source of truth. - •Follow PLANS.md exactly. If any instruction conflicts with this skill, PLANS.md wins.
Output location
- •Write the ExecPlan to
.agent/execplan-pending.mdin the target repo. - •If
.agent/does not exist, create it before writing the file.
Format rules
- •Because
.agent/execplan-pending.mdcontains only the ExecPlan, do not wrap it in outer triple backticks.
Authoring workflow
- •Read the user’s input and identify the concrete outcomes and acceptance criteria.
- •Inspect the repo to understand relevant files and structure; note paths explicitly in the plan.
- •Draft the ExecPlan using the skeleton and rules from PLANS.md.
- •Ensure required sections exist and are self-contained, novice-friendly, and behavior-focused.
- •Save to
.agent/execplan-pending.md.