make_requirementslisted

Gather and document requirements, turn an idea into formal requirement documents (RDs). Use for "make_requirements" (full discovery: brain dump or bare idea into a structured requirements/ set), "add_requirement" (add one new RD to an existing set), and "review_requirements" (health check / gap analysis on an existing set). Trigger when the user wants to capture, expand, structure, or audit what a system must do before building it — e.g. "help me spec out my app", "document requirements", "what features am I missing", "add a feature to the requirements", "review my requirements for gaps". Acts as a proactive domain consultant: absorbs the seed idea, expands it with comparable-system features, challenges it with edge cases, then decomposes it into numbered RDs behind a hard Zero-Ambiguity Gate.
blendsdk/claude-codeops · ★ 4 · AI & Automation · score 75

Install: claude install-skill blendsdk/claude-codeops

# Requirements Gathering & Documentation > **CodeOps Skills Version**: 3.20.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.