wolfpack-mcp 1.0.16 → 1.0.18

package/dist/index.js

@@ -223,6 +223,18 @@ const CreateIssueCommentSchema = z.object({
     issue_id: z.string().describe('The issue UUID'),
     content: z.string().describe('Comment content (markdown)'),
 });
+// Helper to detect if a work item description contains a plan
+function hasPlan(description) {
+    if (!description)
+        return false;
+    // Check for markdown checklist items (plan indicators)
+    if (/- \[[ x]\]/.test(description))
+        return true;
+    // Check for --- separator with content after (agent-added section)
+    if (/\n---\n/.test(description))
+        return true;
+    return false;
+}
 class WolfpackMCPServer {
     server;
     client;
@@ -246,12 +258,13 @@ class WolfpackMCPServer {
                 {
                     name: 'list_teams',
                     description: 'List all teams (projects) you have access to. ' +
+                        'TERMINOLOGY: In this software, "team" and "project" are synonymous and interchangeable. All tool names and parameters use "team" (e.g., team_id), but the concepts are identical. ' +
                         'IMPORTANT - PROJECT FOCUS RULES: ' +
-                        '1) Call this FIRST to identify which project you are working in. ' +
-                        '2) Once you identify a project, STAY WITHIN that project for all operations unless the user explicitly asks to switch projects. ' +
-                        '3) NEVER perform bulk actions across multiple projects - always work in one project at a time. ' +
-                        '4) If the user mentions a specific project, use that project for all subsequent operations. ' +
-                        '5) If unclear which project to use, ASK the user before proceeding. ' +
+                        '1) Call this FIRST to identify which team/project you are working in. ' +
+                        '2) Once you identify a team, STAY WITHIN that team for all operations unless the user explicitly asks to switch. ' +
+                        '3) NEVER perform bulk actions across multiple teams - always work in one team at a time. ' +
+                        '4) If the user mentions a specific team or project, use that for all subsequent operations. ' +
+                        '5) If unclear which team to use, ASK the user before proceeding. ' +
                         'Returns team IDs, slugs, and names. Single-team users have their team auto-selected; multi-team users must specify team_id in other tool calls.',
                     inputSchema: {
                         type: 'object',
@@ -790,8 +803,15 @@ class WolfpackMCPServer {
                         const parsed = GetWorkItemSchema.parse(args);
                         const workItem = await this.client.getWorkItem(parsed.work_item_id, parsed.team_id || this.client.getTeamId() || undefined);
                         if (workItem) {
+                            let text = JSON.stringify(workItem, null, 2);
+                            // Add hint if no plan detected in description
+                            if (!hasPlan(workItem.description)) {
+                                text =
+                                    'REMINDER: This work item has no plan. Before starting work, use update_work_progress to add a plan below a "---" separator. Preserve the original description and append your plan with markdown checkboxes (- [ ] task).\n\n' +
+                                        text;
+                            }
                             return {
-                                content: [{ type: 'text', text: JSON.stringify(workItem, null, 2) }],
+                                content: [{ type: 'text', text }],
                             };
                         }
                         return {

package/package.json

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