Stats
Actions
Tags
From scaffold
Dispatch a milestone build end-to-end (drives /milestone via the milestone-workflow skill)
How this command is triggered — by the user, by Claude, or both
Slash command
/scaffold:goal <milestone-name> [notes]fableThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Drive the milestone named in `$ARGUMENTS` to completion. 1. Identify the target (first token of `$ARGUMENTS`). Open the matching milestone command and its playbook at `docs/playbooks/<target>.md`. If the target is ambiguous or absent, ask which milestone — do not guess. 2. Read first: `CLAUDE.md`, `docs/decisions/`, then the playbook and the specs it cites. Load the relevant skills and say which. 3. Follow the `milestone-workflow` skill: restate goal + gate, check preconditions, work the ordered workstreams, capture forward-looking data per the project's capture plan, self-v...
Drive the milestone named in $ARGUMENTS to completion.
$ARGUMENTS). Open the matching milestone
command and its playbook at docs/playbooks/<target>.md. If the target is
ambiguous or absent, ask which milestone — do not guess.CLAUDE.md, docs/decisions/, then the playbook and the specs it
cites. Load the relevant skills and say which.milestone-workflow skill: restate goal + gate, check
preconditions, work the ordered workstreams, capture forward-looking data per
the project's capture plan, self-verify, update context in the same PR.Treat the remaining text in $ARGUMENTS as scoping notes for this run.
npx claudepluginhub mrinaldhillon/claude-skills --plugin scaffold/goalExtract a full task specification up front (goal, constraints, definition of done), then execute — the primary documented lever for Opus 4.8 long-horizon quality.