The project methodology graph for AI agents
Your agent describes a project and gets a route from presale to closure, a decision at every gate and a check of its own plan. It all rests on linked practices from PMBOK®, PRINCE2®, Scrum, Kanban, BABOK® and systems analysis, and every answer names the rule behind it.
agile-today.org/api/mcpCustom software, hybrid delivery, complex scope, fixed price. Everything is ready except a discovery. Can we commit?
check_gate { gate: "g.g1", context: { dom: "software", ap: "hybrid", unc: "complex", con: "fixed" }, evidence: { … } … }
Do not enter the next stage until the evidence exists.
- Where is “Paid discovery report”? It is required for G1 · Commit. It cannot be waived at this gate.
- Solution outlinepresent
- Estimate (range)present
- Assumptions and exclusions logpresent
- Proposalpresent
- Contract / statement of workpresent
- Paid discovery reportmissing
- Risk register (RAID)present
Why
Ask a model twice, get two different answers
Language models know PMBOK® and Scrum, but answer the same question differently every time. A project needs decisions that can be repeated, explained and defended — so Agile Today gives the agent rules instead of recollections.
Reproducible
The same input on the same graph version always gives the same verdict — no sampling, no drift.
Traceable
Each answer carries the rule that fired, link ids and the source of every concept, so any decision can be checked.
Built for agents
One MCP endpoint, 8 read-only tools, one response envelope and suggestions on typos.
Mission
Help AI agents run projects by rules, not by a model's memory — and show people the rule, the link and the source behind every recommendation.
- A gate assesses evidence; it does not block work.
- A waiver always has a reason.
- Stale critical evidence means “not ready”.
- Every decision can be cited by its rule and link id.
- The project context decides, not school membership.
- Neutral: no methodology is the default.
Verdicts are recommendations; people decide. More about the project
How it works
From the first call to closure
10 stages and 11 gates, from presale to benefits. For each stage: what to do, what to avoid and what the gate will check.
Describe the project
Type, approach, uncertainty, contract, scale, size and 12 flags such as migration, regulation or shared people.
Get the route
For each stage: the events, the core practices with the reason, what to avoid and the evidence each gate needs.
Pass the gates
Give the evidence you have. Get Go, Conditional go, Hold, Recycle or Stop — with the rule that fired and the questions to ask.
- 01PresaleG0Bid / no-bidG1Commit
- 02Initiation and kickoffG2Launch
- 03DiscoveryG3Scope baseline
- 04AnalysisG4Requirements ready
- 05Design and planningG5Design and plan approved
- 06BuildG6Test readiness
- 07Verification and acceptanceG7Acceptance
- 08Release and go-liveG8Go / no-go
- 09Hypercare and handoverG9Handover
- 10Closure and benefitsG10Closure
What's inside
One graph instead of a shelf of standards
Practices, events, artifacts, gates and antipatterns of the leading schools — from PMBOK® and PRINCE2® to Scrum, Kanban and BABOK® — linked to each other. Every node has a description, conditions of use and a source.
a standard or body of knowledge · 134
an established practice with a named author · 173
an editorial statement by Agile Today, marked as such · 118
Schools and bodies of knowledge
Details
Worth knowing before you connect
How a gate decides, what “core” means, what this is not, what happens to your data and what it costs.
How a gate decidesStop › Recycle › Hold › Conditional › Go
- Stop — the business case no longer holds.
- Recycle — an earlier stage is no longer true; the answer names the stage to return to.
- Hold — critical evidence is missing, stale or cannot be waived.
- Conditional go — required, non-critical evidence is missing, or a waiver lacks its reason or approver.
- Go — everything required is present and current, or waived with a reason and an approver; optional gaps become notes.
Modifiers on any outcome: work started without the gate, evidence overdue, stale or waived. The answer carries the rule (R1–R5), the evidence behind it and the questions to ask.
What “core” means≤ 8 per stage
Core means “do it here”. An item is core only when the context calls for it (a rule or a flag) or when it produces an artifact the stage's gate treats as critical. Belonging to a school gives at most “recommended”. At most eight core work items per stage.
What it is not
- Not a task tracker or a replacement for your PM tools.
- Not an autopilot: a verdict is a recommendation; the gate's decider decides.
- Not a copy of the standards: concepts are named and linked to their source; standards' texts are not reproduced.
What happens to your datanothing is stored
The server is stateless: the project context and evidence you send are used only to answer. Answers are deterministic. No accounts, no cookies, no analytics. Privacy
Plansbeta — free
- Beta — free, no account, within fair use.
- Pilot — your organisation's own methodology on top of the graph, for integrators and PMOs. Planned.
- Team / Enterprise — saved projects, a gate decision log, a private endpoint. Planned.
Get started
Three ways to start
Connect your agent in 60 seconds
A remote read-only server, no key during the beta.
- Claude — Settings → Connectors → Add custom connector → paste the URL.
- Claude Code — one command:
claude mcp add --transport http agile-today https://agile-today.org/api/mcp - Cursor, VS Code — add the URL in the MCP settings; config examples are on the connect page.
Plan a project
Describe a project in a form and get the route stage by stage — no agent needed, right in the browser.
Explore the graph
425 nodes with conditions of use, sources and links: practices, events, artifacts, gates and antipatterns.
Already know which evidence is ready? Check a gate