spec_coding_goal_confirmed
Confirm feature goal completion and transition to requirements collection phase in spec-driven development workflows.
Instructions
Confirm the completion of the feature goal, set the feature_name, and proceed to the requirements collection phase
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | Session identifier | |
| feature_name | Yes | Feature name generated based on the goal (e.g., user-auth) | |
| goal_summary | Yes | Brief description of the feature goal |
Implementation Reference
- src/tools/goal.ts:7-34 (handler)The main handler function implementing the logic for the 'spec_coding_goal_confirmed' tool. It destructures input params, logs confirmation, and returns a markdown-formatted response updating workflow progress and prompting next step.
export async function goalConfirmed(params: GoalConfirmedParams): Promise<string> { const { session_id, feature_name, goal_summary } = params; console.error(`[MCP] Goal confirmed for session ${session_id} with feature: ${feature_name}`); return `# ✅ Feature Goal Confirmed ## Confirmed Feature Goal: - **Feature Name**: \`${feature_name}\` - **Feature Description**: ${goal_summary} - **Project Directory**: \`docs/specs/${feature_name}/\` --- ## Next Stage: Requirements Gathering (2/5) ### Workflow Progress: - [x] 1. **Goal Collection** ✅ - [ ] 2. **Requirements Gathering** ← Next Stage - [ ] 3. Design Documentation - [ ] 4. Task Planning - [ ] 5. Task Execution Now please call \`spec_coding_requirements_start\` to begin detailed requirements gathering. **Session Information**: - Session ID: \`${session_id}\` - Feature Name: \`${feature_name}\``; } - src/tools/goal.ts:1-5 (schema)TypeScript interface defining the expected input parameters for the goalConfirmed handler, matching the MCP tool schema.
export interface GoalConfirmedParams { session_id: string; feature_name: string; goal_summary: string; } - src/server.ts:38-59 (schema)MCP tool definition including name, description, and input schema for 'spec_coding_goal_confirmed', used in the listTools response.
{ name: 'spec_coding_goal_confirmed', description: 'Confirm the completion of the feature goal, set the feature_name, and proceed to the requirements collection phase', inputSchema: { type: 'object', properties: { session_id: { type: 'string', description: 'Session identifier' }, feature_name: { type: 'string', description: 'Feature name generated based on the goal (e.g., user-auth)' }, goal_summary: { type: 'string', description: 'Brief description of the feature goal' } }, required: ['session_id', 'feature_name', 'goal_summary'] } }, - src/server.ts:38-59 (registration)Registration of the tool in the tools array returned by listTools handler.
{ name: 'spec_coding_goal_confirmed', description: 'Confirm the completion of the feature goal, set the feature_name, and proceed to the requirements collection phase', inputSchema: { type: 'object', properties: { session_id: { type: 'string', description: 'Session identifier' }, feature_name: { type: 'string', description: 'Feature name generated based on the goal (e.g., user-auth)' }, goal_summary: { type: 'string', description: 'Brief description of the feature goal' } }, required: ['session_id', 'feature_name', 'goal_summary'] } }, - src/server.ts:211-213 (registration)Dispatch registration in the callTool request handler switch statement, mapping tool name to the goalConfirmed function.
case 'spec_coding_goal_confirmed': result = await goalConfirmed(args as any); break;