The spec lifecycle
Agentissimo is spec-driven by default. Every change — feature, fix, even a typo — flows through one lifecycle. The lifecycle is the product: it is what turns an agent’s work into a reviewed, documented, mergeable change.
The framework is pluggable. OpenSpec is the first; others follow behind a common adapter.
The phases
Section titled “The phases”- Propose — write the proposal, design, and tasks. What and why, then how, then the steps. Approve the artifacts before any code is written.
- Apply — implement the tasks. All code changes happen here, each commit scoped to the change name.
- Verify — run tests, type checks, and a smoke pass. Confirm the implementation matches the proposal; document any deviation.
- Archive — promote the spec delta into the live spec, record the change, and land the archive commit on the same branch as the implementation.
- PR — push the branch and open one pull request covering the whole change.
Why a spec, not just a diff
Section titled “Why a spec, not just a diff”A bare diff loses the why. The lifecycle keeps the proposal, the implementation, and the historical record landing together — so the next person, agent or human, can see not just what changed but the decision behind it.
Artifacts
Section titled “Artifacts”Each change carries a proposal.md, a design.md, a tasks.md, and (when
behaviour changes) spec deltas. Apply works against the delta; archive promotes
it into the canonical spec for you.