wolfpack-mcp 1.0.13 → 1.0.15

package/dist/index.js

@@ -48,7 +48,7 @@ const ListWorkItemsSchema = z.object({
     status: z.coerce
         .string()
         .optional()
-        .describe('Filter by status. Board columns: "new", "doing", "review", "blocked", "completed". Use "pending" or "backlog" for backlog items. Use "all" to include completed/closed. Default excludes completed/closed.'),
+        .describe('Filter by status. Board columns: "new", "doing", "review", "ready", "blocked", "completed". Use "pending" or "backlog" for backlog items. Use "all" to include completed/closed. Default excludes completed/closed.'),
     assigned_to_id: z.coerce
         .string()
         .optional()
@@ -143,7 +143,7 @@ const CreateWorkItemSchema = z.object({
     status: z
         .string()
         .optional()
-        .describe('Initial status: "pending" (backlog), "new" (to do), "doing", "review", "blocked", "completed". Defaults to "new".'),
+        .describe('Initial status: "pending" (backlog), "new" (to do), "doing", "review", "ready", "blocked", "completed". Defaults to "new".'),
     priority: z.number().optional().describe('Priority level (0-4, higher is more important)'),
     leading_user_id: z.string().optional().describe('User ID to assign as leading user'),
     category_id: z.string().optional().describe('Category ID to organize the work item'),
@@ -256,7 +256,7 @@ class WolfpackMCPServer {
                     name: 'list_work_items',
                     description: 'List work items (tasks/tickets). By default lists ALL items in the team, sorted by most recently updated. ' +
                         'Use assigned_to_id="me" to filter to only your assigned items. ' +
-                        'TERMINOLOGY: The board has columns: "new" (to do), "doing" (in progress), "review" (pending review), "blocked", "completed" (done). ' +
+                        'TERMINOLOGY: The board has columns: "new" (to do), "doing" (in progress), "review" (pending review), "ready" (code done, awaiting deployment), "blocked", "completed" (deployed). ' +
                         'The "backlog" or "pending" status represents items not yet on the board. ' +
                         'By default, completed/closed items are excluded - use status="all" to include them. ' +
                         'Use when user asks about "the board", "work items", "tasks", "my work" (with assigned_to_id="me"), or "backlog".',
@@ -269,7 +269,7 @@ class WolfpackMCPServer {
                             },
                             status: {
                                 type: 'string',
-                                description: 'Filter by status. Board columns: "new", "doing", "review", "blocked", "completed". ' +
+                                description: 'Filter by status. Board columns: "new", "doing", "review", "ready", "blocked", "completed". ' +
                                     'Use "pending" or "backlog" for backlog items not on board. ' +
                                     'Use "all" to include completed/closed items. Default excludes completed/closed.',
                             },
@@ -308,7 +308,11 @@ class WolfpackMCPServer {
                 },
                 {
                     name: 'get_work_item',
-                    description: 'Get a specific work item/task by ID or reference number. Returns full details including description (markdown notes). Call this before updating to see current content.',
+                    description: 'Get a specific work item/task by ID or reference number. Returns full details including description (markdown notes). ' +
+                        'Call this before updating to see current content. ' +
+                        'WORKFLOW: When asked to work on an item, check its status and follow the required state transitions ' +
+                        '(pending→pull first, new→doing, blocked/ready/completed/closed→new→doing, then review when done). ' +
+                        'PLANNING: Check if the description contains a plan (markdown checklist). If not, APPEND one using update_work_progress - preserve all original description text and add your plan below a "---" separator.',
                     inputSchema: {
                         type: 'object',
                         properties: {
@@ -326,7 +330,9 @@ class WolfpackMCPServer {
                 },
                 {
                     name: 'update_work_progress',
-                    description: 'Update work item description/notes with your progress. WORKFLOW: 1) get_work_item to read current notes 2) Modify the markdown description with new findings/progress 3) Call this with the complete updated description. The full description replaces the existing one.',
+                    description: 'Update work item description/notes with your progress. WORKFLOW: 1) get_work_item to read current notes 2) Modify the markdown description with new findings/progress 3) Call this with the complete updated description. The full description replaces the existing one. ' +
+                        'CRITICAL: NEVER overwrite or remove the original description text. Preserve all existing content exactly as-is. Append your plan below a "---" separator. You may only modify content you previously added (your plan section). ' +
+                        'BEST PRACTICE: Append a plan with markdown checkboxes (- [ ] task). Check off completed tasks (- [x] task) as you progress. Include sections for: Plan (checklist), Approach (strategy), and Notes (discoveries/decisions).',
                     inputSchema: {
                         type: 'object',
                         properties: {
@@ -342,9 +348,14 @@ class WolfpackMCPServer {
                 {
                     name: 'update_work_item_status',
                     description: 'Change work item status. ' +
-                        'Board columns: "new" (to do), "doing" (in progress), "review" (pending review), "blocked", "completed" (done). ' +
-                        '"pending" is for backlog items not yet on the board. ' +
-                        'WORKFLOW: Move to "doing" when starting work, "review" when ready for review, "completed" when done.',
+                        'REQUIRED WORKFLOW when working on items: ' +
+                        '1) For "new" items: move to "doing" when starting work. ' +
+                        '2) For "pending" (backlog) items: use pull_work_item first (claims and sets to "new"), then move to "doing". ' +
+                        '3) For items in "blocked", "ready", "completed", or "closed": move to "new" first, then to "doing". ' +
+                        '4) When work is complete: move to "review" (NOT "completed" - that is only for deployed work) and add a completion comment summarizing what was done. ' +
+                        '5) If work cannot be done: move to "blocked" and add a detailed comment explaining the blocker, what was attempted, and what is needed to unblock. ' +
+                        'Statuses: "pending" (backlog), "new" (to do), "doing" (in progress), "review" (work done, pending review), ' +
+                        '"ready" (reviewed, awaiting deployment), "blocked", "completed" (deployed).',
                     inputSchema: {
                         type: 'object',
                         properties: {
@@ -354,7 +365,7 @@ class WolfpackMCPServer {
                             },
                             status: {
                                 type: 'string',
-                                description: 'New status: "pending" (backlog), "new" (to do), "doing" (in progress), "review", "blocked", "completed" (done)',
+                                description: 'New status: "pending" (backlog), "new" (to do), "doing" (in progress), "review" (work done), "ready" (awaiting deployment), "blocked", "completed" (deployed)',
                             },
                         },
                         required: ['work_item_id', 'status'],
@@ -382,10 +393,9 @@ class WolfpackMCPServer {
                 {
                     name: 'pull_work_item',
                     description: 'Pull a specific work item from the backlog to the board. ' +
-                        'WORKFLOW: 1) Use list_work_items with status="pending" to browse backlog items, ' +
-                        '2) Evaluate and select an item, ' +
-                        '3) Use this tool to pull it onto the board. ' +
-                        'This changes the status from "pending" to "new" and assigns the item. ' +
+                        'REQUIRED: Use this when starting work on a "pending" (backlog) item. ' +
+                        'This claims the item (assigns to you) and sets status to "new". ' +
+                        'After pulling, move to "doing" to indicate active work, then "review" when done. ' +
                         'If no assignee is specified, assigns to the API key owner.',
                     inputSchema: {
                         type: 'object',
@@ -505,7 +515,7 @@ class WolfpackMCPServer {
                             },
                             status: {
                                 type: 'string',
-                                description: 'Initial status: "pending" (backlog), "new" (to do), "doing", "review", "blocked", "completed". Defaults to "new".',
+                                description: 'Initial status: "pending" (backlog), "new" (to do), "doing", "review", "ready", "blocked", "completed". Defaults to "new".',
                             },
                             priority: {
                                 type: 'number',
@@ -692,7 +702,11 @@ class WolfpackMCPServer {
                 // Comment tools
                 {
                     name: 'create_work_item_comment',
-                    description: 'Add a comment to a work item. Requires mcp:comments:create permission.',
+                    description: 'Add a comment to a work item. Requires mcp:comments:create permission. ' +
+                        'USE COMMENTS FOR: 1) Blocking reasons when moving to "blocked" (what failed, what was tried, what is needed). ' +
+                        '2) Completion summaries when moving to "review" (what was done, files changed, testing notes). ' +
+                        '3) Important observations or decisions that should be visible in the activity history. ' +
+                        'USE DESCRIPTION (update_work_progress) FOR: Plans, checklists, and progress tracking that need to be updated over time.',
                     inputSchema: {
                         type: 'object',
                         properties: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wolfpack-mcp",
-  "version": "1.0.13",
+  "version": "1.0.15",
   "description": "MCP server for Wolfpack AI-enhanced software delivery tools",
   "main": "dist/index.js",
   "type": "module",