For a project that already exists
Already built it? Start here.
Describe your project and give the inspection prompt to your coding agent. Bring back its report to identify open decisions, reported gaps, and evidence that needs checking.
Reviewed this project before?
Start with the previous project brief
Upload the previous agent-directive.json — the structured build rules. We carry forward your confirmed boundaries and show what changed.
2 / Ask your coding agent
Check the project without changing it
Using an MCP-capable coding agent?
Connect the hosted endpoint once, then the agent can request the checklist and return the sanitized assessment directly. No account or API key is required.
https://agentdirective.org/mcpExactly what the agent may return
Accepted: relative file paths, test names and outcomes, telemetry names, short implementation summaries, and limitations.
Do not submit source code, file contents, secrets, credentials, personal or customer data, production records, absolute paths, or repository URLs.
3 / Send the assessment
Paste or choose your agent’s JSON
Review it first. We screen for likely secrets and reject absolute file paths.
Existing project assessment
What is supported, missing, or still unknown
The findings compare your agent's report with the evidence expected by the matched Control Packs.
Prioritized findings
Decisions only you can make
Hand the next step to your coding agent
This prompt is built from the reported gaps. It tells the agent to ask you before choosing any open boundary.
Understanding this report
What this report does not prove