Plan with features, decisions and relationships
Define features with acceptance criteria, record the decisions behind them, and link everything across your spec graph. All of it queryable by AI agents over MCP.
Features, decisions and relationships, all connected
Features
Define features with acceptance criteria, user stories, priority and status. Capture what each piece of work does and how you will know it is done.
Acceptance criteria and user stories
Spell out the behaviour you expect in plain language. Acceptance criteria and user stories keep features grounded in what users actually need.
Architecture Decision Records
Capture the why behind every technical choice. Context, decision, consequences and alternatives considered, all in one place.
Cross-entity relationships
Link features to tests, ADRs to solution designs, and entities to one another. Navigate your spec graph and never lose traceability.
Priority and status
Set priority and status on each feature so the team can see what matters now and where each piece of work has got to.
Queryable by agents
AI coding agents fetch features and decisions over MCP with list_features and list_decisions before writing code, so they build what you actually designed.
Use cases
Platform migration
Record the features, decisions and tests involved in moving from one stack to another, and link them so nothing gets lost.
Planning the next build
Define features with acceptance criteria, set priority and status, and share the plan with stakeholders through the client portal.
Compliance and audits
Every architecture decision has context, alternatives and consequences, ready for audit review.
Onboarding new engineers
New team members read the ADRs to understand why things are built the way they are. No tribal knowledge required.