Lightweight intent-alignment plugin for coding agents: requirement-analysis playbook, three-level intent funnel with file-in-the-loop persistence, optional red-blue review skill (DingTalk group channel lives in the intent-gate-service sister service)
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"intent-gate-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# intent-gate **English** | [简体中文](README.zh-CN.md) [](LICENSE) [](https://www.python.org/) [](https://modelcontextprotocol.io/) [](https://pypi.org/project/intent-gate-mcp/) **Stop AI coding agents from guessing.** Complex business requirements. A thin or sloppy PRD. No legacy code to reference. That is exactly where coding agents start inventing: "happy path only, no failure flow", "idempotency with no server-side design" — gaps get silently filled with plausible-looking guesses, and you find out far too late. intent-gate moves intent alignment **before** coding, into the requirement-analysis stage: a PRD goes through an intent-confidence gate → gaps are resolved through a three-level funnel → the output is technically annotated Mermaid contracts (state machines / sequence diagrams / decision tables) → a mechanical lint gate must reach zero CRITICAL → only then is coding allowed to begin. It runs as an **MCP server (stdio subprocess)** — plug-and-play with Claude Code and other MCP clients. **No daemon, no credentials, zero config** — full workflow out of the box. ## Where it sits in a vibe-coding workflow intent-gate owns exactly one stage of the pipeline, the requirement-analysis stage: ``` PRD ──▶ [ intent-gate: confidence gate → intent alignment → Mermaid contracts ] ──▶ summary.md (every edge technically annotated, lint CRITICAL = 0) ──▶ coding agent (Claude Code / Cursor / any agent) ──▶ tests ──▶ ship ``` The leverage is asymmetric: **if the contracts land well, the coding stage is a free win** — every edge, step and rule already has a home, so any competent agent can implement the spec. That is why intent-gate deliberately does NOT touch coding, review or deployment: downstream agents a…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.