chief-clancy 0.2.0 → 0.3.1

package/src/workflows/map-codebase.md

@@ -43,12 +43,16 @@ Each agent is defined in `src/agents/`. Pass the agent the full path to the docs
 
 Tell the user agents are running:
 ```
-Scanning codebase with 5 parallel agents...
-  tech     → STACK.md, INTEGRATIONS.md
-  arch     → ARCHITECTURE.md
-  quality  → CONVENTIONS.md, TESTING.md, GIT.md, DEFINITION-OF-DONE.md
-  design   → DESIGN-SYSTEM.md, ACCESSIBILITY.md
-  concerns → CONCERNS.md
+🚨 Clancy — Map Codebase
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+"Sending in the task force..." — 5 agents deployed.
+
+  🔍 tech     → STACK.md, INTEGRATIONS.md
+  🔍 arch     → ARCHITECTURE.md
+  🔍 quality  → CONVENTIONS.md, TESTING.md, GIT.md, DEFINITION-OF-DONE.md
+  🔍 design   → DESIGN-SYSTEM.md, ACCESSIBILITY.md
+  🔍 concerns → CONCERNS.md
 ```
 
 ---
@@ -57,11 +61,11 @@ Scanning codebase with 5 parallel agents...
 
 Each agent returns a brief confirmation when done. Display as they complete:
 ```
-  ✓ tech agent complete
-  ✓ arch agent complete
-  ✓ quality agent complete
-  ✓ design agent complete
-  ✓ concerns agent complete
+  ✅ tech agent complete
+  ✅ arch agent complete
+  ✅ quality agent complete
+  ✅ design agent complete
+  ✅ concerns agent complete
 ```
 
 ---
@@ -102,12 +106,9 @@ git commit -m "docs(clancy): map codebase — generate .clancy/docs/"
 ## Step 7 — Final message
 
 ```
-Codebase mapped. Clancy is ready.
-
-Docs written to .clancy/docs/ (10 files)
+✅ Codebase mapped — 10 files written to .clancy/docs/
 
-Run /clancy:once to pick up your first ticket.
-Run /clancy:run to process the full queue.
+"Case closed. All files accounted for." — Run /clancy:once to pick up your first ticket, or /clancy:run to process the queue.
 ```
 
 ---

package/src/workflows/once.md

@@ -4,7 +4,7 @@ Before doing anything else, check for updates:
 
 1. Run: `npm show chief-clancy version`
 2. Read the installed version from the Clancy `package.json`
-3. If a newer version exists, print: `ℹ Clancy v{current} → v{latest} available. Run /clancy:update to upgrade.` then continue normally.
+3. If a newer version exists, print: `ℹ️ Clancy v{current} → v{latest} available. Run /clancy:update to upgrade.` then continue normally.
 4. If already on latest, continue silently.
 5. If the npm check fails for any reason (offline, network error), continue silently. Never block on this.
 
@@ -32,12 +32,12 @@ Pick up exactly one ticket from the Kanban board, implement it, commit, squash-m
    ```
    Stop.
 
-3. The script to run is always `.clancy/clancy-once.sh` regardless of board.
-   `/clancy:init` copies the correct board variant as `clancy-once.sh` during setup.
+3. The script to run is always `.clancy/clancy-once.js` regardless of board.
+   `/clancy:init` copies the correct board variant as `clancy-once.js` during setup.
 
-4. Check `.clancy/clancy-once.sh` exists. If not:
+4. Check `.clancy/clancy-once.js` exists. If not:
    ```
-   .clancy/clancy-once.sh not found. Run /clancy:init to scaffold scripts.
+   .clancy/clancy-once.js not found. Run /clancy:init to scaffold scripts.
    ```
    Stop.
 
@@ -51,24 +51,30 @@ Check if the user passed `--dry-run` as an argument to the slash command.
 
 Display:
 ```
-Running Clancy for one ticket.
+🚨 Clancy — Once
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+"I'm on the case." — Running for one ticket.
 ```
 
 Execute:
 ```bash
-bash .clancy/clancy-once.sh
+node .clancy/clancy-once.js
 ```
 
 **With `--dry-run`:**
 
 Display:
 ```
-Running Clancy in dry-run mode — no changes will be made.
+🚨 Clancy — Dry Run
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+"Just a routine patrol." — Running in dry-run mode, no changes will be made.
 ```
 
 Execute:
 ```bash
-bash .clancy/clancy-once.sh --dry-run
+node .clancy/clancy-once.js --dry-run
 ```
 
 Stream output directly — do not buffer or summarise.
@@ -79,13 +85,16 @@ Stream output directly — do not buffer or summarise.
 
 On success, echo the result line from the script output:
 ```
-✓ {TICKET-KEY} complete.
+✅ {TICKET-KEY} complete.
+
+"That's some fine police work there, Lou."
 ```
 
 On failure:
 ```
-Clancy stopped. See output above for details.
-Run /clancy:status to check the board, or /clancy:review to inspect the ticket.
+❌ Clancy stopped. See output above for details.
+
+"Looks like we've got ourselves a 23-19." — Run /clancy:status to check the board, or /clancy:review to inspect the ticket.
 ```
 
 ---
@@ -94,3 +103,4 @@ Run /clancy:status to check the board, or /clancy:review to inspect the ticket.
 
 - Do not loop. This command runs the script exactly once and stops.
 - Do not attempt to run scripts from `src/templates/` — only scripts in `.clancy/`.
+- The runtime scripts in `.clancy/` are self-contained bundles — no npm package dependency needed at runtime.

package/src/workflows/review.md

@@ -14,9 +14,9 @@ Same as status workflow. Check `.clancy/`, `.clancy/.env`, and board credentials
 
 ## Step 2 — Fetch next ticket
 
-Detect board from `.clancy/.env` and fetch with `maxResults=1`. The query must match `clancy-once.sh` exactly — what review shows is what run would pick up.
+Detect board from `.clancy/.env` and fetch with `maxResults=1`. The query must match the once-runner exactly — what review shows is what run would pick up.
 
-**Jira:** Build JQL using the same clauses as `clancy-once.sh`:
+**Jira:** Build JQL using the same clauses as the once-runner:
 - Sprint clause: include `AND sprint in openSprints()` if `CLANCY_JQL_SPRINT` is set
 - Label clause: include `AND labels = "$CLANCY_LABEL"` if `CLANCY_LABEL` is set
 - `CLANCY_JQL_STATUS` defaults to `To Do` if not set
@@ -43,7 +43,12 @@ Fetch full ticket content: summary, description (full text), acceptance criteria
 
 If no tickets found:
 ```
+🚨 Clancy — Review
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
 No tickets in the queue. Nothing to review.
+
+"Quiet. Too quiet." — Check your board or run /clancy:status.
 ```
 Stop.
 
@@ -108,43 +113,51 @@ Bad: "Ensure design specs are provided"
 ## Step 5 — Display output
 
 ```
-Reviewing: [{TICKET-KEY}] {Summary}
-
-Confidence: {score}% — {band label}
+🚨 Clancy — Review
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
+[{TICKET-KEY}] {Summary}
+
+Confidence: {score}% — {badge} {band label}
+
 {for each criterion:}
-✓ {criterion name} — {pass reason}
-⚠ {criterion name} — {warn reason}
-  → {specific recommendation}
-✗ {criterion name} — {fail reason}
-  → {specific recommendation}
-
-Verdict: {action based on band}
-         {next step options}
+✅ {criterion name} — {pass reason}
+⚠️ {criterion name} — {warn reason}
+   → {specific recommendation}
+❌ {criterion name} — {fail reason}
+   → {specific recommendation}
+
+{verdict line}
+
+{sign-off quote}
 ```
 
 ### Confidence bands
 
-| Score | Label | Verdict action |
-|---|---|---|
-| 85–100% | Ready | "Run with confidence." |
-| 65–84% | Good to go with caveats | "Review the warnings above, then run /clancy:once." |
-| 40–64% | Needs work | "Address the ✗ items in the ticket, then re-run /clancy:review." |
-| 0–39% | Not ready | "This ticket needs significant rework before Clancy can implement it reliably." |
+| Score | Badge | Label | Verdict action |
+|---|---|---|---|
+| 85–100% | 🟢 | Ready | "Run with confidence." |
+| 65–84% | 🟡 | Good to go with caveats | "Review the warnings above, then run /clancy:once." |
+| 40–64% | 🟠 | Needs work | "Address the ❌ items in the ticket, then re-run /clancy:review." |
+| 0–39% | 🔴 | Not ready | "This ticket needs significant rework before Clancy can implement it reliably." |
 
 **Executability override:** If criterion 7 (Clancy executability) scores Fail, ignore the calculated band and show:
 ```
-Verdict: Not ready for Clancy
-         This ticket requires work outside the codebase — Clancy can only implement code changes.
-         Update the ticket to focus on the codebase side, or remove it from the queue.
+🔴 Verdict: Not ready for Clancy
+   This ticket requires work outside the codebase — Clancy can only implement code changes.
+   Update the ticket to focus on the codebase side, or remove it from the queue.
+
+   "This is Papa Bear. Put out an APB for a better ticket spec."
 ```
 
-Next-step line per band (append after the verdict — never suggest bypassing the review on low-confidence tickets):
-- **Ready:** `Run /clancy:once to pick it up.`
-- **Good to go:** `Fix the warnings if possible, then run /clancy:once.`
-- **Needs work:** `Update the ticket to address the ✗ items above, then re-run /clancy:review.`
-- **Not ready / executability override:** `Rework the ticket first — do not run Clancy on it yet.`
+### Sign-off quotes per band
+
+Append a Wiggum-themed quote after the verdict to add personality. Never suggest bypassing the review on low-confidence tickets:
+
+- **🟢 Ready:** `"Bake 'em away, toys." — Run /clancy:once to pick it up.`
+- **🟡 Good to go:** `"I'd rather let Herman go. I don't think we've got enough to nail him." — Fix the warnings, then run /clancy:once.`
+- **🟠 Needs work:** `"Uh, no. You got the wrong number. This is 9-1... 2." — Update the ticket, then re-run /clancy:review.`
+- **🔴 Not ready:** `"This is Papa Bear. Put out an APB for a better ticket spec." — Rework the ticket first.`
 
 ---
 

package/src/workflows/run.md

@@ -4,7 +4,7 @@ Before doing anything else, check for updates:
 
 1. Run: `npm show chief-clancy version`
 2. Read the installed version from the Clancy `package.json`
-3. If a newer version exists, print: `ℹ Clancy v{current} → v{latest} available. Run /clancy:update to upgrade.` then continue normally.
+3. If a newer version exists, print: `ℹ️ Clancy v{current} → v{latest} available. Run /clancy:update to upgrade.` then continue normally.
 4. If already on latest, continue silently.
 5. If the npm check fails for any reason (offline, network error), continue silently. Never block on this.
 
@@ -28,14 +28,17 @@ The command may be invoked as `/clancy:run` or `/clancy:run N` where N is a posi
 If the resolved value of `MAX_ITERATIONS` is **10 or greater**, show a warning before continuing:
 
 ```
-⚠ You're about to run Clancy for up to {N} tickets.
+🚨 Clancy — Run
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+⚠️ You're about to run Clancy for up to {N} tickets.
 
 At rough estimates per ticket (Sonnet):
   Simple tickets  ~$0.25–$0.75 each  →  up to ~${low} total
   Complex tickets ~$2.00–$5.00 each  →  up to ~${high} total
 
-Mistakes compound — if Claude misreads a ticket, it will do so {N} times before you check.
-Consider starting with /clancy:once or a smaller run to validate first.
+"Slow down there, cowboy..." — Mistakes compound. If Claude misreads a ticket, it will do so {N} times.
+Consider /clancy:once or a smaller run to validate first.
 
 Continue with {N} tickets? [Y/n]
 ```
@@ -72,9 +75,9 @@ If the user types `n` or `N`: print `Cancelled.` and stop. Any other input (incl
    ```
    Stop.
 
-4. Check `.clancy/clancy-afk.sh` exists. If not:
+4. Check `.clancy/clancy-afk.js` exists. If not:
    ```
-   .clancy/clancy-afk.sh not found. Run /clancy:init to scaffold scripts.
+   .clancy/clancy-afk.js not found. Run /clancy:init to scaffold scripts.
    ```
    Stop.
 
@@ -82,9 +85,12 @@ If the user types `n` or `N`: print `Cancelled.` and stop. Any other input (incl
 
 ## Step 3 — Start
 
-Display:
+Display (only if the high-iteration warning was not already shown):
 ```
-Starting Clancy — will process up to {N} ticket(s). Ctrl+C to stop early.
+🚨 Clancy — Run
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+"All right, let's do this." — Processing up to {N} ticket(s). Ctrl+C to stop early.
 ```
 
 ---
@@ -93,7 +99,7 @@ Starting Clancy — will process up to {N} ticket(s). Ctrl+C to stop early.
 
 Execute:
 ```bash
-MAX_ITERATIONS={N} bash .clancy/clancy-afk.sh
+MAX_ITERATIONS={N} node .clancy/clancy-afk.js
 ```
 
 Stream output directly — do not buffer or summarise.
@@ -104,10 +110,11 @@ Stream output directly — do not buffer or summarise.
 
 When the script exits, echo the final summary line from the output.
 
-If `clancy-afk.sh` exits with a non-zero status:
+If `clancy-afk.js` exits with a non-zero status:
 ```
-Clancy stopped with an error. Check the output above.
-Run /clancy:once for more detail on the next ticket.
+❌ Clancy stopped with an error. Check the output above.
+
+"Looks like we've got ourselves a 23-19." — Run /clancy:once for more detail on the next ticket.
 ```
 
 ---
@@ -117,3 +124,4 @@ Run /clancy:once for more detail on the next ticket.
 - The `N` argument is session-only. It never modifies `.clancy/.env`.
 - If the user wants to permanently change their default, they edit `.clancy/.env` directly or re-run `/clancy:init` advanced setup.
 - Do not attempt to run scripts from `src/templates/` — only run scripts in `.clancy/`.
+- The runtime scripts in `.clancy/` are self-contained bundles — no npm package dependency needed at runtime.