create-plan

To generate a structured implementation plan, you need to define requirements, design, and implementation steps with clear review gates. This skill automates that scoping process by producing three Markdown files with gated milestones to align your team.

Automating feature planning with gated milestones requires a phase-driven workflow that separates requirements, design, and implementation. This skill generates those distinct phases with explicit approvals, ensuring structured progression across project milestones.

Yes, you can create requirements and design documentation for architecture changes. The skill explicitly applies to feature planning tasks across software components and architecture changes, outputting dedicated Markdown files for each phase.

Context logging during plan generation automatically updates a Context section after significant interactions. This mechanism ensures session recovery by capturing iteration history directly within the generated workflow files.

Yes, the plan-generation workflow supports manual approvals between phases. It utilizes a phase-driven workflow with explicit gates, requiring review and approval before moving from requirements to design and implementation.

The generated implementation steps and requirements are saved in Markdown format. The skill outputs three specific Markdown files: requirements.md, design.md, and implementation.md, each containing gated review steps and frontmatter metadata.