feature-plan

Feature planning generates a structured discovery narrative, testable acceptance criteria, and a user story by guiding teams through end-to-end validation. It captures product goals, decisions, and constraints directly into a story.md file for immediate team action.

Documenting discovery outcomes involves creating an annotated summary and seed design.md files that capture formal validation, traceable decisions, and scope constraints. This ensures implementation-era handoff records all product constraints and design seeds.

Creating design seeds and repo-context requires populating repository context and seeding design.md during the feature planning phase. This produces structured implementation notes and traceable decisions ready for developer review and downstream coding.

Structured feature planning applies to new product ideas, internal initiatives, and features requiring formal validation. It supports diverse contexts by generating discovery narratives and acceptance criteria aligned with specific product goals and scope.

End-to-end feature planning requires no specific dependencies or tooling environments to generate the core story.md and design.md files. It provides optional tooling guidance and review steps to fit your existing collaboration workflow.