Doctrine Packs
A doctrine pack is a bundle of related built-in doctrine artifacts (paradigm, tactics, styleguide, directive, template fragment, skill, and docs) that a project can activate as a unit through charter selection.
This page is specifically about built-in doctrine packs — the ones that ship with Spec Kitty itself (SPDD today). If you're looking to author and distribute your own pack across multiple projects, that's a different mechanism: see How to Create an Org Doctrine Pack.
Doctrine packs are opt-in. Projects that do not select a pack see no behavior change. Projects that do select a pack receive guidance scoped to the workflow action they are running.
Charter selection happens during the governance setup workflow. To verify which doctrine is active for the current project, run:
spec-kitty charter context --action specify --json
Optional doctrine packs
| Pack | Summary |
|---|---|
| SPDD and the REASONS Canvas | Structured-Prompt-Driven Development with a seven-section change-intent canvas. For high-risk and multi-WP missions where a clear change boundary reduces drift. Code remains the source of truth for current behavior; the canvas records approved intent. |
See also
- How to set up project governance
- How to Create an Org Doctrine Pack — for a project-authored, shareable pack instead of these built-in ones.