multi-agents-cli 1.1.52 → 1.1.54

package/core/templates/.agents/backend/API.md

@@ -177,6 +177,24 @@ These apply to every API task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/backend/AUTH.md

@@ -169,6 +169,24 @@ These apply to every auth task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/backend/DB.md

@@ -176,6 +176,24 @@ These apply to every DB task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/backend/EVENTS.md

@@ -175,6 +175,24 @@ These apply to every events task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/backend/INIT.md

@@ -159,6 +159,24 @@ is responsible for populating the actual values in `.env.*` files.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/backend/JOBS.md

@@ -175,6 +175,24 @@ These apply to every jobs task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/backend/LOGIC.md

@@ -201,6 +201,24 @@ These apply to every backend logic task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/backend/TESTING.md

@@ -183,6 +183,24 @@ These apply to every backend testing task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/client/ACCESSIBILITY.md

@@ -178,6 +178,24 @@ These apply to every accessibility task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/client/FORMS.md

@@ -163,6 +163,24 @@ These apply to every form task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/client/LOGIC.md

@@ -195,6 +195,24 @@ These apply to every client logic task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/client/ROUTING.md

@@ -164,6 +164,24 @@ These apply to every routing task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/client/TESTING.md

@@ -165,6 +165,24 @@ These apply to every testing task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/client/UI.md

@@ -156,6 +156,24 @@ These apply to every UI task regardless of framework.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/templates/.agents/shared/SECURITY.md

@@ -178,6 +178,24 @@ These apply to every security task regardless of framework or project type.
 
 ---
 
+## Progress Narration
+
+Before starting each major build phase, emit one plain-English status line:
+
+```
+▶ [Phase name] — [what is being built and why, one line]
+```
+
+Examples:
+- `▶ Exploring existing components — checking current patterns before writing anything`
+- `▶ Building UI primitives — Button, Badge, Card as presentational shells`
+- `▶ Validating output — running tsc and dev server to confirm zero errors`
+
+This is mandatory. It is the only human-readable signal the user gets while
+the agent is working. Keep it specific and honest — not generic filler.
+
+---
+
 ## Workflow
 
 ```

package/core/workflow/sync.js

@@ -53,12 +53,12 @@ const getWorktrees = () => {
 };
 
 const getLocalBranches = () => {
-  const out = gitRead('branch --format=%(refname:short)');
+  const out = gitRead('branch --format=\"%(refname:short)\"');
   return out ? out.split('\n').map(s => s.trim()).filter(Boolean) : [];
 };
 
 const getMergedBranches = () => {
-  const out = gitRead('branch --merged main --format=%(refname:short)');
+  const out = gitRead('branch --merged main --format=\"%(refname:short)\"');
   return out ? out.split('\n').map(s => s.trim()).filter(Boolean) : [];
 };
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "multi-agents-cli",
-  "version": "1.1.52",
+  "version": "1.1.54",
   "description": "Multi-agent workflow orchestration for Claude Code — isolated git worktrees, structured state tracking, autonomous task chaining",
   "keywords": [
     "claude-code",