Intent Engineering
Wire an MCP server so your coding agent can audit, scaffold, and triage intent specifications against a fixed nine-section template before you ship agent behavior.
Overview
com.seanwinslow/intent-engineering is a MCP server for the Build phase that audits, scaffolds, and triages agent intent specs against a nine-section template.
What is this MCP server?
- Audit existing agent intent specs against a nine-section template
- Scaffold new intent documents from the same template
- Triage gaps and inconsistencies before implementation
- stdio npm package @swins/intent-engineering-mcp v0.1.1
- GitHub-hosted MCP server for local agent configuration
- Nine-section intent template
- Server version 0.1.1
- Transport: stdio via npm @swins/intent-engineering-mcp
What problem does it solve?
Agent projects drift when intent lives in chat history instead of a structured spec you can review and reuse.
Who is it for?
Solo builders defining or refactoring custom agents who want template-driven intent docs inside their existing MCP-enabled workflow.
Skip if: Teams that only need a single chat prompt with no formal agent spec, or builders not using MCP at all.
What do I get? / Deliverables
After you register the server, your agent can produce and check nine-section intent specs so implementation and reviews align on the same document.
- Scaffolded nine-section agent intent spec
- Audit report against the template
- Triage notes on gaps or conflicts in intent
Recommended MCP Servers
Journey fit
Intent specs are operational artifacts for agents you are building; the canonical shelf is build agent-tooling even though you may start drafting during validate. Agent-tooling is where MCP servers extend Claude Code, Cursor, or Codex with structured intent-engineering workflows rather than one-off scripts.
How it compares
MCP intent-spec tooling, not a bundled Claude skill or a hosted no-code agent builder.
Common Questions / FAQ
Who is com.seanwinslow/intent-engineering for?
Indie and solo developers building MCP-connected agents who want standardized intent documents before coding tools and policies.
When should I use com.seanwinslow/intent-engineering?
Use it when starting a new agent, auditing an existing intent file, or triaging unclear requirements against the nine-section template.
How do I add com.seanwinslow/intent-engineering to my agent?
Install @swins/intent-engineering-mcp from npm, add a stdio MCP entry pointing at that package in Claude Code, Cursor, or Codex, then restart the client so tools appear.