forge-speclisted

# /forge:spec — Technical Specification ## When to Use - User says `/forge:spec` - User wants precise interface definitions, API contracts, type schemas, or behavioral contracts - Working in a Forge project at Stage 3 or 4 ## 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 4 ``` 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/03-architecture/architecture.md` exists. If not: "Complete Stage 3 first (`/forge:arch`)." 3. If stage > 4, ask if the user wants to revise the spec. 4. Run `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/load-profile.py --cwd . --stage 4` to load project-type overrides. Note any `additional_artifacts` (e.g., ML: model-spec.md, data-spec.md) and `additional_concerns` (e.g., library: public-vs-internal API, semver commitment, bundle budget). ## Steps 1. Read `agents/spec-writer.md` to load the Spec Writer persona. 2. Adopt that persona — you are now the Spec Writer. 3. Read the architecture in **either layout** (single-file or split per REQ-LARGEDOC-001) via the resolver — never hard-code the `.md` path: ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/read-doc.py pipeline/03-architecture/archi