create-plan

You can automate plan file creation by generating a new .plan.md file with required YAML frontmatter (name, overview, todos) and a structured markdown body containing Title, Objective, Architecture, File Changes, and Key Design Decisions.

Generating an agile plan file involves creating a structured markdown document with actionable todos and YAML frontmatter, which is then automatically stored in the unsorted backlog at .chalk/.cursor/plans/ to streamline sprint and feature-level planning.

Yes, newly generated plan files default to the unsorted backlog but include options to place them directly into specific workflow columns such as todo, inprogress, testing, or done to fit agile tracking needs.

The plan generation process validates your inputs against project conventions defined in AGENTS.md and provides a clear confirmation after file creation, ensuring the structured markdown plan adheres to required standards.

Manually drafting plan files is time-consuming and prone to formatting errors; automating the process enforces standardized YAML frontmatter and a consistent markdown body structure, eliminating manual overhead and structural inconsistencies.

A structured markdown plan file requires specific sections for Title, Objective, Architecture, File Changes, and Key Design Decisions, alongside YAML frontmatter defining the plan name, overview, and actionable todos.