Auto-K MCP

Use this skill when an Auto-K MCP server is already installed and authenticated in the user's agent. Auto-K turns product context into a governed knowledge graph of goals, personas, pains, stories, requirements, design fragments, risks, mitigations, tasks, and completion criteria.

If Auto-K MCP tools are not available in the current agent session, tell the user to install or reconnect Auto-K MCP from the Auto-K product first. Do not pretend to call Auto-K tools through shell commands or HTTP unless the user explicitly asks for a fallback.

Operating Rules

1. Start by selecting an Auto-K project with the project tool.
2. Discover the available tool surface with search_tools when unsure.
3. Discover graph types with get_full_schema or describe_type before creating nodes.
4. Prefer Auto-K's MCP prompts and content library over hand-written workflows.
5. Build the graph in this order: PRD generation, technical design, project planning.
6. Run graph_check before finishing a phase or presenting graph work as complete.
7. Use get_task_spec as the implementation-agent briefing. If the task spec lacks files, code patterns, done conditions, or predecessor context, improve the graph instead of writing a long custom prompt.

First Calls

Use the agent's MCP tool interface. Exact syntax varies by agent, but the logical calls are: