Four approaches, and one more
| Approach | Examples | Source of truth | What it does well | What it leaves open |
|---|---|---|---|---|
| Spec-driven frameworks | GitHub Spec Kit, BMAD-METHOD, OpenSpec, Kiro | Written specs per feature or project | Replaces throwaway chat prompts with durable, structured specs that guide coding agents | Specs are usually scoped to one feature or project rather than a domain model that grows with every release |
| Context platforms | Augment | The existing codebase | Deep, persistent understanding of large codebases across sessions | Works forward from the code as it is, without a separate model of what the business intends |
| Architecture & modelling tools | C4 tooling, enterprise-architecture platforms | Diagrams and architecture documentation | Clear models of systems, boundaries and dependencies for people | Typically not connected to the delivery pipeline or queried by coding agents |
| Convention-driven tools | Agent OS | Conventions extracted from the code | Keeps agents consistent with a team’s existing standards | Does not aim to keep a standing model of business intent |
| Connected delivery system | M1Spec | One persistent model: domain, event model, contracts, architecture, decisions | Carries intent from the business story to the merged pull request, with the agent building from that model | Asks teams to work from a shared model — a change in how they work, not just a new tool |
Based on each product’s public documentation and positioning as of October 2026. Tools change quickly — if something here is out of date, tell us and we will correct it.
Complementary, not either-or
M1Spec works with your coding assistant
M1Spec doesn’t replace Claude Code or GitHub Copilot — its agent drives the assistant you already use, task by task, in your own repository.
It keeps what the others produce in one place
Specs, architecture and conventions are all valuable. M1Spec’s job is to keep them connected to each other and to the business intent behind them.
Check your own setup
Answer five questions about the tools and process you use today. Nothing leaves your browser.
