Appendix I: Templates
Status: drafted · Time: 8 min · Audience: everyone Outcome: Find the right template for the artefact you are about to create.
Eight ready-to-fork templates. Each is a working starting point. Copy the template into your repository or working folder, fill in the placeholders, and ship.
The templates pair with specific chapters that explain the why and the discipline. Use the chapter for context; use the template for the artefact.
Which template do I need?
Section titled “Which template do I need?”| You want to | Open this template | The chapter that explains it |
|---|---|---|
| Add a CLAUDE.md to a single service or repo | CLAUDE-md-service | G.3 |
| Add a CLAUDE.md to a monorepo root | CLAUDE-md-monorepo | G.4 |
| Add a personal CLAUDE.local.md (gitignored) | CLAUDE-local-md | G.5 |
| Author your first SKILL.md | SKILL-md-minimum | G.7 |
| Author a SKILL.md with progressive disclosure | SKILL-md-full | G.7 and B.7 |
| Write an AI RFC | RFC-template | B.14 and C.3 |
| Write a retro (Quest, Boss Fight, or Embedded Sprint) | retro-template | The relevant belt’s quest or boss-fight chapter |
| Stand up a minimum viable wiki | minimum-viable-wiki-seed | Prologue §0.7 and Appendix N.7 |
How the templates are written
Section titled “How the templates are written”Every template has three sections.
Header. What the template is for, when to use it, and what to fill in. Read this first; it tells you whether you have the right template.
Template body. The actual artefact, with placeholders in <!-- comment --> blocks. Replace each placeholder with your content. Comments that should not appear in the final artefact start with <!-- DELETE -->.
Worked example. A populated version of the template below the body. Use it as a calibration check: if your artefact looks roughly like the worked example, you have used the template correctly.
Conventions
Section titled “Conventions”The templates use the following conventions consistently.
- Placeholder format.
<!-- replace this with ... -->for content the user fills in.<!-- DELETE -->for instructional comments that should be removed before shipping. - Voice. The template is written from the perspective of the person filling it in. The worked example is written from the perspective of someone reading the populated artefact.
- Length guidance. Each template indicates the approximate target length. Real artefacts vary; the guidance is for calibration, not enforcement.
- Cross-references. Templates point at the chapter where the discipline is explained. They do not duplicate the discipline; the template is the artefact, the chapter is the rationale.
Maintenance
Section titled “Maintenance”Templates are revised as the curriculum evolves. When a chapter changes its discipline (e.g., the RFC chapter adds a new required section), the corresponding template is updated in the same revision. The revision history is tracked in the file’s updated front-matter and in the playbook changelog.
Pull requests welcome. The templates are most useful when many builders use them; feedback from real use shapes the next revision.
See also: Appendix N.7 — The minimum viable wiki, the deeper treatment of the wiki seed template; Appendix C — Skills Library, the catalogue of skills that the SKILL.md templates produce.
Templates: CLAUDE-md-service · CLAUDE-md-monorepo · CLAUDE-local-md · SKILL-md-minimum · SKILL-md-full · RFC-template · retro-template · minimum-viable-wiki-seed