forge-srslisted

# /forge:srs — Requirements Analysis ## When to Use - User says `/forge:srs` - User wants to define requirements, write an SRS, or describe what to build - Working in a Forge project at Stage 0 or 1 ## Pre-flight Check 1. Read `pipeline/state.md` to confirm this is a Forge project. 2. Note the current stage. If stage > 1, inform the user this stage appears done and ask if they want to revise it. 3. Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 1` to load any project-type overrides for this stage. Apply the emphasis hints, skip flags, additional artifacts, concerns, and criteria when following the persona workflow below. ## Steps 1. Read `agents/requirements-analyst.md` to load the Requirements Analyst persona. 2. Adopt that persona completely — you are now the Requirements Analyst. 3. Ask the user to describe their project if they haven't already. Gather: - What the system does - Who uses it - Key constraints (technology, timeline, compliance) 4. **Clarify before writing (REQ-INTERACTIVE-CLARIFY-001).** If the description is vague or under-specified, ask ONE bounded clarifying-question round BEFORE writing `pipeline/01-srs/srs.md` — a single batch covering the highest-ambiguity areas (scope, users, constraints). This is a single round, not a drip; cap at one batch (max 1 round) and bundle the questions rather than trickling them out. 5. Follow the Requirements Analyst workflow: clarify, categorize, assign REQ-IDs, write acceptance c