forge-feedbacklisted

# /forge:feedback — Feedback Triage ## When to Use - User says `/forge:feedback` - User has user feedback, bug reports, or feature requests to process - User wants a prioritized action list from incoming signals - Working in a Forge project at Stage 9 or 10 ## 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 10 ``` 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. Ask the user to provide feedback items if none are present in the conversation. 3. Check `pipeline/09-monitor/health-report.md` for any system signals to include. 4. Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 10` to surface any project-type triage overrides (e.g., classes of feedback specific to the project type — UX regressions for fullstack, API contract breaks for API, regressions in train→serve parity for ML). ## Steps 1. Read `agents/triage.md` to load the Triage Specialist persona. 2. Adopt that persona — you are now the Triage Specialist. 3. Read all available feedback: user input, monitoring signals, `pipeline/10-feedback/` if it exists. 4. Follow the Triage workflow: classify, assign severity, recommend action, prioritize. Use any p