multi-agents-cli 1.1.53 → 1.1.55

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

@@ -177,6 +177,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -169,6 +169,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -176,6 +176,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -175,6 +175,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -159,6 +159,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -175,6 +175,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -201,6 +201,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -183,6 +183,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -178,6 +178,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -163,6 +163,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -195,6 +195,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -164,6 +164,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -165,6 +165,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -156,6 +156,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

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

@@ -178,6 +178,32 @@ 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.
+
+### Output Mode
+
+Read `output_mode` from `.claude-scope` at session start. Honor it for the entire session:
+
+- `full`     — no restrictions, behave normally
+- `insights` — emit `▶ narration` lines before each phase; suppress routine file read/write commentary in between
+- `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases, no other output
+
+---
+
 ## Workflow
 
 ```

package/core/templates/CLAUDE.md

@@ -146,7 +146,12 @@ the agent must:
    # then take the parent directory of that path - this is PROJECT_ROOT
    ```
    Store this as PROJECT_ROOT. All subsequent paths (`.scaffold/`, `BUILD_STATE.md`, `CONTRACTS.md`, etc.) resolve from PROJECT_ROOT, never from the worktree directory.
-2. Read `BUILD_STATE.md` at PROJECT_ROOT - understand what has been built
+2. Read `output_mode` from `.claude-scope` in the current worktree directory:
+   - `full`     — default, no restrictions on output
+   - `insights` — emit `▶ narration` lines before each phase only; suppress routine file read/write commentary
+   - `silent`   — emit only git operations, errors, and verification results; show `✢ working...` between phases
+   Store this as OUTPUT_MODE. Apply it consistently for the entire session.
+3. Read `BUILD_STATE.md` at PROJECT_ROOT - understand what has been built
 3. Check if `TASK.md` exists in the current directory
 4. If yes - read it and verify dependencies are met against BUILD_STATE.md
 5. If dependencies not met - surface what is missing and propose options

package/core/workflow/agent.js

@@ -486,6 +486,7 @@ project      : ${project}
 agent        : ${agent}
 branch       : ${branchName}
 worktree     : ${worktreePath}
+output_mode  : ${outputMode}
 
 ## Scope Verification Rule
 Before doing anything else, verify:
@@ -1733,6 +1734,17 @@ ${excludedUrls}
   );
   const skipPermissions = permIdx === 0;
 
+  const outputModeIdx = await arrowSelect(
+    'Agent output mode for this session?',
+    [
+      { label: `${green('→')} Full output      ${dim('— see everything (default)')}` },
+      { label: `${green('→')} Insights only    ${dim('— phase narrations + important blocks')}` },
+      { label: `${green('→')} Silent           ${dim('— spinner + critical blocks only')}` },
+    ],
+    rl
+  );
+  const outputMode = ['full', 'insights', 'silent'][outputModeIdx];
+
   sessionLoop: while (true) {
   const sessionIdx = await arrowSelect('How would you like to start the session?', [
     { label: `${green('→')} IDE + new terminal ${dim('(Claude Code CLI)')}  ${dim('← recommended')}` },

package/package.json

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