Packages

development-driven-specs — the dds toolchain (protocol 2) as a Mix task. A thin shim over the bundled instruments (Python, stdlib); never a port.

Current section

Files

Jump to
dds priv toolchain canon CLAUDE.md
Raw

priv/toolchain/canon/CLAUDE.md

# Claude Code
This file exists so Claude Code finds it; the canonical instructions
for any LLM agent working in this repository are in
[AGENTS.md](AGENTS.md). Read that first.
## Claude-Code-specific
The development-driven-specs skills are provided by the **`dds`
package** (installed via APM), not committed into this repository. Once
installed they are available, all prefixed `dds-`:
- `/dds-upgrade`**owns the framework version**: installs the discipline
canon, reconciles it against upstream updates, and firmly enforces the
structure (reshaping artifacts to conform; never altering content).
- `/dds-sync`**surveys the code** (per the carried witnessing procedure) to identify what must be
documented and decided, and writes stub artifacts with every gap
marked; a human fills them. It detects and scaffolds, never invents.
- `/dds-prep-merge` — prepare the branch for merge (the executable form
of the [Prep-merge procedure](AGENTS.md#prep-merge-procedure)).
Run `/dds-upgrade` first (it installs the framework and runs its
migrations), then `/dds-sync` to populate against it; `/dds-check`
is the read-only verdict for CI.
The docs under `docs/` *are* committed here and owned by this
repository — the skills scaffold and conserve them; they do not own
them, and never author their content.
Project-local Claude Code state (`.claude/settings.local.json`,
`.claude/state/`, `.claude/cache/`) remains local-only via `.gitignore`.