@lbruton/spec-workflow-mcp 2.2.4

package/dist/prompts/implement-task.js

@@ -0,0 +1,173 @@
+const prompt = {
+    name: 'implement-task',
+    title: 'Implement Specification Task',
+    description: 'Guide for implementing a specific task from the tasks.md document. Provides comprehensive instructions for task execution, including reading _Prompt fields, marking progress, completion criteria, and logging implementation details for the dashboard.',
+    arguments: [
+        {
+            name: 'specName',
+            description: 'Feature name in kebab-case for the task to implement',
+            required: true
+        },
+        {
+            name: 'taskId',
+            description: 'Specific task ID to implement (e.g., "1", "2.1", "3")',
+            required: false
+        }
+    ]
+};
+async function handler(args, context) {
+    const { specName, taskId } = args;
+    if (!specName) {
+        throw new Error('specName is a required argument');
+    }
+    const messages = [
+        {
+            role: 'user',
+            content: {
+                type: 'text',
+                text: `Implement ${taskId ? `task ${taskId}` : 'the next pending task'} for the "${specName}" feature.
+
+**Context:**
+- Project: ${context.projectPath}
+- Feature: ${specName}
+${taskId ? `- Task ID: ${taskId}` : ''}
+${context.dashboardUrl ? `- Dashboard: ${context.dashboardUrl}` : ''}
+
+**Implementation Workflow:**
+
+1. **Check Current Status:**
+   - Use the spec-status tool with specName "${specName}" to see overall progress
+   - Read .spec-workflow/specs/${specName}/tasks.md to see all tasks
+   - Identify ${taskId ? `task ${taskId}` : 'the next pending task marked with [ ]'}
+
+2. **Start the Task:**
+   - Edit .spec-workflow/specs/${specName}/tasks.md directly
+   - Change the task marker from [ ] to [-] for the task you're starting
+   - Only one task should be in-progress at a time
+
+3. **Read Task Guidance:**
+   - Look for the _Prompt field in the task - it contains structured guidance:
+     - Role: The specialized developer role to assume
+     - Task: Clear description with context references
+     - Restrictions: What not to do and constraints
+     - Success: Specific completion criteria
+   - Note the _Leverage fields for files/utilities to use
+   - Check _Requirements fields for which requirements this implements
+
+4. **Discover Existing Implementations (CRITICAL):**
+   - BEFORE writing any code, search implementation logs to understand existing artifacts
+   - Implementation logs are stored as markdown files in: .spec-workflow/specs/${specName}/Implementation Logs/
+
+   **Option 1: Use grep/ripgrep for fast searches**
+   \`\`\`bash
+   # Search for API endpoints
+   grep -r "GET\|POST\|PUT\|DELETE" ".spec-workflow/specs/${specName}/Implementation Logs/"
+
+   # Search for specific components
+   grep -r "ComponentName" ".spec-workflow/specs/${specName}/Implementation Logs/"
+
+   # Search for integration patterns
+   grep -r "integration\|dataFlow" ".spec-workflow/specs/${specName}/Implementation Logs/"
+   \`\`\`
+
+   **Option 2: Read markdown files directly**
+   - Use the Read tool to examine implementation log files
+   - Search for relevant sections (## API Endpoints, ## Components, ## Functions, etc.)
+   - Review artifacts from related tasks to understand established patterns
+
+   **Discovery best practices:**
+   - First: Search for "API" or "endpoint" to find existing API patterns
+   - Second: Search for "component" or specific component names to see existing UI structures
+   - Third: Search for "integration" or "dataFlow" to understand how frontend/backend connect
+   - Why this matters:
+     - ❌ Don't create duplicate API endpoints - check for similar paths
+     - ❌ Don't reimplement components/functions - verify utilities already don't exist
+     - ❌ Don't ignore established patterns - understand middleware/integration setup
+     - ✅ Reuse existing code - leverage already-implemented functions and components
+     - ✅ Follow patterns - maintain consistency with established architecture
+   - If initial search doesn't find expected results, refine your grep patterns
+   - Document any existing related implementations before proceeding
+   - If you find existing code that does what the task asks, leverage it instead of recreating
+
+5. **Implement the Task:**
+   - Follow the _Prompt guidance exactly
+   - Use the files mentioned in _Leverage fields
+   - Create or modify the files specified in the task
+   - Write clean, well-commented code
+   - Follow existing patterns in the codebase
+   - Test your implementation thoroughly
+
+6. **Log Implementation (MANDATORY - must complete BEFORE marking task done):**
+   - ⚠️ **STOP: Do NOT mark the task [x] until this step succeeds.**
+   - A task without an implementation log is NOT complete. Skipping this step is the #1 workflow violation.
+   - Call log-implementation with ALL of the following:
+     - specName: "${specName}"
+     - taskId: ${taskId ? `"${taskId}"` : 'the task ID you just completed'}
+     - summary: Clear description of what was implemented (1-2 sentences)
+     - filesModified: List of files you edited
+     - filesCreated: List of files you created
+     - statistics: {linesAdded: number, linesRemoved: number}
+     - artifacts: {apiEndpoints: [...], components: [...], functions: [...], classes: [...], integrations: [...]}
+   - You MUST include artifacts (required field) to enable other agents to find your work:
+     - **apiEndpoints**: List all API endpoints created/modified with method, path, purpose, request/response formats, and location
+     - **components**: List all UI components created with name, type, purpose, props, and location
+     - **functions**: List all utility functions with signature and location
+     - **classes**: List all classes with methods and location
+     - **integrations**: Document how frontend connects to backend with data flow description
+   - Example artifacts for an API endpoint:
+     \`\`\`json
+     "apiEndpoints": [{
+       "method": "GET",
+       "path": "/api/todos/:id",
+       "purpose": "Fetch a specific todo by ID",
+       "requestFormat": "URL param: id (string)",
+       "responseFormat": "{ id: string, title: string, completed: boolean }",
+       "location": "src/server.ts:245"
+     }]
+     \`\`\`
+   - Why: Future AI agents will query logs before implementing, preventing duplicate code and ensuring architecture consistency
+   - This creates a searchable knowledge base — without it, implementation knowledge is lost when the conversation ends
+
+7. **Complete the Task (only after step 6 succeeds):**
+   - Confirm that log-implementation returned success in step 6
+   - Verify all success criteria from the _Prompt are met
+   - Run any relevant tests to ensure nothing is broken
+   - Edit .spec-workflow/specs/${specName}/tasks.md directly
+   - Change the task marker from [-] to [x] for the completed task
+   - ⚠️ If you skipped step 6, go back now — a task marked [x] without a log is incomplete
+
+**Important Guidelines:**
+- Always mark a task as in-progress before starting work
+- Follow the _Prompt field guidance for role, approach, and success criteria
+- Use existing patterns and utilities mentioned in _Leverage fields
+- Test your implementation before marking the task complete
+- **ALWAYS call log-implementation BEFORE marking a task [x]** — this is the most-skipped step and it is mandatory
+- If a task has subtasks (e.g., 4.1, 4.2), complete them in order
+- If you encounter blockers, document them and move to another task
+
+**Tools to Use:**
+- spec-status: Check overall progress
+- Bash (grep/ripgrep): CRITICAL - Search existing implementations before coding (step 4)
+- Read: Examine markdown implementation log files directly (step 4)
+- log-implementation: MANDATORY - Record implementation details with artifacts BEFORE marking task complete (step 6)
+- Edit: Directly update task markers in tasks.md file
+- Read/Write/Edit: Implement the actual code changes
+- Bash: Run tests and verify implementation
+
+**View Implementation Logs:**
+- All logged implementations appear in the "Logs" tab of the dashboard
+- Filter by spec, task ID, or search by summary
+- View detailed statistics including files changed and lines modified
+- Or search directly using grep on markdown files in .spec-workflow/specs/{specName}/Implementation Logs/
+
+Please proceed with implementing ${taskId ? `task ${taskId}` : 'the next task'} following this workflow.`
+            }
+        }
+    ];
+    return messages;
+}
+export const implementTaskPrompt = {
+    prompt,
+    handler
+};
+//# sourceMappingURL=implement-task.js.map

package/dist/prompts/implement-task.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"implement-task.js","sourceRoot":"","sources":["../../src/prompts/implement-task.ts"],"names":[],"mappings":"AAIA,MAAM,MAAM,GAAW;IACrB,IAAI,EAAE,gBAAgB;IACtB,KAAK,EAAE,8BAA8B;IACrC,WAAW,EAAE,2PAA2P;IACxQ,SAAS,EAAE;QACT;YACE,IAAI,EAAE,UAAU;YAChB,WAAW,EAAE,sDAAsD;YACnE,QAAQ,EAAE,IAAI;SACf;QACD;YACE,IAAI,EAAE,QAAQ;YACd,WAAW,EAAE,uDAAuD;YACpE,QAAQ,EAAE,KAAK;SAChB;KACF;CACF,CAAC;AAEF,KAAK,UAAU,OAAO,CAAC,IAAyB,EAAE,OAAoB;IACpE,MAAM,EAAE,QAAQ,EAAE,MAAM,EAAE,GAAG,IAAI,CAAC;IAElC,IAAI,CAAC,QAAQ,EAAE,CAAC;QACd,MAAM,IAAI,KAAK,CAAC,iCAAiC,CAAC,CAAC;IACrD,CAAC;IAED,MAAM,QAAQ,GAAoB;QAChC;YACE,IAAI,EAAE,MAAM;YACZ,OAAO,EAAE;gBACP,IAAI,EAAE,MAAM;gBACZ,IAAI,EAAE,aAAa,MAAM,CAAC,CAAC,CAAC,QAAQ,MAAM,EAAE,CAAC,CAAC,CAAC,uBAAuB,aAAa,QAAQ;;;aAGtF,OAAO,CAAC,WAAW;aACnB,QAAQ;EACnB,MAAM,CAAC,CAAC,CAAC,cAAc,MAAM,EAAE,CAAC,CAAC,CAAC,EAAE;EACpC,OAAO,CAAC,YAAY,CAAC,CAAC,CAAC,gBAAgB,OAAO,CAAC,YAAY,EAAE,CAAC,CAAC,CAAC,EAAE;;;;;+CAKrB,QAAQ;iCACtB,QAAQ;gBACzB,MAAM,CAAC,CAAC,CAAC,QAAQ,MAAM,EAAE,CAAC,CAAC,CAAC,uCAAuC;;;iCAGlD,QAAQ;;;;;;;;;;;;;;;iFAewC,QAAQ;;;;;4DAK7B,QAAQ;;;mDAGjB,QAAQ;;;2DAGA,QAAQ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;oBAkC/C,QAAQ;iBACX,MAAM,CAAC,CAAC,CAAC,IAAI,MAAM,GAAG,CAAC,CAAC,CAAC,gCAAgC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iCA8BzC,QAAQ;;;;;;;;;;;;;;;;;;;;;;;;;;;;mCA4BN,MAAM,CAAC,CAAC,CAAC,QAAQ,MAAM,EAAE,CAAC,CAAC,CAAC,eAAe,2BAA2B;aAClG;SACF;KACF,CAAC;IAEF,OAAO,QAAQ,CAAC;AAClB,CAAC;AAED,MAAM,CAAC,MAAM,mBAAmB,GAAqB;IACnD,MAAM;IACN,OAAO;CACR,CAAC"}

package/dist/prompts/index.d.ts

@@ -0,0 +1,15 @@
+import { Prompt, ListPromptsResult, GetPromptResult } from '@modelcontextprotocol/sdk/types.js';
+import { ToolContext } from '../types.js';
+/**
+ * Get all registered prompts
+ */
+export declare function registerPrompts(): Prompt[];
+/**
+ * Handle prompts/list request
+ */
+export declare function handlePromptList(): Promise<ListPromptsResult>;
+/**
+ * Handle prompts/get request
+ */
+export declare function handlePromptGet(name: string, args: Record<string, any> | undefined, context: ToolContext): Promise<GetPromptResult>;
+//# sourceMappingURL=index.d.ts.map

package/dist/prompts/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/prompts/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,EAAiB,iBAAiB,EAAE,eAAe,EAAE,MAAM,oCAAoC,CAAC;AAC/G,OAAO,EAAE,WAAW,EAAE,MAAM,aAAa,CAAC;AAuB1C;;GAEG;AACH,wBAAgB,eAAe,IAAI,MAAM,EAAE,CAE1C;AAED;;GAEG;AACH,wBAAsB,gBAAgB,IAAI,OAAO,CAAC,iBAAiB,CAAC,CAInE;AAED;;GAEG;AACH,wBAAsB,eAAe,CACnC,IAAI,EAAE,MAAM,EACZ,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,YAAK,EAC9B,OAAO,EAAE,WAAW,GACnB,OAAO,CAAC,eAAe,CAAC,CAa1B"}

package/dist/prompts/index.js

@@ -0,0 +1,49 @@
+// Import individual prompt definitions
+import { createSpecPrompt } from './create-spec.js';
+import { createSteeringDocPrompt } from './create-steering-doc.js';
+import { implementTaskPrompt } from './implement-task.js';
+import { specStatusPrompt } from './spec-status.js';
+import { injectSpecWorkflowGuidePrompt } from './inject-spec-workflow-guide.js';
+import { injectSteeringGuidePrompt } from './inject-steering-guide.js';
+import { refreshTasksPrompt } from './refresh-tasks.js';
+// Registry of all prompts
+const promptDefinitions = [
+    createSpecPrompt,
+    createSteeringDocPrompt,
+    implementTaskPrompt,
+    specStatusPrompt,
+    injectSpecWorkflowGuidePrompt,
+    injectSteeringGuidePrompt,
+    refreshTasksPrompt
+];
+/**
+ * Get all registered prompts
+ */
+export function registerPrompts() {
+    return promptDefinitions.map(def => def.prompt);
+}
+/**
+ * Handle prompts/list request
+ */
+export async function handlePromptList() {
+    return {
+        prompts: registerPrompts()
+    };
+}
+/**
+ * Handle prompts/get request
+ */
+export async function handlePromptGet(name, args = {}, context) {
+    const promptDef = promptDefinitions.find(def => def.prompt.name === name);
+    if (!promptDef) {
+        throw new Error(`Prompt not found: ${name}`);
+    }
+    try {
+        const messages = await promptDef.handler(args, context);
+        return { messages };
+    }
+    catch (error) {
+        throw new Error(`Failed to generate prompt messages: ${error.message}`);
+    }
+}
+//# sourceMappingURL=index.js.map

package/dist/prompts/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/prompts/index.ts"],"names":[],"mappings":"AAIA,uCAAuC;AACvC,OAAO,EAAE,gBAAgB,EAAE,MAAM,kBAAkB,CAAC;AACpD,OAAO,EAAE,uBAAuB,EAAE,MAAM,0BAA0B,CAAC;AACnE,OAAO,EAAE,mBAAmB,EAAE,MAAM,qBAAqB,CAAC;AAC1D,OAAO,EAAE,gBAAgB,EAAE,MAAM,kBAAkB,CAAC;AACpD,OAAO,EAAE,6BAA6B,EAAE,MAAM,iCAAiC,CAAC;AAChF,OAAO,EAAE,yBAAyB,EAAE,MAAM,4BAA4B,CAAC;AACvE,OAAO,EAAE,kBAAkB,EAAE,MAAM,oBAAoB,CAAC;AAExD,0BAA0B;AAC1B,MAAM,iBAAiB,GAAuB;IAC5C,gBAAgB;IAChB,uBAAuB;IACvB,mBAAmB;IACnB,gBAAgB;IAChB,6BAA6B;IAC7B,yBAAyB;IACzB,kBAAkB;CACnB,CAAC;AAEF;;GAEG;AACH,MAAM,UAAU,eAAe;IAC7B,OAAO,iBAAiB,CAAC,GAAG,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,CAAC,MAAM,CAAC,CAAC;AAClD,CAAC;AAED;;GAEG;AACH,MAAM,CAAC,KAAK,UAAU,gBAAgB;IACpC,OAAO;QACL,OAAO,EAAE,eAAe,EAAE;KAC3B,CAAC;AACJ,CAAC;AAED;;GAEG;AACH,MAAM,CAAC,KAAK,UAAU,eAAe,CACnC,IAAY,EACZ,OAA4B,EAAE,EAC9B,OAAoB;IAEpB,MAAM,SAAS,GAAG,iBAAiB,CAAC,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,CAAC,MAAM,CAAC,IAAI,KAAK,IAAI,CAAC,CAAC;IAE1E,IAAI,CAAC,SAAS,EAAE,CAAC;QACf,MAAM,IAAI,KAAK,CAAC,qBAAqB,IAAI,EAAE,CAAC,CAAC;IAC/C,CAAC;IAED,IAAI,CAAC;QACH,MAAM,QAAQ,GAAG,MAAM,SAAS,CAAC,OAAO,CAAC,IAAI,EAAE,OAAO,CAAC,CAAC;QACxD,OAAO,EAAE,QAAQ,EAAE,CAAC;IACtB,CAAC;IAAC,OAAO,KAAU,EAAE,CAAC;QACpB,MAAM,IAAI,KAAK,CAAC,uCAAuC,KAAK,CAAC,OAAO,EAAE,CAAC,CAAC;IAC1E,CAAC;AACH,CAAC"}

package/dist/prompts/inject-spec-workflow-guide.d.ts

@@ -0,0 +1,3 @@
+import { PromptDefinition } from './types.js';
+export declare const injectSpecWorkflowGuidePrompt: PromptDefinition;
+//# sourceMappingURL=inject-spec-workflow-guide.d.ts.map

package/dist/prompts/inject-spec-workflow-guide.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"inject-spec-workflow-guide.d.ts","sourceRoot":"","sources":["../../src/prompts/inject-spec-workflow-guide.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAC;AAkD9C,eAAO,MAAM,6BAA6B,EAAE,gBAG3C,CAAC"}

package/dist/prompts/inject-spec-workflow-guide.js

@@ -0,0 +1,47 @@
+import { specWorkflowGuideHandler } from '../tools/spec-workflow-guide.js';
+const prompt = {
+    name: 'inject-spec-workflow-guide',
+    title: 'Inject Spec Workflow Guide into Context',
+    description: 'Injects the complete spec-driven development workflow guide into the conversation context. This provides immediate access to all workflow phases, tools, and best practices without requiring separate tool calls.'
+};
+async function handler(args, context) {
+    // Call the spec-workflow-guide tool to get the full guide
+    const toolResponse = await specWorkflowGuideHandler({}, context);
+    // Extract the guide content from the tool response
+    const guide = toolResponse.data?.guide || '';
+    const dashboardUrl = toolResponse.data?.dashboardUrl;
+    const nextSteps = toolResponse.nextSteps || [];
+    const messages = [
+        {
+            role: 'user',
+            content: {
+                type: 'text',
+                text: `Please review and follow this comprehensive spec-driven development workflow guide:
+
+${guide}
+
+**Current Context:**
+- Project: ${context.projectPath}
+${dashboardUrl ? `- Dashboard: ${dashboardUrl}` : '- Dashboard: Please start the dashboard or use VS Code extension "Spec Workflow MCP"'}
+
+**Next Steps:**
+${nextSteps.map(step => `- ${step}`).join('\n')}
+
+**Important Instructions:**
+1. This guide has been injected into your context for immediate reference
+2. Follow the workflow sequence exactly: Requirements → Design → Tasks → Implementation
+3. Use the MCP tools mentioned in the guide to execute each phase
+4. Always request approval between phases using the approvals tool
+5. Never proceed to the next phase without successful approval cleanup
+
+Please acknowledge that you've reviewed this workflow guide and are ready to help with spec-driven development.`
+            }
+        }
+    ];
+    return messages;
+}
+export const injectSpecWorkflowGuidePrompt = {
+    prompt,
+    handler
+};
+//# sourceMappingURL=inject-spec-workflow-guide.js.map

package/dist/prompts/inject-spec-workflow-guide.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"inject-spec-workflow-guide.js","sourceRoot":"","sources":["../../src/prompts/inject-spec-workflow-guide.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,wBAAwB,EAAE,MAAM,iCAAiC,CAAC;AAE3E,MAAM,MAAM,GAAW;IACrB,IAAI,EAAE,4BAA4B;IAClC,KAAK,EAAE,yCAAyC;IAChD,WAAW,EAAE,oNAAoN;CAClO,CAAC;AAEF,KAAK,UAAU,OAAO,CAAC,IAAyB,EAAE,OAAoB;IACpE,0DAA0D;IAC1D,MAAM,YAAY,GAAG,MAAM,wBAAwB,CAAC,EAAE,EAAE,OAAO,CAAC,CAAC;IAEjE,mDAAmD;IACnD,MAAM,KAAK,GAAG,YAAY,CAAC,IAAI,EAAE,KAAK,IAAI,EAAE,CAAC;IAC7C,MAAM,YAAY,GAAG,YAAY,CAAC,IAAI,EAAE,YAAY,CAAC;IACrD,MAAM,SAAS,GAAG,YAAY,CAAC,SAAS,IAAI,EAAE,CAAC;IAE/C,MAAM,QAAQ,GAAoB;QAChC;YACE,IAAI,EAAE,MAAM;YACZ,OAAO,EAAE;gBACP,IAAI,EAAE,MAAM;gBACZ,IAAI,EAAE;;EAEZ,KAAK;;;aAGM,OAAO,CAAC,WAAW;EAC9B,YAAY,CAAC,CAAC,CAAC,gBAAgB,YAAY,EAAE,CAAC,CAAC,CAAC,sFAAsF;;;EAGtI,SAAS,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,KAAK,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;;;;;;;;;gHASiE;aACzG;SACF;KACF,CAAC;IAEF,OAAO,QAAQ,CAAC;AAClB,CAAC;AAED,MAAM,CAAC,MAAM,6BAA6B,GAAqB;IAC7D,MAAM;IACN,OAAO;CACR,CAAC"}

package/dist/prompts/inject-steering-guide.d.ts

@@ -0,0 +1,3 @@
+import { PromptDefinition } from './types.js';
+export declare const injectSteeringGuidePrompt: PromptDefinition;
+//# sourceMappingURL=inject-steering-guide.d.ts.map

package/dist/prompts/inject-steering-guide.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"inject-steering-guide.d.ts","sourceRoot":"","sources":["../../src/prompts/inject-steering-guide.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAC;AAsD9C,eAAO,MAAM,yBAAyB,EAAE,gBAGvC,CAAC"}

package/dist/prompts/inject-steering-guide.js

@@ -0,0 +1,51 @@
+import { steeringGuideHandler } from '../tools/steering-guide.js';
+const prompt = {
+    name: 'inject-steering-guide',
+    title: 'Inject Steering Guide into Context',
+    description: 'Injects the complete steering document workflow guide into the conversation context. This provides instructions for creating project-level guidance documents (product.md, tech.md, structure.md) when explicitly requested by the user.'
+};
+async function handler(args, context) {
+    // Call the steering-guide tool to get the full guide
+    const toolResponse = await steeringGuideHandler({}, context);
+    // Extract the guide content from the tool response
+    const guide = toolResponse.data?.guide || '';
+    const dashboardUrl = toolResponse.data?.dashboardUrl;
+    const nextSteps = toolResponse.nextSteps || [];
+    const messages = [
+        {
+            role: 'user',
+            content: {
+                type: 'text',
+                text: `Please review and follow this steering document workflow guide:
+
+${guide}
+
+**Current Context:**
+- Project: ${context.projectPath}
+${dashboardUrl ? `- Dashboard: ${dashboardUrl}` : '- Dashboard: Please start the dashboard or use VS Code extension "Spec Workflow MCP"'}
+
+**Next Steps:**
+${nextSteps.map(step => `- ${step}`).join('\n')}
+
+**Important Instructions:**
+1. This guide has been injected into your context for creating steering documents
+2. Only proceed if the user explicitly requested steering document creation
+3. Follow the sequence exactly: product.md → tech.md → structure.md
+4. Read templates from .spec-workflow/templates/ directory
+5. Create documents in .spec-workflow/steering/ directory
+6. Request approval after each document using the approvals tool
+7. Never proceed to the next document without successful approval cleanup
+
+**Note:** Steering documents are NOT part of the standard spec workflow. They are project-level guidance documents that should only be created when explicitly requested by the user. These documents establish vision, architecture, and conventions for established codebases.
+
+Please acknowledge that you've reviewed this steering workflow guide and confirm whether the user wants to create steering documents.`
+            }
+        }
+    ];
+    return messages;
+}
+export const injectSteeringGuidePrompt = {
+    prompt,
+    handler
+};
+//# sourceMappingURL=inject-steering-guide.js.map

package/dist/prompts/inject-steering-guide.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"inject-steering-guide.js","sourceRoot":"","sources":["../../src/prompts/inject-steering-guide.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,oBAAoB,EAAE,MAAM,4BAA4B,CAAC;AAElE,MAAM,MAAM,GAAW;IACrB,IAAI,EAAE,uBAAuB;IAC7B,KAAK,EAAE,oCAAoC;IAC3C,WAAW,EAAE,0OAA0O;CACxP,CAAC;AAEF,KAAK,UAAU,OAAO,CAAC,IAAyB,EAAE,OAAoB;IACpE,qDAAqD;IACrD,MAAM,YAAY,GAAG,MAAM,oBAAoB,CAAC,EAAE,EAAE,OAAO,CAAC,CAAC;IAE7D,mDAAmD;IACnD,MAAM,KAAK,GAAG,YAAY,CAAC,IAAI,EAAE,KAAK,IAAI,EAAE,CAAC;IAC7C,MAAM,YAAY,GAAG,YAAY,CAAC,IAAI,EAAE,YAAY,CAAC;IACrD,MAAM,SAAS,GAAG,YAAY,CAAC,SAAS,IAAI,EAAE,CAAC;IAE/C,MAAM,QAAQ,GAAoB;QAChC;YACE,IAAI,EAAE,MAAM;YACZ,OAAO,EAAE;gBACP,IAAI,EAAE,MAAM;gBACZ,IAAI,EAAE;;EAEZ,KAAK;;;aAGM,OAAO,CAAC,WAAW;EAC9B,YAAY,CAAC,CAAC,CAAC,gBAAgB,YAAY,EAAE,CAAC,CAAC,CAAC,sFAAsF;;;EAGtI,SAAS,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,KAAK,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;;;;;;;;;;;;;sIAauF;aAC/H;SACF;KACF,CAAC;IAEF,OAAO,QAAQ,CAAC;AAClB,CAAC;AAED,MAAM,CAAC,MAAM,yBAAyB,GAAqB;IACzD,MAAM;IACN,OAAO;CACR,CAAC"}

package/dist/prompts/refresh-tasks.d.ts

@@ -0,0 +1,3 @@
+import { PromptDefinition } from './types.js';
+export declare const refreshTasksPrompt: PromptDefinition;
+//# sourceMappingURL=refresh-tasks.d.ts.map

package/dist/prompts/refresh-tasks.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"refresh-tasks.d.ts","sourceRoot":"","sources":["../../src/prompts/refresh-tasks.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAC;AAmO9C,eAAO,MAAM,kBAAkB,EAAE,gBAGhC,CAAC"}

package/dist/prompts/refresh-tasks.js

@@ -0,0 +1,224 @@
+import { PathUtils } from '../core/path-utils.js';
+import { readFile } from 'fs/promises';
+import { join } from 'path';
+const prompt = {
+    name: 'refresh-tasks',
+    title: 'Refresh Tasks After Spec Changes',
+    description: 'Comprehensive guide for updating tasks.md when requirements or design change during implementation. Preserves completed work while aligning pending tasks with current spec.',
+    arguments: [
+        {
+            name: 'specName',
+            description: 'Name of the specification to refresh tasks for',
+            required: true
+        },
+        {
+            name: 'changes',
+            description: 'Description of what changed in requirements or design',
+            required: false
+        }
+    ]
+};
+async function handler(args, context) {
+    const { specName, changes = 'Requirements or design have been updated' } = args;
+    const projectPath = context.projectPath;
+    // Try to load existing documents for context
+    let contextInfo = '';
+    try {
+        const specDir = PathUtils.getSpecPath(projectPath, specName);
+        // Check what documents exist
+        let hasRequirements = false;
+        let hasDesign = false;
+        let hasTasks = false;
+        try {
+            await readFile(join(specDir, 'requirements.md'), 'utf-8');
+            hasRequirements = true;
+        }
+        catch (error) {
+            // File doesn't exist
+        }
+        try {
+            await readFile(join(specDir, 'design.md'), 'utf-8');
+            hasDesign = true;
+        }
+        catch (error) {
+            // File doesn't exist
+        }
+        try {
+            await readFile(join(specDir, 'tasks.md'), 'utf-8');
+            hasTasks = true;
+        }
+        catch (error) {
+            // File doesn't exist
+        }
+        contextInfo = `
+## Current Spec Status for "${specName}"
+- Requirements.md exists: ${hasRequirements ? 'Yes' : 'No'}
+- Design.md exists: ${hasDesign ? 'Yes' : 'No'}
+- Tasks.md exists: ${hasTasks ? 'Yes' : 'No'}
+
+## Reported Changes
+${changes}
+`;
+    }
+    catch (error) {
+        contextInfo = `
+## Spec: "${specName}"
+Unable to check existing documents. Ensure the spec exists at the correct path.
+
+## Reported Changes
+${changes}
+`;
+    }
+    const content = `# Task Refresh Instructions
+
+${contextInfo}
+
+## Context
+You are refreshing the task list for specification "${specName}" because requirements or design have changed during implementation. Your goal is to ensure the task list accurately reflects what needs to be done to bridge the gap between current implementation and the updated requirements/design.
+
+## CRITICAL: Source of Truth
+- Requirements come ONLY from requirements.md - not from existing tasks
+- Design decisions come ONLY from design.md - not from existing tasks
+- Tasks are implementation steps - they implement requirements, they don't define them
+- If a feature exists in tasks but NOT in requirements.md/design.md, it has been REMOVED from the spec
+
+## Three-Pass Validation Process
+
+### PASS 1: Validate Existing Tasks Against Current Spec
+For each existing task, verify if the feature it implements still exists in requirements.md or design.md.
+
+Actions for PENDING tasks:
+- KEEP if the feature is still in requirements/design
+- REMOVE if the feature is NOT in requirements/design (feature was cut from spec)
+
+Actions for COMPLETED/IN-PROGRESS tasks:
+- ALWAYS PRESERVE completed [x] and in-progress [-] tasks exactly as written
+- If the feature was removed, add a note: "_Note: Feature removed from spec but task preserved_"
+- If architecture changed, add migration tasks immediately after the completed work
+
+### PASS 2: Gap Analysis
+For each requirement in requirements.md, verify corresponding task coverage exists.
+For each design decision in design.md, verify tasks align with the architecture.
+
+Actions:
+- ADD new tasks for requirements/design elements without task coverage
+- ADD migration tasks when architecture changes affect completed work
+- UPDATE pending tasks that need alignment with updated requirements
+
+### PASS 3: Create Updated Task List
+After Pass 1 and Pass 2, determine if changes are needed:
+- Are there pending tasks to remove?
+- Are there new tasks to add?
+- Are there migration tasks needed?
+- Are there existing tasks to modify?
+
+If NO changes needed: Report "Task list is already aligned with current requirements - no refresh needed" and STOP.
+
+If changes ARE needed, build the new tasks.md with:
+1. All completed [x] tasks preserved exactly as written
+2. All in-progress [-] tasks preserved exactly as written
+3. Migration tasks added where architecture changes affect completed work
+4. Only pending [ ] tasks that have backing in current requirements/design
+5. New tasks for any missing requirements/design elements
+6. Proper sequencing and requirement references
+
+## Handling Architecture Changes
+
+When architecture changes affect already-implemented code, add migration tasks:
+
+Example: MongoDB to PostgreSQL switch with completed MongoDB work:
+- [x] 2.1 Create MongoDB connection logic
+- [x] 2.2 Define MongoDB schemas
+- [x] 2.3 Implement MongoDB queries
+- [ ] 2.4 Migrate MongoDB schemas to PostgreSQL tables (NEW)
+- [ ] 2.5 Replace MongoDB connection with PostgreSQL client (NEW)
+- [ ] 2.6 Convert MongoDB queries to PostgreSQL syntax (NEW)
+- [ ] 2.7 Migrate existing data from MongoDB to PostgreSQL (NEW)
+- [ ] 2.8 Verify data integrity after migration (NEW)
+- [ ] 2.9 Remove MongoDB dependencies after verification (NEW)
+- [ ] 2.10 Implement remaining PostgreSQL features
+
+Example: REST to GraphQL migration with completed REST endpoints:
+- [x] 3.1 Implement user REST endpoints
+- [x] 3.2 Implement product REST endpoints
+- [ ] 3.3 Define GraphQL schema for users and products (NEW)
+- [ ] 3.4 Create GraphQL resolvers wrapping REST logic (NEW)
+- [ ] 3.5 Update client to use GraphQL queries (NEW)
+- [ ] 3.6 Test GraphQL implementation thoroughly (NEW)
+- [ ] 3.7 Remove REST endpoints after GraphQL verified (NEW)
+
+## Task Format Requirements
+Each task must follow this format:
+- [ ] 1.1 Create user authentication interface
+  - File: src/auth/UserAuth.ts
+  - Implement login and registration forms
+  - Add form validation and error handling
+  - Purpose: Enable user account management
+  - _Leverage: src/components/BaseForm.tsx, src/utils/validation.ts_
+  - _Requirements: 1.1, 1.2_
+
+Migration tasks should follow this format:
+- [ ] 2.4 Migrate MongoDB schemas to PostgreSQL tables
+  - File: src/database/migrations/mongo-to-postgres.ts
+  - Convert document schemas to relational tables
+  - Map embedded documents to foreign key relationships
+  - Preserve all existing data relationships
+  - Purpose: Transition database layer to new architecture
+  - _Leverage: Completed MongoDB schemas in tasks 2.1-2.3_
+  - _Requirements: Design section 3.2_
+
+## Critical Rules
+- ALWAYS preserve completed [x] tasks exactly as written
+- ALWAYS preserve in-progress [-] tasks exactly as written
+- ALWAYS add migration tasks when architecture changes affect completed work
+- ALWAYS reference specific requirements (e.g., _Requirements: 1.1, 2.3_)
+- ENSURE tasks build incrementally with proper dependencies
+- MAKE tasks atomic, specific, and actionable
+- PRESERVE the original tasks.md structure and format
+- KEEP tasks.md clean - only include the task list itself
+
+## Progressive Migration Strategy
+
+For major architecture changes, create tasks that support progressive migration:
+1. Implement new architecture alongside existing
+2. Add compatibility layer tasks
+3. Migrate functionality incrementally
+4. Verify each migration step
+5. Remove old implementation only after full verification
+
+This ensures the application remains functional throughout the transition.
+
+## Implementation Steps
+1. Read requirements.md and design.md carefully - these define what should exist
+2. Read current tasks.md and identify completed, in-progress, and pending tasks
+3. Perform Pass 1: Validate existing tasks against current spec
+4. Perform Pass 2: Identify gaps in task coverage
+5. Determine if changes are needed
+6. If changes needed, build updated task list with proper validation
+7. Use create-spec-doc tool to save the updated tasks.md
+8. Report what changes were made and why
+
+## Example Analysis Output
+
+When refreshing tasks, provide clear feedback:
+
+"Task Refresh Analysis:
+- Preserved: 5 completed tasks, 2 in-progress tasks
+- Removed: 3 pending tasks for deleted reporting feature
+- Added: 4 migration tasks for MongoDB to PostgreSQL transition
+- Added: 6 new tasks for social login feature
+- Updated: 2 pending tasks to align with new API design
+
+The tasks.md has been updated to reflect current requirements while preserving all completed work."`;
+    return [
+        {
+            role: 'user',
+            content: { type: 'text', text: content }
+        }
+    ];
+}
+export const refreshTasksPrompt = {
+    prompt,
+    handler
+};
+//# sourceMappingURL=refresh-tasks.js.map

package/dist/prompts/refresh-tasks.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"refresh-tasks.js","sourceRoot":"","sources":["../../src/prompts/refresh-tasks.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAClD,OAAO,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC;AACvC,OAAO,EAAE,IAAI,EAAE,MAAM,MAAM,CAAC;AAE5B,MAAM,MAAM,GAAW;IACrB,IAAI,EAAE,eAAe;IACrB,KAAK,EAAE,kCAAkC;IACzC,WAAW,EAAE,8KAA8K;IAC3L,SAAS,EAAE;QACT;YACE,IAAI,EAAE,UAAU;YAChB,WAAW,EAAE,gDAAgD;YAC7D,QAAQ,EAAE,IAAI;SACf;QACD;YACE,IAAI,EAAE,SAAS;YACf,WAAW,EAAE,uDAAuD;YACpE,QAAQ,EAAE,KAAK;SAChB;KACF;CACF,CAAC;AAEF,KAAK,UAAU,OAAO,CAAC,IAAyB,EAAE,OAAoB;IACpE,MAAM,EAAE,QAAQ,EAAE,OAAO,GAAG,0CAA0C,EAAE,GAAG,IAAI,CAAC;IAChF,MAAM,WAAW,GAAG,OAAO,CAAC,WAAW,CAAC;IAExC,6CAA6C;IAC7C,IAAI,WAAW,GAAG,EAAE,CAAC;IACrB,IAAI,CAAC;QACH,MAAM,OAAO,GAAG,SAAS,CAAC,WAAW,CAAC,WAAW,EAAE,QAAQ,CAAC,CAAC;QAE7D,6BAA6B;QAC7B,IAAI,eAAe,GAAG,KAAK,CAAC;QAC5B,IAAI,SAAS,GAAG,KAAK,CAAC;QACtB,IAAI,QAAQ,GAAG,KAAK,CAAC;QAErB,IAAI,CAAC;YACH,MAAM,QAAQ,CAAC,IAAI,CAAC,OAAO,EAAE,iBAAiB,CAAC,EAAE,OAAO,CAAC,CAAC;YAC1D,eAAe,GAAG,IAAI,CAAC;QACzB,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,qBAAqB;QACvB,CAAC;QAED,IAAI,CAAC;YACH,MAAM,QAAQ,CAAC,IAAI,CAAC,OAAO,EAAE,WAAW,CAAC,EAAE,OAAO,CAAC,CAAC;YACpD,SAAS,GAAG,IAAI,CAAC;QACnB,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,qBAAqB;QACvB,CAAC;QAED,IAAI,CAAC;YACH,MAAM,QAAQ,CAAC,IAAI,CAAC,OAAO,EAAE,UAAU,CAAC,EAAE,OAAO,CAAC,CAAC;YACnD,QAAQ,GAAG,IAAI,CAAC;QAClB,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,qBAAqB;QACvB,CAAC;QAED,WAAW,GAAG;8BACY,QAAQ;4BACV,eAAe,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI;sBACpC,SAAS,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI;qBACzB,QAAQ,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI;;;EAG1C,OAAO;CACR,CAAC;IACA,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,WAAW,GAAG;YACN,QAAQ;;;;EAIlB,OAAO;CACR,CAAC;IACA,CAAC;IAED,MAAM,OAAO,GAAG;;EAEhB,WAAW;;;sDAGyC,QAAQ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;oGAuIsC,CAAC;IAEnG,OAAO;QACL;YACE,IAAI,EAAE,MAAM;YACZ,OAAO,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,OAAO,EAAE;SACzC;KACF,CAAC;AAAA,CAAC;AAEL,MAAM,CAAC,MAAM,kBAAkB,GAAqB;IAClD,MAAM;IACN,OAAO;CACR,CAAC"}

package/dist/prompts/spec-status.d.ts

@@ -0,0 +1,3 @@
+import { PromptDefinition } from './types.js';
+export declare const specStatusPrompt: PromptDefinition;
+//# sourceMappingURL=spec-status.d.ts.map

package/dist/prompts/spec-status.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"spec-status.d.ts","sourceRoot":"","sources":["../../src/prompts/spec-status.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,gBAAgB,EAAE,MAAM,YAAY,CAAC;AA8E9C,eAAO,MAAM,gBAAgB,EAAE,gBAG9B,CAAC"}