expand-requirements

To decompose design documents into structured requirements, provide your ideation materials and reference documents to the skill. It processes the input to extract discrete, testable features with acceptance criteria and outputs per-feature specifications to a standardized docs folder.

The best way to plan iterations and map dependencies from feature scoping is to process your design documents through automated requirement extraction. This sorts features into iterative plans with dependencies, enabling verifiable development across iterations.

Yes, you can extract testable requirements from prose without manual specifications. The skill applies automated requirement extraction to convert design inspirations into discrete, verifiable features with acceptance criteria and exports them to docs/harness/specs/.

Yes, the requirement decomposition process supports reference materials for Unity development. You can provide reference materials alongside your design documents to generate verifiable requirements, iteration plans, and dependency maps for downstream tooling.

Generated feature specifications are saved to a standardized docs/harness/specs/ folder after requirement extraction. The skill exports per-feature specs and templates to this location to guide downstream tooling and development across iterations.