docs

Everything, in one place.

Start with install, learn the DAIC loop and the gates that enforce it, then reach for the reference pages when you need the exact tool surface. For the workflows themselves, see the protocols overview.

There are three groups below, and they answer three different questions.

Getting started is the shortest path from nothing to a working setup. Add the marketplace, install the plugin, run init. Your team picks it up from a single committed file, so nobody has to be talked through it. If you are new here, read this group and come back for the rest later.

Concepts explains why it behaves the way it does. DAIC is the loop everything else hangs off — discuss before you build, with hooks that hold the line rather than asking politely. Around it sit the pieces that make a long session survivable: what happens when context runs out, when a test is worth writing first, what the spec gate checks before work can be called done, how knowledge accumulates instead of being re-derived every morning, and how to change any of it when the defaults do not suit you.

Reference is what you open with a specific question in mind. The exact tool surface, the functions you can wire into a step, how issues move between the engine and your tracker, and how a second or third model joins the work.

Read them in that order the first time. After that, most people live in Reference.