frd-getting-started

Feature requirements scaffolding automates initial FRD creation by parsing product overview documents to identify feature sets. It generates a standardized directory structure with stub files, solving the blank page problem when initializing a new project.

Initial project requirements should be scoped using guided scoping that calibrates between agile and waterfall methodologies based on preference. This ensures feature sets are structured and aligned with product goals without manual template creation.

To scaffold agile feature requirements, run a discovery-driven skill that analyzes the current project and existing product descriptions. It identifies feature sets and automatically generates the necessary FRD stubs to kickstart development.

Yes, automated FRD scaffolding supports both agile and waterfall methodologies through guided scoping. It calibrates project requirements based on user preference to ensure the generated feature sets align with the chosen development approach.

Use automated scaffolding for feature requirements when initializing a new project with an empty requirements folder. It reads existing product descriptions to propose a feature set and generate standardized FRD stubs, bypassing manual template creation.