Structured Workflow MCP

Instructions

Implementation Reference

• src/index.ts:210-223 (handler)

  Dispatch handler in main server that catches calls to 'question_determine_guidance' and invokes handlePhaseGuidance(name, sessionManager)
  case 'setup_guidance': case 'audit_inventory_guidance': case 'compare_analyze_guidance': case 'question_determine_guidance': case 'refactor_guidance': case 'lint_guidance': case 'iterate_guidance': case 'present_guidance': return { content: [{ type: 'text', text: JSON.stringify(await handlePhaseGuidance(name, sessionManager), null, 2) }] };
• src/tools/phaseGuidance.ts:22-25 (schema)

  Tool schema definition: name, description, and empty input schema
  { name: 'question_determine_guidance', description: 'Get guidance for the QUESTION_DETERMINE phase - clarify and finalize plan', inputSchema: { type: 'object', properties: {} }
• src/index.ts:146-146 (registration)

  Registration of phase guidance tools including 'question_determine_guidance' via createPhaseGuidanceTools()
  ...createPhaseGuidanceTools(), // Handles both suggestive and directive modes
• src/tools/phaseGuidance.ts:52-65 (handler)

  Core handler function that routes to suggestive or directive guidance based on session mode
  export async function handlePhaseGuidance( phaseName: string, sessionManager: SessionManager ): Promise<PhaseGuidance> { const session = sessionManager.getSession(); const isDirectiveMode = session?.workflowConfig !== undefined; // Route to appropriate guidance based on mode if (isDirectiveMode) { return getDirectiveGuidance(phaseName, sessionManager); } else { return getSuggestiveGuidance(phaseName, sessionManager); } }
• src/tools/phaseGuidance.ts:188-233 (handler)

  Specific guidance logic returned for 'question_determine_guidance' in suggestive mode (similar detailed block exists for directive mode at lines 868-1017)
  question_determine_guidance: { phase: 'QUESTION_DETERMINE', objective: 'Clarify any ambiguities AND determine your final implementation plan', instructions: [ '--- QUESTION PHASE (Clarification) ---', 'Review your understanding from the analysis and inventory', 'Identify any ambiguous requirements or unclear aspects', 'Formulate specific, answerable questions', 'Document assumptions you\'re making', 'If critical questions need user input, consider using user_input_required_guidance', '--- DETERMINE PHASE (Planning) ---', 'Based on all clarifications, create a detailed implementation plan', 'Break down your chosen approach into specific steps', 'Order the steps logically based on dependencies', 'Define clear success criteria for each step', 'Plan validation points throughout the implementation' ], suggestedApproach: [ 'QUESTION: Be specific with questions - vague questions get vague answers', 'QUESTION: Prioritize questions that would block progress', 'QUESTION: Document assumptions clearly if answers aren\'t available', 'DETERMINE: Start with foundation changes that others depend on', 'DETERMINE: Keep implementation steps small and focused', 'DETERMINE: Plan to test after each major change', 'DETERMINE: Include rollback strategies for risky changes' ], importantNotes: [ 'Questions and planning go hand-in-hand', 'A clear plan requires all ambiguities to be resolved', 'This phase finalizes your strategy before any code changes', 'If you need user input for critical questions, don\'t hesitate to escalate' ], expectedOutput: { // Question outputs questions: 'List of specific questions (if any)', assumptions: 'What you\'re assuming if not clarified', clarifications: 'Any resolved ambiguities', // Determine outputs implementationSteps: 'Numbered list of specific changes to make', dependencies: 'Which steps depend on others', validation: 'How to verify each step', successCriteria: 'Definition of completion', rollbackPlan: 'How to undo changes if needed' }, nextPhase: 'Use refactor_guidance to begin implementation' },