Spec-driven Development MCP Server

export interface RequirementsConfirmedParams { session_id: string; feature_name: string; } 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`; }