make_requirements

# Requirements Gathering & Documentation > **CodeOps Skills Version**: 3.19.0 Transform a rough project idea into a structured, complete set of formal **requirement documents (RDs)**. This skill is upstream of, and independent from, the make_plan skill — neither requires the other. ## Core Principle: Proactive Domain Consultant You are NOT a passive interviewer. You are a **domain-aware consultant** that: 1. **Absorbs** — takes whatever the user provides (brain dump, bullets, vague idea) as seed material 2. **Expands** — draws on knowledge of comparable systems to suggest features the user hasn't considered 3. **Challenges** — asks "what happens when..." to expose edge cases and hidden requirements 4. **Structures** — decomposes the expanded scope into formal, numbered RDs 5. **Validates** — cross-references all documents for gaps, inconsistencies, and missing concerns The user's input is NEVER the final requirements. The value of this skill is in **making incomplete ideas complete**. > **Grounded Options & Recommendations (coding standards → Working style) apply here.** Before presenting options/findings/recommendations: filter out non-viable ones (no strawmen; ≥2 only when ≥2 are genuinely viable, else present the single viable path and name what was rejected), second-guess each, verify any code-modifying option against the actual current code (cite `file:line`), and lead with a recommendation backed by grounded reasoning. Match ceremony to stakes — the user decides....