wolfpack-mcp 1.0.81 → 1.0.82
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +5 -1
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -862,7 +862,9 @@ class WolfpackMCPServer {
|
|
|
862
862
|
'Call this before updating to see current content. ' +
|
|
863
863
|
'WORKFLOW: When asked to work on an item, check its status and follow the required state transitions ' +
|
|
864
864
|
'(pending→pull first, new→doing, review→doing when you are picking the work back up, ' +
|
|
865
|
-
'
|
|
865
|
+
'ready/completed/closed→new→doing, then review when done). ' +
|
|
866
|
+
'AGENTS: a "blocked" item is not yours to restart — a human clears the blocker. Leave it where it is, ' +
|
|
867
|
+
'comment if you can help clear it, and take the next claimable item instead. ' +
|
|
866
868
|
'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. ' +
|
|
867
869
|
'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. ' +
|
|
868
870
|
'REVIEW CHECKS: items under review may carry review checks (code-review, security-review, ...); see list_work_item_checks and claim/complete_work_item_check. ' +
|
|
@@ -913,6 +915,7 @@ class WolfpackMCPServer {
|
|
|
913
915
|
'STATUS WORKFLOW: "pending" (backlog) → "new" (to do) → "doing" (in progress) → "review" (work done) → "ready" (awaiting deployment) → "completed" (deployed). ' +
|
|
914
916
|
'Use "blocked" when work cannot proceed. AGENTS: you cannot start un-started work here — ' +
|
|
915
917
|
'a status change on a "pending" or "new" item that is not assigned to you is refused. ' +
|
|
918
|
+
'Nor can you move an item OUT of "blocked": clearing a blocker is a human decision. ' +
|
|
916
919
|
'Take it with pull_work_item, which assigns it to you and puts it in "doing"; that is ' +
|
|
917
920
|
'what makes the board show who is working on what. ' +
|
|
918
921
|
'When moving to "review", add a completion comment via create_work_item_comment. When moving to "blocked", add a comment explaining the blocker. ' +
|
|
@@ -1068,6 +1071,7 @@ class WolfpackMCPServer {
|
|
|
1068
1071
|
description: 'List review checks (key controls such as code-review, security-review, e2e-review) on work items. ' +
|
|
1069
1072
|
'With work_item_id: every check on that item. Without it: your REVIEWER INBOX — pending checks on ' +
|
|
1070
1073
|
'work items in the work pools you belong to that are unclaimed or held by you, each with workItemRefId and workItemTitle. ' +
|
|
1074
|
+
'Checks on blocked items are left out — blocked work is not picked up, and claiming one is refused. ' +
|
|
1071
1075
|
'REVIEW WORKFLOW: claim a check with claim_work_item_check, get_work_item to read the work, review it, ' +
|
|
1072
1076
|
'then complete_work_item_check with "passed" or "failed" and a short summary. ' +
|
|
1073
1077
|
'A failed check sends the item back to its developer with your summary as feedback; do not change the item status yourself.',
|