execplan-planner

To generate an execution plan, provide your feature goal and context to synthesize conversation-derived requirements into a production-grade Markdown plan file. The planner validates against repository guidelines, enforcing exact file paths, sections, and acceptance criteria without altering code.

Creating a step-by-step implementation plan involves drafting a file under .agent/plans/ that complies exactly with .agent/PLANS.md format. It enforces strict structure, sections, and kebab-case naming conventions to ensure plan reusability and auditability while selecting or updating the plan file.

The planner does not modify your codebase when generating a plan, as it only outputs a complete, ready-to-implement Markdown file. It interprets requirements and validates against .agent/PLANS.md to ensure exact file paths and acceptance criteria are documented without altering code.

If requirements are ambiguous during plan generation, the planner prompts you for clarification to resolve the ambiguity. It accepts conversation-derived requirements and any extra hints, ensuring the final execution plan accurately captures explicit steps and file-level guidance before saving.