Skip to main content
Glama
kevinlin

Spec-driven Development MCP Server

by kevinlin

spec_coding_workflow_start

Initiate structured development by collecting project goals and requirements to guide subsequent specification, design, and implementation phases.

Instructions

Start the specs workflow and begin the goal collection phase

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function implementing the tool logic: generates a unique session ID, loads the 'ask-goal.md' template, and returns the formatted workflow start message with stage information and instructions.
    export async function workflowStart(): Promise<string> { const session_id = generateSessionId(); console.error(`[MCP] Starting workflow with session_id: ${session_id}`); // Use ask-goal.md template const template = await readTemplate('ask-goal.md', { session_id }); return `# πŸš€ Spec-driven Development Workflow Started ## Current Stage: Goal Collection (1/5) Welcome to the Spec-driven development workflow! I'll help you complete the entire development process from requirements to code. ### Workflow Overview: - [ ] 1. **Goal Collection** ← Current Stage - [ ] 2. Requirements Gathering - [ ] 3. Design Documentation - [ ] 4. Task Planning - [ ] 5. Task Execution --- ${template} --- **Session Information**: - Session ID: \`${session_id}\` **Important**: - Please discuss the feature goals with me thoroughly until the goals are completely clear - **Only when you explicitly confirm the goals can you call** \`spec_coding_goal_confirmed\` tool - **Never** call the next stage tool before the user **explicitly confirms the goals**`; }
  • src/server.ts:207-209 (registration)
    Registration of the tool handler in the switch statement that dispatches tool calls to the workflowStart function.
    case 'spec_coding_workflow_start': result = await workflowStart(); break;
  • Tool registration including the name, description, and input schema (empty since no input parameters are required).
    { name: 'spec_coding_workflow_start', description: 'Start the specs workflow and begin the goal collection phase', inputSchema: { type: 'object', properties: {}, required: [] } },
  • Workflow step definition that references the 'spec_coding_workflow_start' tool as part of the overall development workflow.
    { step_number: 1, name: STEP_NAMES.GOAL_CONFIRMATION, description: 'Clarify the feature development goal through conversation', tool: 'spec_coding_workflow_start β†’ spec_coding_goal_confirmed', deliverable: 'Clear feature goal and feature_name' },
  • src/server.ts:6-6 (registration)
    Import statement for the workflowStart handler function used by the tool.
    import { workflowStart } from './tools/workflow.js';

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kevinlin/spec-driven-dev-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server