@yemi33/minions 0.1.586 → 0.1.588

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 0.1.588 (2026-04-08)
+
+### Other
+- refactor: extract shared playbook rules to shared-rules.md
+
 ## 0.1.586 (2026-04-08)
 
 ### Fixes

package/bin/minions.js

@@ -705,11 +705,15 @@ if (!cmd || cmd === 'help' || cmd === '--help' || cmd === '-h') {
 } else if (cmd === 'dash' || cmd === 'dashboard') {
   ensureInstalled();
   // If dashboard is already running, just open the browser
-  const http = require('http');
+  const net = require('net');
   const dashPort = 7331;
-  const probe = http.get(`http://localhost:${dashPort}/api/status`, (res) => {
-    res.resume();
-    // Dashboard is running — open browser
+  const sock = new net.Socket();
+  let handled = false;
+  sock.setTimeout(1000);
+  sock.on('connect', () => {
+    sock.destroy();
+    if (handled) return;
+    handled = true;
     const url = `http://localhost:${dashPort}`;
     console.log(`\n  Dashboard already running: ${url}\n`);
     try {
@@ -717,11 +721,18 @@ if (!cmd || cmd === 'help' || cmd === '--help' || cmd === '-h') {
       execSync(openCmd, { stdio: 'ignore', windowsHide: true });
     } catch {}
   });
-  probe.on('error', () => {
-    // Dashboard not running — start it
+  sock.on('error', () => {
+    if (handled) return;
+    handled = true;
     delegate('dashboard.js', rest);
   });
-  probe.setTimeout(2000, () => { probe.destroy(); delegate('dashboard.js', rest); });
+  sock.on('timeout', () => {
+    sock.destroy();
+    if (handled) return;
+    handled = true;
+    delegate('dashboard.js', rest);
+  });
+  sock.connect(dashPort, '127.0.0.1');
 } else if (engineCmds.has(cmd)) {
   delegate('engine.js', [cmd, ...rest]);
 } else {

package/engine/playbook.js

@@ -216,6 +216,12 @@ function renderPlaybook(type, vars) {
     return null;
   }
 
+  // Inject shared rules (apply to all playbooks)
+  try {
+    const sharedRules = fs.readFileSync(path.join(PLAYBOOKS_DIR, 'shared-rules.md'), 'utf8');
+    if (sharedRules) content += '\n\n' + sharedRules;
+  } catch { /* optional — shared rules file may not exist */ }
+
   // Inject pinned context (always visible to agents) — capped at 4KB
   let pinnedContent = '';
   try { pinnedContent = fs.readFileSync(path.join(MINIONS_DIR, 'pinned.md'), 'utf8'); } catch { /* optional */ }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.586",
+  "version": "0.1.588",
   "description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
   "bin": {
     "minions": "bin/minions.js"

package/playbooks/ask.md

@@ -37,7 +37,6 @@ Write your answer to `{{team_root}}/notes/inbox/{{agent_id}}-answer-{{task_id}}-
 Keep it concise but complete. Write for a senior engineer who wants the real answer, not fluff.
 
 ### 4. Status
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.
 
 ## Rules
 - Do NOT modify any code unless the question explicitly asks you to.

package/playbooks/build-and-test.md

@@ -147,4 +147,3 @@ Replace `<SHORT DESCRIPTION OF FAILURE>` and `<PASTE THE BUILD/TEST ERROR OUTPUT
 
 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.
 
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.

package/playbooks/explore.md

@@ -50,7 +50,6 @@ Do NOT create additional worktrees — the engine handles worktree management.
 If the task is purely exploratory (no deliverable requested), skip this step.
 
 ### 6. Status
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.
 
 ## Working Style
 

package/playbooks/fix.md

@@ -64,4 +64,3 @@ Before pushing your fix, run the project's test suite:
 
 Your task is complete once you have: (1) pushed the fix, (2) created or updated the PR, and (3) confirmed tests pass. Do NOT continue exploring unrelated code or making additional improvements. Stop immediately after the fix is verified.
 
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.

package/playbooks/implement-shared.md

@@ -73,4 +73,3 @@ After implementation:
 
 ## Signal Completion
 
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.

package/playbooks/implement.md

@@ -64,7 +64,6 @@ Do NOT remove the worktree — the engine handles cleanup automatically.
 
 Your task is complete once you have: (1) pushed your branch, (2) created the PR, and (3) confirmed the build passes. Do NOT continue exploring, refactoring, or adding features beyond the task description. Stop immediately after the PR is created and verified.
 
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.
 
 ## Build and Demo Rule
 

package/playbooks/plan-to-prd.md

@@ -102,4 +102,3 @@ Rules for items:
 
 ## Signal Completion
 
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.

package/playbooks/plan.md

@@ -93,7 +93,6 @@ High-level design decisions and rationale.
 
 ## Signal Completion
 
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.
 
 ## Team Notes
 {{notes_content}}

package/playbooks/review.md

@@ -71,4 +71,3 @@ If you encounter merge conflicts (e.g., the PR shows conflicts):
 
 Your task is complete once you have: (1) posted your review comment on the PR, and (2) cast your vote. Do NOT continue reading unrelated files or performing additional analysis. Stop after voting.
 
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.

package/playbooks/shared-rules.md

@@ -0,0 +1,7 @@
+## Engine Rules (apply to all tasks)
+
+- Do NOT write to `agents/*/status.json` — the engine manages your status automatically.
+- Do NOT remove worktrees — the engine handles cleanup automatically.
+- Do NOT checkout branches in the main working tree — use worktrees or `git diff`/`git show`.
+- Read `notes.md` for team rules and decisions before starting.
+- If you discover a repeatable workflow, output it as a ```skill block (the engine auto-extracts it).

package/playbooks/test.md

@@ -63,6 +63,5 @@ Include:
 - The run command (absolute paths, copy-pasteable from any terminal)
 - Localhost URL if applicable
 
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.
 
 Do NOT remove worktrees — the engine handles cleanup automatically.

package/playbooks/verify.md

@@ -150,4 +150,3 @@ Use subagents only for genuinely parallel, independent tasks (e.g., building sep
 - Use absolute paths everywhere so the user can copy-paste commands
 - E2E PRs are for review only — do NOT auto-complete or merge them
 
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.

package/playbooks/work-item.md

@@ -50,7 +50,6 @@ Keep branch names lowercase, use hyphens, max 60 chars.
 
 Write your findings to: `{{team_root}}/notes/inbox/{{agent_id}}-{{item_id}}-{{date}}.md`
 
-**Note:** Do NOT write to `agents/*/status.json` — the engine manages your status automatically.
 
 ## Rules
 - Do not checkout branches in the main working tree — use worktrees