How it works

A fixed main chain: brainstorming and project shaping → research and architecture selection → requirements and specs → one feature at a time, tests first → layered testing → independent review → convergence and lessons learned. Each step calls its designated skill; no step is skipped.

Every claim of completion traces back to real artifacts, call records, hashes, gates and exit codes. A step without evidence is shown as "unverified" and does not count as done.

Human gates appear at these points: confirming the project shape, choosing a design, review disputes and risk acceptance, release and rollback. Ordinary tasks do not interrupt you.

When the host session ends or you go offline, the plugin does not claim it is "still running in the background"; next time you open it, it continues from the recorded recovery point.