spec
Use when a request, or new wishes for a stored brief, issue or plan, leaves a product decision open: what counts as done, data, architecture or a trade-off. When a new visual surface does not name its
Files61
View on GitHubSKILL.mdskills/spec/SKILL.md
GitHubShaping
Steps
- Gate.
- First invoke every installed non-
exo:skill matching the request. - Spec always ends on a brief; with no open decision the brief still gets written.
- An open decision is one the user would notice that neither request nor code settles.
- Diff fits one sentence or code settles every point → no question, exo closes each choice; ask only what to build.
- Asked for options → per
references/architecture-sketch.md, no file.
- First invoke every installed non-
- Sort each point.
- Answerable by running or reading → record, never ask.
- Each open decision is a question, root first.
- A decision the user left open stays open despite code.
- Name the owning layer, a smaller alternative.
- Ask one at a time.
- Ask per
../route-skills/references/question.md; decide nothing silently. - Recommend a loaded skill's pattern over an option it rules out.
Land:→ plan approval approves only its mode; ask only ifshipisask.- No git repo or
origin→Land: local, no question. - Last answer → brief now, no recap, no yes question.
- Ask per
- Map, then locate.
- Run
node "${CLAUDE_SKILL_DIR}/scripts/repo-map.mjs", plan mode too. - Unmapped range →
exo:locate-code, at most eight, read none located; outside facts → oneexo:fetch-docsround, no gap-fill; both foreground, one message. - Never
cat,headorsed: dumps cost context.
- Run
- List tasks per
references/task-list.mdandreferences/brief.md. - Store it per
references/brief.md. - Check it. Run
node "${CLAUDE_SKILL_DIR}/scripts/plan-check.mjs" --plan <brief file> --root <checkout root> --loop; fix flagged lines, any missing heading,Data:, Success criterion or## Manual checks; read its output, never its source. - Find open points per
references/brief.md## Open points step; rerun step 7, leaving flagged## Open pointsunfixed. - Hand off per
references/hand-off.md.
References
| File | Read it when |
|---|---|
references/stored-brief.md |
Request names or extends a brief, issue or plan. |
../route-skills/references/question.md |
Each question and reply. |
references/brief.md |
Before writing the brief; step 8. |
references/task-list.md |
Before writing the task list. |
references/example-plan.md |
Once, before the first task. |
../build/references/data-migration.md |
When its first line applies. |
../build/references/test-design.md |
When its first line applies. |
../build/references/security.md |
When its first line applies. |
references/brief-in-an-issue.md |
specs is issues or both. |
../file-issues/references/fields.md |
Before creating that issue. |
references/architecture-sketch.md |
Two or more structural shapes compete. |
../../docs/principles/README.md |
Request adds or changes an AI agent or LLM worker, its prompt, tools or loop. |
references/hand-off.md |
Step 9. |
references/watching.md |
Step 9, run started. |
references/measured-goal.md |
Goal is a measured score, cost or time on a task set. |
Report: brief location and next stage, or question.