l3-spec-planning

To turn non-functional requirements into a feature implementation plan, the Skill translates NFRs and acceptance criteria into a structured plan.md file. This plan maps design elements to tests-first increments, risks, and a definition of done for execution.

Spec-driven development planning is a process that maps NFRs and acceptance criteria to defined increments and tests. It produces a comprehensive plan covering scope, design alignment, risks, and a definition of done before implementation begins.

You generate a plan.md with tests-first increments by deriving the feature name from your request and mapping acceptance criteria to defined increments. The output is saved at features/<feature_name>/plan.md for review and execution.

Spec-driven feature planning works without predefined dependencies by documenting assumptions and design alignment directly in the generated plan.md. It independently structures feature scope, risks, and increments from your provided NFRs.

The best way to structure incremental development plans for NFRs is to map each requirement to specific tests-first increments and a definition of done. This ensures every non-functional requirement is validated through concrete tests within defined scope boundaries.