What problem does it solve? It turns a resolved design or brainstorm into a formal, numbered requirements specification with observable verification criteria, preventing vague or untestable requirements from reaching architecture and planning stages. ## Core Features & Use Cases - Gap-only interview: Reads prior brainstorm and grill-me findings first, then asks only about unresolved sections instead of re-asking settled questions. - Append-only FR/NFR numbering: Continues from the highest existing FR-NN/NFR-NN number, never renumbering or reusing retired identifiers so downstream citations stay valid. - Encryption gate: Checks .gitattributes for a git-crypt filter before writing docs/REQUIREMENTS.md, stopping plaintext writes by default. - Use Case: After running /grill-me to resolve open design questions for a new feature, invoke /requirements to produce a testable spec that /architecture can trace every requirement back to a component. ## Quick Start Run /requirements with a feature note after your design questions are resolved to generate a numbered FR/NFR spec at docs/REQUIREMENTS.md.