plan

To create a standardized feature plan, provide a feature slug and context. The skill reads existing architecture notes and goals, then generates a structured plan file with sections for Goal, Design Decisions, Scope, Implementation, Test Cases, and Open Questions, saving it sequentially to .agents/plans/.

A feature planning document for architecture reviews should include structured sections for Goal, Design Decisions, Scope, Implementation, Test Cases, and Open Questions. This standardized template enforces consistency and aligns product teams during feature ideation and scoping.

Document design decisions and scope by generating a plan file that reads existing architecture notes and goals. The skill enforces a structured template with dedicated sections, prompting for user confirmation before saving to ensure quality and alignment with project objectives.

Yes, context-driven planning reads existing architecture notes and goals to guide feature scoping and task rationalization. The skill uses this context to generate a sequential plan file, ensuring new feature work aligns with established architecture and product goals before saving.

The best way to maintain consistent feature planning files is sequential plan generation. The skill creates a next-plan file under .agents/plans/ with a unique sequential number, using a standardized template and a review flow that prompts for confirmation before saving.

Generating sequential plan files requires a .agents/plans/ directory in the repository. The skill saves the structured plan file, featuring Goal, Design Decisions, Scope, Implementation, Test Cases, and Open Questions sections, to this location with a sequential numeral.