Cadence
Appearance is cheap. Verification is the work.
Cadence is a Claude Code plugin for a single developer who expects to maintain the software after the session ends. It keeps the project’s decisions, plans and results in the repository, where the next session can find them.
This guide follows the work: start a project, settle a phase, build it and check what it delivered. Testing has its own section because deciding when to stop is part of the job. The configuration reference is there when you need to change how Cadence behaves.
If you’re new to Cadence, start with installation. If it’s already installed, start or adopt a project.
Find what you need
| If you want to… | Start here |
|---|---|
| Work through a phase | Plan and execute |
| Keep testing proportionate | Bound the testing effort |
| Change a setting | Configuration |
| Look up a command | Command reference |
| Understand access and publishing | Permissions and data |
| See what the controls can establish | Controls and their limits |
This guide describes Cadence 3.11.0. The full contents are also readable on GitHub.