Start

You are about to adopt a discipline, not install a tool. You plan the work in documents, do it in bounded steps, and keep the record as you go—so the AI writes the code while you keep architectural authority and genuine understanding. Walk the chain once and you have the shape of every project that follows.

First steps

1. Install the skills. They are Claude-Code-native collaborators, one per conversation in the chain; with them installed the practice runs from inside your editor. (the catalog · source on GitHub)
2. Run Kamae 1 to develop a seed. The seed is your project's opinions written down—what it is, who it's for, the shape you have in mind—before any code exists.
3. Follow the chain. Kamae 2 turns opinions into decisions, 3 into a README that fixes scope, 4 into an ordered sequence of steps. Each one narrows what is still possible, so the last document is easy to write.
4. Open your first ho. Kamae 5 authors it: one bounded, verified, recorded step—small enough to pick up and finish in a single session.
5. Keep the record. Each ho closes on the record; a superseded step is never erased, only marked. The arc of your project is that record, moving forward only.

The document templates are tool-agnostic and ready to use—download the raw Markdown and the skills author into them. Self-directed guides are taking shape in the repo alongside them.

That is the whole on-ramp. When you want the named parts in depth, they are one door over: the framework and the skills.