feature-requirements

To generate requirements from a PRD and technical plan, use this Skill to formalize user stories and business rules into numbered functional and non-functional requirements. It produces a structured requirements.md file for the active Flutter feature slice.

The best way to formalize user stories and business rules into numbered requirements is using a structured documentation generator. This Skill applies your project template to convert existing PRD and plan inputs into reviewable functional and non-functional requirement lists.

Yes, you need both a PRD and a technical plan before generating requirements.md. The Skill requires existing prd.md and plan.md files for the current feature slice to extract and formalize technical invariants and business rules accurately.

Yes, you can automatically copy the out-of-scope list from a PRD into a requirements document. The Skill extracts the PRD out-of-scope section and includes it in the final requirements.md file without inventing new exclusions.

This requirements generation tool works specifically for the Flutter movie-theater-tickets project. It applies the exact project template to ensure the numbered functional, non-functional, and out-of-scope requirements match your established documentation structure.

The generated requirements file only includes existing PRD exclusions to prevent scope creep and maintain document fidelity. By copying the out-of-scope section directly without inventing new exclusions, it ensures the formalized requirements accurately reflect the original PRD boundaries.