Requirements Doc

Capture a stream-of-consciousness description of requirements and produce a structured requirements document.

Mode

interactive (default): Full standalone workflow. Saves to Docs/requirements/{feature-name}.md.
spec: Called by create-spec. Produces the Requirements section of the unified spec at Docs/In-Progress/{feature-name}-spec.md. Does not create a standalone file.

Ask the user: "What are you building? Give me the full stream of consciousness — don't worry about structure, I'll organize it."
If the user has already provided the description, proceed directly.
Ask clarifying questions where the description is ambiguous or incomplete. Focus on:
- Who are the users?
- What problem does this solve?
- What are the must-haves vs nice-to-haves?
- Are there constraints (technology, timeline, budget)?
- Are there integrations with existing systems?
Produce a structured Markdown document at Docs/requirements/{feature-name}.md (interactive mode) or as the ## 1. Requirements section of the unified spec (spec mode) with: