@yemi33/minions 0.1.188 → 0.1.189
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
|
@@ -70,7 +70,7 @@ function derivePlanStatus(prdFile, mdFile, prdJsonStatus, workItems) {
|
|
|
70
70
|
w.sourcePlan === prdFile || w.sourcePlan === mdFile ||
|
|
71
71
|
(w.type === 'plan-to-prd' && (w.planFile === prdFile || w.planFile === mdFile))
|
|
72
72
|
);
|
|
73
|
-
const implementWi = wi.filter(w => w.type !== 'plan-to-prd' && w.type !== 'verify');
|
|
73
|
+
const implementWi = wi.filter(w => w.type !== 'plan-to-prd' && w.type !== 'verify' && w.type !== 'evaluate');
|
|
74
74
|
const hasPendingPrd = wi.some(w => w.type === 'plan-to-prd' && (w.status === 'pending' || w.status === 'dispatched'));
|
|
75
75
|
const hasActiveWork = implementWi.some(w => w.status === 'pending' || w.status === 'dispatched');
|
|
76
76
|
const allDone = implementWi.length > 0 && implementWi.every(w => w.status === 'done');
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@yemi33/minions",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.189",
|
|
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"
|
|
@@ -34,42 +34,4 @@ Write a clear meeting conclusion covering:
|
|
|
34
34
|
|
|
35
35
|
Be decisive. If there's a clear best option, say so.
|
|
36
36
|
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
After writing the conclusion, decide: **are there concrete action items that require implementation work?**
|
|
40
|
-
|
|
41
|
-
- **If YES** — write a plan file to `plans/<slugified-meeting-title>-<YYYY-MM-DD>.md` using the Minions plan format below. Only create this file if there are real, actionable implementation tasks — not just discussion points or observations.
|
|
42
|
-
|
|
43
|
-
- **If NO** — do not create a plan file. A conclusion with only open questions, observations, or decisions that require no code/implementation changes does not need a plan.
|
|
44
|
-
|
|
45
|
-
### Plan format (only if action items exist)
|
|
46
|
-
|
|
47
|
-
```markdown
|
|
48
|
-
# <Plan Title>
|
|
49
|
-
|
|
50
|
-
> Source: Meeting {{meeting_title}} — <date>
|
|
51
|
-
|
|
52
|
-
## Background
|
|
53
|
-
|
|
54
|
-
<1-2 sentence summary of why this plan exists, from the meeting conclusion>
|
|
55
|
-
|
|
56
|
-
## Tasks
|
|
57
|
-
|
|
58
|
-
### 1. <Task title>
|
|
59
|
-
- **What**: <what needs to be done>
|
|
60
|
-
- **Why**: <from the meeting — what problem does this fix>
|
|
61
|
-
- **Owner**: <agent role best suited: Engineer / Architect / Analyst>
|
|
62
|
-
- **Files**: <relevant files if known>
|
|
63
|
-
|
|
64
|
-
### 2. <Task title>
|
|
65
|
-
...
|
|
66
|
-
|
|
67
|
-
## Open Questions
|
|
68
|
-
|
|
69
|
-
<Any unresolved items that need human input before work begins>
|
|
70
|
-
```
|
|
71
|
-
|
|
72
|
-
Do NOT create a plan for:
|
|
73
|
-
- Informational findings with no follow-up work
|
|
74
|
-
- Decisions that have already been made and require no changes
|
|
75
|
-
- Items that are purely "monitor and observe"
|
|
37
|
+
Do NOT create plan files — plan creation is handled separately (by the pipeline plan stage or the dashboard "Create Plan" button).
|