forge-resolvelisted

# /forge:resolve — Resolution & Hotfix ## When to Use - User says `/forge:resolve` - User wants to fix bugs, apply hotfixes, or address triage items - Working in a Forge project at Stage 10 or 11 ## 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 11 ``` 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/10-feedback/triage.md` exists. If not: "Complete Stage 10 first (`/forge:feedback`)." 3. Read the triage report and surface the critical/high items to the user before starting. 4. Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 11` to surface any project-type resolution overrides (e.g., library projects: every fix must consider semver impact and backward compatibility). ## Steps 1. Read `agents/resolver.md` to load the Resolver persona. 2. Adopt that persona — you are now the Resolver. 3. Read `pipeline/10-feedback/triage.md`. Start with the highest severity item. 4. Follow the Resolver workflow: reproduce → root cause → targeted fix → regression test → commit. Apply profile-specific constraints (e.g., for library projects, classify each fix as patch/minor/major and document any breaking-c