Skip to main content
Glama
kevinlin

Spec-driven Development MCP Server

by kevinlin

spec_coding_goal_confirmed

Confirm feature goal completion and transition to requirements gathering phase in spec-driven development workflow.

Instructions

Confirm the completion of the feature goal, set the feature_name, and proceed to the requirements collection phase

Input Schema

NameRequiredDescriptionDefault
feature_nameYesFeature name generated based on the goal (e.g., user-auth)
goal_summaryYesBrief description of the feature goal
session_idYesSession identifier

Input Schema (JSON Schema)

{ "properties": { "feature_name": { "description": "Feature name generated based on the goal (e.g., user-auth)", "type": "string" }, "goal_summary": { "description": "Brief description of the feature goal", "type": "string" }, "session_id": { "description": "Session identifier", "type": "string" } }, "required": [ "session_id", "feature_name", "goal_summary" ], "type": "object" }

Implementation Reference

  • The `goalConfirmed` function implements the core logic of the `spec_coding_goal_confirmed` tool, confirming the feature goal and returning workflow advancement instructions.
    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}\``; }
  • Input schema definition for the `spec_coding_goal_confirmed` tool, defining parameters: session_id, feature_name, goal_summary.
    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, used for ListToolsRequestHandler.
    { 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 to the handler function in the CallToolRequestHandler switch statement.
    case 'spec_coding_goal_confirmed': result = await goalConfirmed(args as any); break;
  • TypeScript interface defining the input parameters for the handler function.
    export interface GoalConfirmedParams { session_id: string; feature_name: string; goal_summary: 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-coding-mcp'

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