Setting the file. One moment.
Subchapter 23.29
references/spec-template.mdMarkdown2 KBView on GitHub
Do not put runtime instructions or full provenance tables here.
For tiny wording-only fixes, update SOURCES.md changelog instead.
| File | Purpose |
|---|---|
SKILL.md | runtime activation and execution |
SPEC.md | maintenance contract |
SOURCES.md | source inventory, decisions, gaps, changelog |
references/ | runtime-loadable depth |
references/evidence/ | persistent iteration examples |
# <Skill Name> Specification
## Intent
<1-2 short paragraphs>
## Scope
In scope:
- ...
Out of scope:
- ...
## Users And Trigger Context
- Primary users:
- Common user requests:
- Should not trigger for:
## Runtime Contract
- Required first actions:
- Required outputs:
- Non-negotiable constraints:
- Expected bundled files loaded at runtime:
## Source And Evidence Model
Authoritative sources:
- ...
Useful improvement sources:
- positive examples:
- negative examples:
- commit logs/changelogs:
- issue or PR feedback:
- validation results:
Data that must not be stored:
- secrets
- customer data
- private URLs or identifiers not needed for reproduction
## Reference Architecture
- `SKILL.md` contains:
- `references/` contains:
- `references/evidence/` contains:
- `scripts/` contains:
- `assets/` contains:
## Validation
- Lightweight validation:
- Deeper validation:
- Holdout examples:
- Acceptance gates:
## Known Limitations
- ...
## Maintenance Notes
- When to update `SKILL.md`:
- When to update `SOURCES.md`:
- When to update `references/evidence/`:SPEC.md concise.SOURCES.md or refs instead of duplicating them.references/evidence/.