goalforge-speclisted
Install: claude install-skill Truncuso/cogwright
# goalforge-spec
Reads a captured feature overview, conducts a design pass, writes `spec.md`,
and advances the feature status from `draft` to `ready`. The `draft → ready`
transition is **human-gated**: the skill halts and asks for explicit approval
before changing any `status:` field.
**Full route only.** A `route: fast` feature (overview frontmatter, stamped by
`goalforge-capture`) has no `spec.md` by design — its single WP carries the complete
goal block. Invoking goalforge-spec on a fast feature is the deliberate promotion
path (the feature outgrew the fast route — e.g. 3+ WPs or a cross-WP
contract): author the spec retroactively and flip `route: full` with a note.
Schema reference: `${CLAUDE_PLUGIN_ROOT}/references/schema.md`.
Templates: `${CLAUDE_PLUGIN_ROOT}/references/templates/`.
## Unattended mode (`SDD_AUTONOMY=unattended`)
When `SDD_AUTONOMY=unattended` is set (the `autopilot` driver sets it), the
`draft → ready` sign-off has no human to grant it. **Do not call `AskUserQuestion`
to wait — PARK:** write the spec and the verbatim approval prompt to a handoff and
stop (the run resumes when a human approves, or on the next `/autopilot`); the
parked prompt is the gate block with the `grill` token stripped. The
status is **not** advanced autonomously — accepting a spec is a human commitment.
Spec *content* quality checks (personas/architect/judge) are evidence-decidable and
still run. See `~/.claude/skills/autopilot/references/autonomy-policy.md`. Unset
(`interacti