forge-validatelisted

# /forge:validate — pipeline gap analysis & traceability confirmation `/forge:validate` runs `scripts/validate-traceability.py`, which combines four checks the per-stage gate scripts don't cover (malformed IDs, misplaced ID definitions, duplicate ID definitions, unimplemented/orphaned requirements) with a rollup of the existing traceability and gate-completeness scripts, into one report. ## When to Use - `/forge:validate` — run the full report now. - Before a gate check or `/forge:release`, to catch drift the mechanical per-stage gates don't check (e.g. a requirement defined but never picked up by any task). - After a big edit to `pipeline/**/*.md` (renamed/renumbered requirements, merged docs) to confirm nothing broke the ID chain. - The user explicitly asks about traceability, ID hygiene, or gap analysis. ## When NOT to Use - A single stage's gate → that's `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/check-gate.py --stage N` (via `/forge:status` or the stage's own skill), not this. - The user wants the pipeline actually advanced → `/forge:orchestrate` or the specific stage's `/forge:*` command. ## Pre-flight Check Read `pipeline/state.md` to confirm this is a Forge project. If it doesn't exist, tell the user to run `/forge:init` first and stop — an uninitialized project has no `pipeline/` directory for this to scan. ## Steps 1. Run the report: ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/validate-traceability.py --cwd . \ --plugin-dir ${CLAUDE_PLUGI