@yemi33/minions 0.1.629 → 0.1.630
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/CHANGELOG.md
CHANGED
|
@@ -1,8 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
-
## 0.1.
|
|
3
|
+
## 0.1.630 (2026-04-08)
|
|
4
4
|
|
|
5
5
|
### Fixes
|
|
6
|
+
- add 'When to Stop' to remaining 5 playbooks
|
|
6
7
|
- hold _ccSending during abort delay, check wasAborted per queue item
|
|
7
8
|
- abort+queue sends queued message after brief delay, not discard
|
|
8
9
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@yemi33/minions",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.630",
|
|
4
4
|
"description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
|
|
5
5
|
"bin": {
|
|
6
6
|
"minions": "bin/minions.js"
|
|
@@ -147,3 +147,7 @@ Replace `<SHORT DESCRIPTION OF FAILURE>` and `<PASTE THE BUILD/TEST ERROR OUTPUT
|
|
|
147
147
|
|
|
148
148
|
Leave the worktree in place at `{{project_path}}/../worktrees/bt-{{pr_number}}` — the user needs it to review the running app. The engine will clean it up after the PR is merged or closed.
|
|
149
149
|
|
|
150
|
+
|
|
151
|
+
## When to Stop
|
|
152
|
+
|
|
153
|
+
Your task is complete once you have: (1) built the project, (2) run tests, (3) started the app if applicable, and (4) written your findings to the inbox file. Stop after writing findings.
|
|
@@ -40,3 +40,7 @@ Write a clear, **self-contained** meeting conclusion. Someone reading ONLY this
|
|
|
40
40
|
**Be concrete, not vague.** Do NOT write "fix 3 bugs" — write which 3 bugs, in which files, with what fix. The conclusion is used as input to create an implementation plan, so it must contain enough detail to act on without re-reading the entire meeting.
|
|
41
41
|
|
|
42
42
|
Do NOT create plan files — plan creation is handled separately (by the pipeline plan stage or the dashboard "Create Plan" button).
|
|
43
|
+
|
|
44
|
+
## When to Stop
|
|
45
|
+
|
|
46
|
+
Your task is complete once you have written the conclusion with action items. Do NOT create plan files or begin implementation. Stop after writing the conclusion.
|
|
@@ -33,3 +33,7 @@ Be direct. Constructive disagreement is encouraged — don't just agree with eve
|
|
|
33
33
|
## Output Format
|
|
34
34
|
|
|
35
35
|
Write your debate response as markdown. Reference other agents' findings by name.
|
|
36
|
+
|
|
37
|
+
## When to Stop
|
|
38
|
+
|
|
39
|
+
Your task is complete once you have written your debate response. Do NOT attempt fixes or implementations. Stop after presenting your position.
|
|
@@ -28,3 +28,7 @@ Focus on what YOU uniquely bring to this discussion. Be thorough but concise.
|
|
|
28
28
|
## Output Format
|
|
29
29
|
|
|
30
30
|
Write your findings as a clear markdown document. Start with your key conclusion, then supporting evidence.
|
|
31
|
+
|
|
32
|
+
## When to Stop
|
|
33
|
+
|
|
34
|
+
Your task is complete once you have written your findings as markdown in your response. Do NOT attempt fixes or implementations. Stop after presenting your analysis.
|
package/playbooks/verify.md
CHANGED
|
@@ -150,3 +150,7 @@ Use subagents only for genuinely parallel, independent tasks (e.g., building sep
|
|
|
150
150
|
- Use absolute paths everywhere so the user can copy-paste commands
|
|
151
151
|
- E2E PRs are for review only — do NOT auto-complete or merge them
|
|
152
152
|
|
|
153
|
+
|
|
154
|
+
## When to Stop
|
|
155
|
+
|
|
156
|
+
Your task is complete once you have: (1) merged dependency branches, (2) built and tested, (3) written the verification report to both locations, and (4) created the E2E PR(s). Stop after creating PRs.
|