goalforge-runlisted

goalforge-internal — use entry commands; do not auto-trigger Orchestrator for the SDD planning chain, route-aware over the canonical route enum one-go|fast|standard|wave: standard = capture → spec → decompose → harden → execute → verify; fast = capture → add-wp → deterministic gates → execute → verify (route: read from the feature overview frontmatter, stamped by goalforge-capture). Routes the entry commands /spec /plan /implement /verify to the correct chain step, resumes mid-chain by reading the current WP status:, and supports --dry-run. Invoke goalforge-run when a user runs any of the four entry commands or when the chain must resume from a known WP stage. SKIP for single-step work: invoke the child skill directly (goalforge-capture, goalforge-spec, goalforge-decompose, goalforge-harden, goalforge-execute, goalforge-verify).
Truncuso/cogwright · ★ 0 · AI & Automation · score 75

Install: claude install-skill Truncuso/cogwright

# goalforge-run — SDD Orchestrator ## Location `goalforge-run` lives at `${CLAUDE_PLUGIN_ROOT}/skills/run/` — the PRIVATE `run/` orchestrator child of the local goalforge v2 package (source of truth per wp-13-local-rename). Its child skills (`goalforge-capture`, `goalforge-spec`, `goalforge-decompose`, `goalforge-harden`, `goalforge-execute`, `goalforge-verify`) are nested siblings under `${CLAUDE_PLUGIN_ROOT}/`, alongside the `sdd` local redirect hub. The orchestrator is invoked by name (`goalforge-run` / `skill-router goalforge-run`), so its directory location does not affect how the slash commands or the router resolve it. ## Chain `chain.yaml` (sibling file) declares the sequence. `goalforge-run` does not autonomously reorder or extend the chain; any modification goes through `/skill-improve`. ## Route awareness (canonical route enum) Routes are the canonical enum `one-go | fast | standard | wave`. The chain adapts to the goal's size: `goalforge-run` reads the feature overview's `route:` frontmatter (stamped by `goalforge-capture` via `goalforge-route.sh` — capture is the routing home; absent ⇒ `standard`) and skips the steps marked `when_route: standard` in `chain.yaml` for a `route: fast` feature: - **`standard`** — the six-step chain, unchanged. - **`fast`** — capture → `goalforge-decompose --add-wp` (ONE WP, complete self-contained goal block, no `spec.md`) → deterministic gates (`goalforge-validate` + `hooks/goalforge-open-questions-gate.sh --check` + `g