Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Requirements Template | Template for creating feature requirements documents |
| Design Template | Template for creating technical design documents |
| Tasks Template | Template for creating task breakdown documents |
| Product Steering Document | Product vision and goals for the project |
| Tech Steering Document | Technical standards and conventions |
| Structure Steering Document | Project structure and organization guidelines |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spec-workflow-guide | Get the complete spec-driven development workflow guide. ALWAYS call this tool FIRST when user requests spec creation, feature development, or mentions working on specifications. This tool provides the essential workflow instructions and must be loaded before any spec work begins. |
| steering-guide | Get the complete guide for creating and managing steering documents. Use this ONLY when user explicitly requests steering documents or asks to create project architecture docs. NOT required for spec creation. |
| create-spec-doc | Create spec document. CRITICAL: Only creates ONE document at a time. You MUST get user review after EACH document before creating the next one. |
| spec-status | Show detailed status of a specification including phase completion and task progress |
| spec-list | List all specifications in the project with their status |
| create-steering-doc | Create a specific steering document (product.md, tech.md, or structure.md) with the provided content. Use ONLY when user explicitly requests steering document creation. NOT automatically required. |
| get-steering-context | Load steering documents (product.md, tech.md, structure.md) for project context. Only use if steering context is not already loaded. |
| get-spec-context | Load specification context documents (requirements.md, design.md, tasks.md) for a specific spec. CRITICAL: DO NOT use during active spec creation workflow if you just created the documents in this conversation. Only use when: 1) Starting fresh on existing spec, 2) Returning to work after conversation break, 3) Implementation phase on existing specs. |
| get-template-context | Load document templates for context optimization |
| manage-tasks | Task management for spec implementation. REQUIRED SEQUENCE: First mark task as in-progress, then implement, finally mark as completed. ALWAYS update status to in-progress before starting work. Implementation workflow: set-status (in-progress) → code → set-status (completed). Status markers: [] = pending, [-] = in-progress, [x] = completed |
| request-approval | Request human approval for a document or action. Creates an approval request that appears in the dashboard for user review. CRITICAL: Provide only the filePath parameter (the dashboard reads files directly). Including content in the request will cause approval system errors. |
| get-approval-status | Check the status of an approval request. Use this to poll for approval status changes. |
| delete-approval | Delete an approval request after it has been fully approved. Use this to clean up completed approvals and prevent codebase pollution. |
| refresh-tasks | Provides requirements.md, design.md, and tasks.md content along with comprehensive instructions for an AI agent to refresh the task list. The agent should analyze the documents and use create-spec-doc to recreate tasks.md with updated tasks that bridge the gap between current implementation and requirements. |