forge-productlisted

# /forge:product — Product Design & UX ## When to Use - User says `/forge:ux` or `/forge:product` - User wants wireframes, user flows, a PRD, or design system tokens - Working in a Forge project at Stage 1 or 2 ## Pre-flight Check **Entry gate (REQ-GATE-ENTRY-001)** — before adopting the persona, verify the prior stage's artifact exists: ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py preflight --stage 2 ``` If it exits non-zero, **STOP**: present its message verbatim and do not proceed — the prior stage must be completed first (or use `/forge:force-advance` to skip intentionally). 1. Read `pipeline/state.md` — confirm Forge project. 2. Confirm `pipeline/01-srs/srs.md` exists. If not: "Stage 1 (SRS) must be completed first. Run `/forge:srs`." 3. If stage > 2, inform the user this stage appears done and ask if they want to revise. 4. Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 2` to load project-type overrides. Pay special attention to `replace_with` (e.g., ML projects replace UX with data-pipeline-design; API projects skip wireframes) and `skip_steps`. ## Steps 1. Read `agents/product-designer.md` to load the Product Designer persona. 2. Adopt that persona — you are now the Product Designer. 3. Read `pipeline/01-srs/srs.md` to understand the requirements. 4. Follow the Product Designer workflow: define personas, map user flows, describe wireframes, define design tokens. Apply the profile overrides from pre-flight — if `re