wolfpack-mcp 1.0.76 → 1.0.78

package/README.md

@@ -232,7 +232,8 @@ Get a specific issue.
 
 #### `create_issue`
 
-Create a new issue.
+Create a new issue. Human callers only — issues are how the people using the product report problems
+they hit, so an agent files what it finds with `create_work_item` instead.
 
 - `title` (required): Issue title
 - `description`, `severity`, `type`, `assigned_to_id`, `environment`, `affected_version`, `reproducible`,

package/dist/index.js

@@ -828,7 +828,8 @@ class WolfpackMCPServer {
                             '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). ' +
+                            '(pending→pull first, new→doing, review→doing when you are picking the work back up, ' +
+                            '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. ' +
                             'FORMS: Procedure-created work items may include formDefinition (field definitions with name, label, type, required, options) and formValues (current values). Use submit_work_item_form to fill in form values. ' +
                             'IMAGES: Image references in the description (e.g. `![alt](/api/files/...)`) can be viewed using the download_image tool.',
@@ -850,7 +851,7 @@ 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. ' +
-                            'STATUS: Items in "new" are auto-advanced to "doing" (updating progress means work has started). Completing the work is NOT auto-detected: when done, set status to "review" via update_work_item and add a completion comment. ' +
+                            'STATUS: Items in "new" — and items in "review" you are picking back up — are auto-advanced to "doing" (recording progress means work is under way). Completing the work is NOT auto-detected: when done, set status to "review" via update_work_item and add a completion comment. ' +
                             '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). ' +
                             CONTENT_LINKING_HELP,
@@ -876,8 +877,12 @@ class WolfpackMCPServer {
                             'Supports: title, description, status, leading_user_id (assignee), assisting_user1/2/3_id, ' +
                             'radar_item_id (initiative), category_id, priority (0-4), size (S/M/L), work_pool_id, tags, and closing_comment. ' +
                             'STATUS WORKFLOW: "pending" (backlog) → "new" (to do) → "doing" (in progress) → "review" (work done) → "ready" (awaiting deployment) → "completed" (deployed). ' +
-                            'Use "blocked" when work cannot proceed. For "pending" items use pull_work_item first. ' +
+                            'Use "blocked" when work cannot proceed. AGENTS: you cannot start un-started work here — ' +
+                            'a status change on a "pending" or "new" item that is not assigned to you is refused. ' +
+                            'Take it with pull_work_item, which assigns it to you and puts it in "doing"; that is ' +
+                            'what makes the board show who is working on what. ' +
                             'When moving to "review", add a completion comment via create_work_item_comment. When moving to "blocked", add a comment explaining the blocker. ' +
+                            'When you take an item back out of "review" to rework it, set it to "doing" first — an item being changed is not an item waiting to be reviewed. ' +
                             'closing_comment is only accepted together with status "closed" — never use it for progress or completion notes.',
                         inputSchema: {
                             type: 'object',
@@ -911,7 +916,7 @@ class WolfpackMCPServer {
                                 },
                                 leading_user_id: {
                                     type: ['string', 'null'],
-                                    description: 'User ID to assign as leading user, or null to unassign',
+                                    description: "User ID to assign as leading user, or null to unassign. Agents may not assign work to themselves — that is the product owner's decision.",
                                 },
                                 radar_item_id: {
                                     type: ['string', 'null'],
@@ -966,15 +971,17 @@ class WolfpackMCPServer {
                     },
                     {
                         name: 'pull_work_item',
-                        description: 'Pull a specific work item from the backlog to the board. ' +
-                            'REQUIRED: Use this when starting work on a "pending" (backlog) item. ' +
-                            'This claims the item (assigns to you) and sets status to "new". ' +
+                        description: 'Pull a specific work item from the backlog to the board, or claim one already on it. ' +
+                            'REQUIRED: Use this when starting work on a "pending" (backlog) item, and to claim an ' +
+                            'unassigned "new" (board) item — approved board work is picked up just like approved ' +
+                            'backlog work. This claims the item (assigns to you); a backlog item also moves to "new". ' +
                             'AGENTS: an item already assigned to you is always pullable, approved or not. An item ' +
                             'that is NOT assigned to you is pullable only if it is routed to a work pool you belong ' +
                             'to AND a human has approved it (approved=true) — pool membership grants the access, ' +
                             'approval grants the go-ahead. An unassigned item in no work pool cannot be pulled by an ' +
                             'agent and will return 403: ask a human to route it to your pool or assign it to you. ' +
-                            'After pulling, move to "doing" to indicate active work, then "review" when done. ' +
+                            'AGENTS: pulling puts the item straight into "doing" — you are taking it to start on it ' +
+                            'now — so there is no separate "move it to doing" step. Move it to "review" when done. ' +
                             'If no assignee is specified, assigns to the API key owner. ' +
                             'In personal projects, items are always assigned to the owner.',
                         inputSchema: {
@@ -982,7 +989,7 @@ class WolfpackMCPServer {
                             properties: {
                                 work_item_id: {
                                     type: 'string',
-                                    description: 'The ID of the work item to pull from backlog',
+                                    description: 'The ID of the work item to pull or claim',
                                 },
                                 leading_user_id: {
                                     type: 'string',
@@ -1209,6 +1216,7 @@ class WolfpackMCPServer {
                     {
                         name: 'create_work_item',
                         description: 'Create a new work item in your current project (auto-selected for single-project users, or use list_projects first for multi-project). Requires mcp:work_items:create permission. ' +
+                            'Agents: work you file lands unassigned in the backlog, whatever status you ask for, and waits there for the product owner to approve and assign it. ' +
                             CONTENT_LINKING_HELP,
                         inputSchema: {
                             type: 'object',
@@ -1248,7 +1256,7 @@ class WolfpackMCPServer {
                                 },
                                 leading_user_id: {
                                     type: 'string',
-                                    description: 'User ID to assign as leading user',
+                                    description: "User ID to assign as leading user. Agents may not assign work to themselves — that is the product owner's decision.",
                                 },
                                 category_id: {
                                     type: 'string',
@@ -1265,6 +1273,7 @@ class WolfpackMCPServer {
                     {
                         name: 'create_issue',
                         description: 'Create a new issue in your current project (auto-selected for single-project users, or use list_projects first for multi-project). Requires mcp:issues:create permission. ' +
+                            'Agents: not for you. Issues are how the people using the product report problems they hit — file what you found with create_work_item instead. ' +
                             CONTENT_LINKING_HELP,
                         inputSchema: {
                             type: 'object',
@@ -2130,12 +2139,16 @@ class WolfpackMCPServer {
                         let workItem = await this.client.updateWorkProgress(parsed.work_item_id, parsed.description, teamSlug);
                         if (workItem) {
                             let summary = `Updated description on: ${workItem.title}`;
-                            // Progress on a "new" item means work has started — advance it to "doing"
-                            if (workItem.status === 'new') {
-                                const advanced = await this.client.updateWorkItem(parsed.work_item_id, { status: 'doing' }, teamSlug);
+                            // Recording progress means the work is under way: a "new" item starts, and an
+                            // item in "review" comes back to "doing" because its developer is working on it
+                            // again (#1787) — otherwise the board keeps showing handed-over work that is
+                            // still being changed.
+                            const previousStatus = workItem.status;
+                            if (previousStatus === 'new' || previousStatus === 'review') {
+                                const advanced = await this.moveToDoing(parsed.work_item_id, teamSlug);
                                 if (advanced) {
                                     workItem = advanced;
-                                    summary += ' (status auto-advanced new → doing)';
+                                    summary += ` (status auto-advanced ${previousStatus} → doing)`;
                                 }
                             }
                             let text = `${summary}\n\n${JSON.stringify(stripUuids(workItem), null, 2)}`;
@@ -2265,7 +2278,7 @@ class WolfpackMCPServer {
                                 content: [
                                     {
                                         type: 'text',
-                                        text: `Pulled "${workItem.title}" from backlog to board (status: new)\n\n${JSON.stringify(stripUuids(workItem), null, 2)}`,
+                                        text: `Claimed "${workItem.title}" (status: ${workItem.status})\n\n${JSON.stringify(stripUuids(workItem), null, 2)}`,
                                     },
                                 ],
                             };
@@ -2965,6 +2978,24 @@ class WolfpackMCPServer {
             }
         });
     }
+    /**
+     * Put a work item in "doing" after progress was recorded on it, and report whether that
+     * stuck. An agent whose work pool may not set "doing" — a reviewer annotating an item in
+     * "review" rather than the developer resuming it — is refused by the backend status
+     * policy; that refusal is the right answer, so it leaves the saved note alone instead of
+     * failing the call the agent actually made.
+     */
+    async moveToDoing(workItemId, teamSlug) {
+        try {
+            return await this.client.updateWorkItem(workItemId, { status: 'doing' }, teamSlug);
+        }
+        catch (error) {
+            if (error && typeof error === 'object' && 'status' in error && error.status === 403) {
+                return null;
+            }
+            throw error;
+        }
+    }
     isImageBuffer(buffer) {
         if (buffer.length < 4)
             return false;

package/dist/workItemReminders.js

@@ -25,6 +25,9 @@ const STATUS_REMINDERS = {
         'BEFORE starting work.',
     doing: 'REMINDER: This work item is in "doing". The moment the work is complete, set status to "review" ' +
         '(update_work_item) and add a completion comment — do not leave it sitting in "doing".',
+    review: 'REMINDER: This work item is in "review" — the work was handed over. If you are picking it back ' +
+        'up (rework, review feedback, a follow-up change), set status to "doing" (update_work_item) BEFORE ' +
+        'starting, so the board shows the work is under way again. If you are reviewing it, leave it where it is.',
 };
 // Reminders to prepend to a get_work_item response, most urgent first.
 export function getWorkItemReminders(status, description, approved) {

package/dist/workItemReminders.test.js

@@ -50,13 +50,18 @@ describe('getWorkItemReminders', () => {
             expect.stringContaining('set status to "review"'),
         ]);
     });
+    it('tells agents picking a reviewed item back up to move it to doing', () => {
+        const reminders = getWorkItemReminders('review', PLAN);
+        expect(reminders).toEqual([expect.stringContaining('set status to "doing"')]);
+        expect(reminders[0]).toContain('If you are reviewing it, leave it where it is');
+    });
     it('adds the no-plan reminder when the description has no plan', () => {
         const reminders = getWorkItemReminders('new', 'Just a description');
         expect(reminders).toHaveLength(2);
         expect(reminders[1]).toContain('no plan');
     });
     it('stays quiet for statuses with no required action', () => {
-        expect(getWorkItemReminders('review', PLAN)).toEqual([]);
         expect(getWorkItemReminders('completed', PLAN)).toEqual([]);
+        expect(getWorkItemReminders('ready', PLAN)).toEqual([]);
     });
 });

package/package.json

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