// Spec-driven graph of intent, constraints, decisions, and rationale. Provides MCP tools for querying, mutating, and verifying the IntentGraph for the current workspace.
| name | intentgraph |
| description | Spec-driven graph of intent, constraints, decisions, and rationale. Provides MCP tools for querying, mutating, and verifying the IntentGraph for the current workspace. |
| allowed-tools | ["graph.query","graph.get_node","graph.upsert_node","graph.upsert_edge","graph.delete","graph.diff_against_code","retrieval.search","task.create","task.lease","task.heartbeat","task.release","task.propose_patch","task.accept_patch","task.reject_patch","verify.run","trace.query"] |
| disable-model-invocation | false |
Activate this skill when the user asks about intents, constraints, decisions, drift, or wants to propose or verify a code change. The skill connects to the IntentGraph subprocess for the current workspace and exposes MCP tools listed above.
Default flow:
retrieval.search to find relevant intent/constraint/concept nodes for the user's request.graph.get_node to expand context for the top hits.task.create → task.lease → make edits in a shadow worktree → task.propose_patch → preview, then task.accept_patch or task.reject_patch.verify.run against affected obligations before accepting any patch.Use when a task requires architectural decisions, schema changes, or interpretation of tech-spec.md. Read-only — proposes ADR drafts, never writes code. The gate for anything load-bearing.
Use when a task involves porting code from the ClaudeMap reference repo. Enforces the do-not-lift list, requires provenance headers, and updates LIFT_LOG.md.
Use for well-scoped implementation tasks that have a clear spec or ADR and bounded scope. Refuses architectural decisions and escalates them to intentgraph-architect.
Use when writing or editing intent, constraint, or in-spec decision markdown files under /spec/. Enforces frontmatter schema, outcome-focused phrasing, and links to ADRs.
Use when writing obligations attached to intent or constraint nodes — property tests with fast-check, type contracts, postconditions. Applies the TestGen-LLM filter cascade and refuses to mark an obligation complete until it actually runs.