spec_coding_requirements_confirmed
Confirm completion of requirements gathering and transition to the design phase in spec-driven development workflows.
Instructions
Confirm the completion of requirements collection and proceed to the design phase
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | Session identifier | |
| feature_name | Yes | Feature name |
Implementation Reference
- src/tools/requirements_confirmed.ts:6-36 (handler)The main execution logic for the tool, confirming requirements and returning a markdown progress update with next steps.
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`; } - src/server.ts:78-94 (schema)MCP protocol input schema definition for the tool, used for validation and listing.
{ 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)Registration in the tool call handler switch statement, mapping tool name to the handler function.
case 'spec_coding_requirements_confirmed': result = await requirementsConfirmed(args as any); break; - TypeScript type definition for handler input parameters.
export interface RequirementsConfirmedParams { session_id: string; feature_name: string; }