AGENT SKILL

goalforge

PUBLIC front door for the goalforge Spec-Driven Development (SDD) chain: capture → spec → decompose → harden → execute → verify. Use to explain the chain, pick the stage child, or locate schemas, templates, and scripts. Triggers: "explain goalforge", "explain SDD", "which goalforge skill", "where are the goalforge templates". Not for RUNNING the chain — use /spec /plan /implement /verify or /goalforge-run.

License 许可
MIT
所属仓库
Truncuso/cogwright
最近更新
2026-11-12
Stars
★ 0
Forks
0

01 前言 Front Matter

name
goalforge
metadata
{ "version": "4.0.0", "skill-kind": "preference" }
description
PUBLIC front door for the goalforge Spec-Driven Development (SDD) chain: capture → spec → decompose → harden → execute → verify. Use to explain the chain, pick the stage child, or locate schemas, templates, and scripts. Triggers: "explain goalforge", "explain SDD", "which goalforge skill", "where are the goalforge templates". Not for RUNNING the chain — use /spec /plan /implement /verify or /goalforge-run.

02 资源文件 104

03 SKILL.md 正文

goalforge — Spec-Driven Development chain (LOCAL authority)

packages/goalforge/ is the authored source of truth; plugins/goalforge/ is its generated artifact (scripts/goalforge-generate.sh, drift-gated). The maintainer's dotfiles reach this package via a per-machine symlink.

This is a PUBLIC-parent package: a PUBLIC parent (this file) owning PRIVATE nested children. Children do not trigger by discovery — they are invoked by name from the entry commands and the orchestrator, or referenced here.

Contract: plans/<feature>/spec.md carries the Interface Contract C1-C7 (WP shape, frontmatter, gate set, stop rules, dispatch unit, trace, human touchpoints); references/schema.md and references/state-machine.md are the field and status authorities. A WP is one overview.md with 8 fixed sections and a checklist; there are no task files.

Children (name → stage → path)

Skill Stage Path
goalforge-capture free-text intent → overview.md (draft) capture/
goalforge-spec design pass → spec.md with goal + behaviors, draft → spec → ready (ratified); respec spec/
goalforge-decompose spec → WP overviews with checklists; --add-wp mode decompose/
goalforge-harden WP spec → hardened → ready (gates G1-G4, 2-round stop) harden/
goalforge-execute ready → executing → implemented (one owner, one commit) execute/
goalforge-verify implemented → verified (gates A/B/C) verify/
goalforge-redecompose reconcile a re-decomposition on a learning event redecompose/
goalforge-archive completed → archived (supersede edges) archive/
goalforge-onboard onboard an existing repo into the chain onboard/
goalforge-plan-index plan index generation plan-index/
goalforge-run chain driver by status run/

Shared assets

You want… At
Frontmatter schema, status machine ${CLAUDE_PLUGIN_ROOT}/references/schema.md, references/state-machine.md
File templates ${CLAUDE_PLUGIN_ROOT}/references/templates/
Trace event schema ${CLAUDE_PLUGIN_ROOT}/references/trace-events.md
Gate, hash, transition scripts ${CLAUDE_PLUGIN_ROOT}/scripts/goalforge-*.sh
Gate sabotage pairs + harness hooks/tests/, scripts/tests/, evals/run.sh (maintainer tree only; not shipped in the plugin)

Entry points

/spec, /plan, /implement, /verify are the human entry points; each is a thin dispatch surface that reads the stage child's SKILL.md directly and runs the procedure in-session. /goalforge-run pins the goalforge-run driver (run/) for the whole chain.

prototype/ and wayfind/ are non-chain tenants co-located in this package, reachable via the installer's top-level symlinks.

Legacy naming

The sdd-* skill/script aliases were RETIRED 2026-07-21. Historic name map: references/alias-map.md.

Gotchas

  • goalforge-run is PUBLIC-PINNED as /goalforge-run, not as a Skill-tool name. It is a PRIVATE nested child with no discovery entry; invoking goalforge-run by name answers "Unknown skill". commands/goalforge-run.md loads run/SKILL.md by path.
  • Package tree and plugin tree discover children differently. In the package tree discovery is one level deep: only goalforge, prototype, and wayfind are discoverable, and every other child is read by path. The plugin emits all 13 children under skills/, so each child is plugin-discoverable as goalforge:<child>, guarded by the do-not-auto-trigger description marker.
  • A gate that does not emit gate.result is not a gate. Every PreToolUse guard and gate script emits through scripts/goalforge-trace-emit and ships a sabotage pair (known-bad exit 2, known-good exit 0) under evals/run.sh. goalforge-pre-commit.sh (git hook) and goalforge-frontmatter-touch.sh (non-blocking) ship pairs but emit no row.

04 同仓库更多 Skills

Truncuso
Truncuso/cogwright

wayfind

goalforge-internal — use entry commands; do not auto-trigger Chart a foggy, multi-session effort into a decision map BEFORE goalforge-capture — when the work is too big to spec yet, spans multiple sessions, and needs a decision map before anyone can write a real spec. Triggers: "chart this foggy effort", "multi-session decision map", "too big to spec yet", "map the unknowns before we plan". Establishes <PLANS_ROOT>/<effort>/wayfind/ (map.md pointer-index + one-decision-per-ticket files), drives a frontier-computed work loop across sessions, and graduates the converged map into goalforge-capture. SKIP when the effort is one session and already clear — a single well-understood feature goes straight to goalforge-capture with no map. SKIP for a bounded one-off edit, and for anything already past spec (that is the SDD chain, not wayfind).

★ 0
Truncuso
Truncuso/cogwright

verify

goalforge-internal — use entry commands; do not auto-trigger Verify a work package at `status: implemented`: gate A deterministic (lint, typecheck, verification.command, diff ⊆ owned_files), gate B one fresh-context review of the WP diff, gate C goal judge plus one second opinion. Advances `implemented → verified` — the sole authority for that edge. TRIGGER: /verify <wp-path>, or when the chain reaches the verify step.

★ 0
Truncuso
Truncuso/cogwright

spec

goalforge-internal — use entry commands; do not auto-trigger Run a design pass on a captured feature and propose the spec document, or propose a revision of an approved spec when a learning falsifies it (the respec edge). Reads plans/<feature>/overview.md, optionally invokes personas or architect for a multi-lens review, writes plans/<feature>/spec.md from the feature-spec template as the proposal (draft → spec), and ratifies it on spec → ready. HUMAN-GATED: spec → ready needs explicit user approval. Trigger: the user asks to spec, design, or elaborate on a feature that already has an overview.md (status: draft), or a feature sits at status: spec with a proposal awaiting ratification.

★ 0
Truncuso
Truncuso/cogwright

run

goalforge-internal — use entry commands; do not auto-trigger Chain driver for the goalforge stages: capture → spec → decompose → harden → execute → verify. Reads the target's on-disk `status:` and enters the one step that status admits; supports --dry-run. Use it to drive a feature end-to-end; for a single stage, use the entry command for that stage.

★ 0
Truncuso
Truncuso/cogwright

redecompose

goalforge-internal — use entry commands; do not auto-trigger Reconcile a proposed re-decomposition against a partially-executed feature's verified WPs. Calls goalforge-reconcile-diff.sh to produce a 5-bucket diff, then routes: same → untouched (no-op), changed+new → status: spec and onto the harden frontier via goalforge-transition.sh, dropped-verified → supersede in place (ledger row, never delete), ambiguous (slug changed, goal matches a verified WP) → judgment/human — never auto-rename or auto-supersede. Logs goal mutations via goalforge-goal-changelog.sh. Idempotent: re-run on unchanged decomposition is a byte-identical no-op. TRIGGER: /goalforge-redecompose <feature-dir> --learning '<text>' or when goalforge-run loops back on a learning event.

★ 0
Truncuso
Truncuso/cogwright

prototype

goalforge-internal — use entry commands; do not auto-trigger Throwaway spike answering exactly ONE design question with runnable code — logic branch (pure logic module + interactive terminal harness, LOGIC.md), UI branch (several radically different variations, UI.md), or perf branch (benchmark study of rival implementations with a scaling curve, PERF.md). Keep the answer, delete the code. Use when an open question is of kind "how should it behave / which approach wins / how should it look / is it fast enough, does it scale, is the optimization worth it" and more interviewing or reading will not settle it — a spike will. Entry points: handoff mode `prototype` (cross-session dispatch seam), goalforge-harden open-question routing, idea-refine, or the user saying "spike this" / "quick prototype to check" / "benchmark this". Refuses to start without a single question AND explicit success criteria.

★ 0