Documentation

The documentation has four tiers.

The assessment looks at spec-driven development as practiced today: what it gets right, where its process shape causes problems, and what the history of these ideas actually says.

The method explains each part of aigile in plain language, with worked examples: the loop, the document layers, the constitution, how to handle deviations and drift, validation, and the authority matrix. Each page links to the deep-dive paper that covers the same ground in full depth.

The tutorials take you from installation to a first completed feature, one per tooling path (SpecKit, Claude Code, OpenSpec), all on the same small example so the paths can be compared directly.

The papers are the canonical documents: the working paper and eight deep dives. Where a method page and a paper differ, the papers take precedence. All documents are versioned and available on the downloads page.

A glossary defines every term of the method in one sentence and links each group to its full treatment; it is the page to keep open while reading anything else.

If you are new to the method, a reasonable path is to read the assessment first, then the method pages in order, then run one of the tutorials hands on, and read the working paper when you want the complete picture.