Template for a project's own spec skill — what the system does: definition, actors and capabilities, domains with states and transitions, cross-domain rules, flows and glossary. Materialized once per project as <project>-spec and owned by that project from then on.
pnpm add -D @turystack/spec-template
turystack skills --claude --skills spec --project acmeThat materializes .claude/skills/acme-spec/, substituting the project's name.
It is never overwritten by a later install: the shape came from here, the
content belongs to the project.
- Overview
- Definition — what the project is
- Domains — what exists and how it changes
- Rules — the ones that cross domains
- Flows — end to end, across domains
- Glossary — one term, one meaning
- Filling — how this skill grows
- Board — the work this spec turns into
- Skill manifest
Each one has a Shape half (from this template, kept) and a project half
(starts with <!-- turystack:unfilled -->). The marker is machine-readable:
turystack-proof reports an unfilled section that a task depends on as a missing
input, so "the spec is silent" is a gate result rather than an opinion.