goalforge-decomposelisted

goalforge-internal — use entry commands; do not auto-trigger Decompose an approved feature spec into work packages and tasks. Reads plans/<feature>/spec.md, emits wp-NN-<slug>/ folders each containing overview.md (status: spec), todo.md, and task-NN-*.md files stamped from WP templates. Fills depends_on and parallel from the spec's WP table. Also owns the single-WP Add-WP mode (--add-wp): author ONE new WP into an existing feature — the fast-path (route: fast) WP author and the lightweight grow-on-the-go path for a mid-flight WP add, without a full re-decomposition (goalforge-redecompose stays the restructure tool). Trigger: the user asks to decompose, break down, or plan the work packages for a feature that has an approved spec.md — or to add a single WP to an existing feature mid-flight.
Truncuso/cogwright · ★ 0 · Data & Documents · score 75

Install: claude install-skill Truncuso/cogwright

# goalforge-decompose Reads an approved feature spec and emits the WP folder tree: one `wp-NN-<slug>/` folder per work package, each containing `overview.md`, `todo.md`, and one or more `task-NN-*.md` files. Fills `depends_on` and `parallel` from the spec's WP table. Schema reference: `${CLAUDE_PLUGIN_ROOT}/references/schema.md`. Templates: `${CLAUDE_PLUGIN_ROOT}/references/templates/`. ## When NOT to decompose — JIT rule (soft, forward-only; 2026-07-16) Do not decompose a feature until it is **next-to-execute** (spec approved AND at the execution frontier). Decompose-ahead builds a speculative WP buffer whose todo.md rollups, `depends_on` edges, and mirrored sequence entries drift before the work ever runs — measured 2026-07-16: 106 WPs at `spec` against 3 executing, and 57% of a month's commits spent on coordination surfaces. When asked to decompose a feature that is not next-to-execute, say so and confirm before proceeding. Forward-only: existing decomposed WPs stay (their depends_on edges are load-bearing); this rule governs NEW decompositions. ## Inputs - `<PLANS_ROOT>/<feature>/spec.md` — must exist. **Exception:** Add-WP mode (below) tolerates an absent `spec.md` — a `route: fast` feature has none by design; a full-path feature's spec is read when present. - `<PLANS_ROOT>/<feature>/overview.md` — read to extract the feature title and confirm `status: ready` (Add-WP mode: any non-`archived` status). ## Outputs (contracted files only) For each work package