feature-planning

To create an actionable feature plan, you need to draft a structured document covering goals, scope, architecture, and tests. This skill interactively elicits requirements and aligns with project conventions to generate an agent-ready plan.md for execution.

An agent-ready feature plan is a structured markdown file designed to guide both human review and automated execution. It includes sections for goals, architecture, steps, migration, and tests, ensuring development aligns with repository conventions.

To ensure feature documentation aligns with repository conventions, the planning process discovers and applies existing project rules during drafting. This guarantees the resulting plan.md maintains consistency with your software engineering workflows.

Yes, you can automatically capture feature requirements and scope before coding. The skill elicits constraints, success criteria, and scope via interactive questions, structuring the answers into a pragmatic plan stored in your repository's planning directory.

A comprehensive feature planning document should include sections for goals, scope, architecture, steps, configuration, migration, tests, and documentation. These sections ensure the plan is executable and addresses all software engineering requirements.

Yes, the feature planning workflow supports repositories without existing documentation by interactively eliciting requirements via AskUserQuestion. It builds the plan from your answers, applying standard design lenses to produce a structured plan.md.