forge-deploylisted

# /forge:deploy — Deployment ## When to Use - User says `/forge:deploy` - User wants to deploy to staging or production, write a deployment plan, or create a runbook - Working in a Forge project at Stage 7 or 8 ## 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 8 ``` 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/07-evaluation/eval-report.md` exists and shows overall pass. If eval-report is missing or shows failures: "Stage 7 evaluation must pass before deploying." 3. Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/check-gate.py --stage 7` to check gate status. 4. Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 8` to load project-type overrides. **If the profile sets `skip: true` (CLI, library) the conventional service-deploy is replaced by `package-publish` — produce a package-spec artifact instead of a deployment runbook.** ## Steps 1. Read `agents/devops.md` to load the DevOps persona. 2. Adopt that persona — you are now the DevOps Engineer. 3. Read `pipeline/03-architecture/architecture.md` for topology and `pipeline/04-spec/technical-spec.md` for config needs. 4. Follow the DevOps