requirements-generatorlisted

# Requirements Generator Take a project idea, feature description, or user story and generate a structured requirements document with functional requirements, non-functional requirements, Gherkin acceptance criteria, edge cases, and out-of-scope items. ## Instructions **Two modes:** - **Description mode** (default): user provides a free-form description or pastes a Jira/Confluence URL. Claude generates requirements from that. - **Interview mode** (`/requirements-generator --interview`): Claude asks a structured set of questions one at a time, then generates requirements from the answers. 1. **Gather input.** Ask the user what they want to build if no description has been provided. Accept any of: - A pasted feature description or user story - A Jira ticket URL or Confluence page URL (read via available MCP tools if present) - A brief verbal description of the feature Prompt: _"Describe the feature or system you want to build. Include the user need it addresses and any known constraints."_ If the user invoked with `--interview`, skip this prompt and proceed to the **Interview Mode** section below instead. 2. **Understand the existing codebase** (if one exists). Use Glob on `*` to detect the project structure. Read `package.json`, `pyproject.toml`, or `go.mod` to identify the tech stack. Read 3–5 representative files from `src/` or `app/` — entry points first (`index.*`, `main.*`, `app.*`), then one route/handler file and one model/schema file — to understa