Skip to main content
Glama
kevinlin

Spec-driven Development MCP Server

by kevinlin

spec_coding_requirements_confirmed

Confirm completion of requirements collection to transition from specification to design phase in structured development workflows.

Instructions

Confirm the completion of requirements collection and proceed to the design phase

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesSession identifier
feature_nameYesFeature name

Implementation Reference

  • The main handler function that confirms requirements completion, logs the event, and returns a markdown-formatted message advancing the workflow to the design phase.
    export async function requirementsConfirmed( params: RequirementsConfirmedParams ): Promise<string> { const { session_id, feature_name } = params; console.error(`[MCP] Requirements confirmed for feature: ${feature_name}`); return `# βœ… Requirements Gathering Completed ## Generated Requirements Document: πŸ“„ "docs/specs/${feature_name}/requirements.md" The requirements document contains complete user stories and EARS-format acceptance criteria. --- ## Next Stage: Design Document (3/5) ### Workflow Progress: - [x] 1. Goal Collection βœ… - [x] 2. **Requirements Gathering** βœ… - [ ] 3. **Design Document** ← Next Stage - [ ] 4. Task Planning - [ ] 5. Task Execution Now please call \`spec_coding_design_start\` to begin the technical design stage. **Session Information**: - Session ID: \`${session_id}\` - Feature Name: \`${feature_name}\` - Requirements: βœ… Completed`; }
  • Input schema definition for the tool, specifying session_id and feature_name as required string parameters.
    inputSchema: { type: 'object', properties: { session_id: { type: 'string', description: 'Session identifier' }, feature_name: { type: 'string', description: 'Feature name' } }, required: ['session_id', 'feature_name'] }
  • src/server.ts:78-95 (registration)
    Tool registration in the listTools response, including name, description, and input schema.
    { name: 'spec_coding_requirements_confirmed', description: 'Confirm the completion of requirements collection and proceed to the design phase', inputSchema: { type: 'object', properties: { session_id: { type: 'string', description: 'Session identifier' }, feature_name: { type: 'string', description: 'Feature name' } }, required: ['session_id', 'feature_name'] } },
  • src/server.ts:219-221 (registration)
    Switch case in callTool handler that invokes the requirementsConfirmed function for this tool name.
    case 'spec_coding_requirements_confirmed': result = await requirementsConfirmed(args as any); break;
  • TypeScript interface defining the input parameters for the handler function, matching the tool schema.
    export interface RequirementsConfirmedParams { session_id: string; feature_name: string; }

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