chief-clancy 0.2.0-beta.3 → 0.3.0

package/src/workflows/doctor.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.
 
@@ -22,7 +22,7 @@ Diagnose your Clancy setup — test every configured integration and report what
 
 - Verify Clancy commands are installed (`.claude/commands/clancy/` or `~/.claude/commands/clancy/`)
 - Read installed version from `package.json` in the commands directory
-- Print: `✓ Clancy v{version} installed ({location})`
+- Print: `✅ Clancy v{version} installed ({location})`
 
 ---
 
@@ -32,24 +32,23 @@ Test each required binary:
 
 | Binary | Check | Fix hint |
 |---|---|---|
-| `jq` | `command -v jq` | `brew install jq` / `apt install jq` |
-| `curl` | `command -v curl` | Install curl for your OS |
+| `node` | `command -v node` | Install Node.js 22+ |
 | `git` | `command -v git` | Install git for your OS |
 
-Print `✓` or `✗` for each.
+Print `✅` or `❌` for each.
 
 ---
 
 ## Step 3 — Check project setup
 
-- `.clancy/` exists → `✓ .clancy/ found`
-- `.clancy/clancy-once.sh` exists and is executable → `✓ clancy-once.sh`
-- `.clancy/clancy-afk.sh` exists and is executable → `✓ clancy-afk.sh`
-- `.clancy/.env` exists → `✓ .clancy/.env found`
-- `.clancy/docs/` has non-empty files → `✓ codebase docs present ({N} files)`
+- `.clancy/` exists → `✅ .clancy/ found`
+- `.clancy/clancy-once.js` exists → `✅ clancy-once.js`
+- `.clancy/clancy-afk.js` exists → `✅ clancy-afk.js`
+- `.clancy/.env` exists → `✅ .clancy/.env found`
+- `.clancy/docs/` has non-empty files → `✅ codebase docs present ({N} files)`
 
-If `.clancy/` is missing: `✗ .clancy/ not found — run /clancy:init`
-If `.clancy/.env` is missing: `✗ .clancy/.env not found — run /clancy:init`
+If `.clancy/` is missing: `❌ .clancy/ not found — run /clancy:init`
+If `.clancy/.env` is missing: `❌ .clancy/.env not found — run /clancy:init`
 
 ---
 
@@ -78,8 +77,8 @@ Source `.clancy/.env` and detect which board is configured:
 
 **Figma** — if `FIGMA_API_KEY` is set:
 - Call `GET https://api.figma.com/v1/me` with `X-Figma-Token: $FIGMA_API_KEY`
-- On success: print `✓ Figma connected — {email}`
-- On 403: print `✗ Figma authentication failed. Check FIGMA_API_KEY in .clancy/.env.`
+- On success: print `✅ Figma connected — {email}`
+- On 403: print `❌ Figma authentication failed. Check FIGMA_API_KEY in .clancy/.env.`
 - Note: Figma's API does not expose plan information — check your plan at figma.com/settings
 
 **Playwright** — if `PLAYWRIGHT_ENABLED=true`:
@@ -97,19 +96,29 @@ Source `.clancy/.env` and detect which board is configured:
 ## Step 6 — Summary
 
 ```
-Clancy doctor — {N} checks passed, {N} warnings, {N} failures
+🚨 Clancy — Doctor
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-✓ Clancy v0.1.0 installed (global)
-✓ jq, curl, git — all present
-✓ .clancy/ set up — 10 docs present
-✓ Jira connected — PROJ reachable
-✓ Figma connected — alex@example.com (check plan at figma.com/settings)
-✗ PLAYWRIGHT_STORYBOOK_PORT — not set in .clancy/.env
+{N} checks passed, {N} warnings, {N} failures
 
-Fix the ✗ items, then run /clancy:once to verify end-to-end.
+✅ Clancy v0.1.0 installed (global)
+✅ node, git — all present
+✅ .clancy/ set up — 10 docs present
+✅ Jira connected — PROJ reachable
+✅ Figma connected — alex@example.com (check plan at figma.com/settings)
+❌ PLAYWRIGHT_STORYBOOK_PORT — not set in .clancy/.env
+
+Fix the ❌ items, then run /clancy:once to verify end-to-end.
+
+"We've got a 415 in progress — a config disturbance."
 ```
 
 If all checks pass:
 ```
-All good. Run /clancy:once to pick up your first ticket.
+🚨 Clancy — Doctor
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+All {N} checks passed.
+
+"Nothing to see here, folks. Move along." — Run /clancy:once to pick up your first ticket.
 ```

package/src/workflows/init.md

@@ -30,20 +30,20 @@ Before proceeding, silently run `command -v` for each required binary:
 
 | Binary | Install hint |
 |---|---|
-| `jq` | `brew install jq` / `apt install jq` |
-| `curl` | pre-installed on macOS and most Linux |
+| `node` | Install Node.js 22+ (nodejs.org) |
 | `git` | `brew install git` / `apt install git` |
+| `claude` | `npm install -g @anthropic-ai/claude-code` |
 
 If all are present: continue silently.
 
 If any are missing, output:
 
 ```
-⚠ Missing prerequisites:
+⚠️ Missing prerequisites:
 
-  ✗ jq — brew install jq  (or apt install jq on Linux)
+  ❌ node — Install Node.js 22+ (nodejs.org)
 
-Clancy's shell scripts require these binaries to run. Install them, then re-run /clancy:init.
+Clancy requires these binaries to run. Install them, then re-run /clancy:init.
 ```
 
 List only the missing ones. Then stop — do not proceed with setup until prerequisites are satisfied.
@@ -54,9 +54,16 @@ List only the missing ones. Then stop — do not proceed with setup until prereq
 
 Output:
 
+```
+🚨 Clancy — Init
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+"Chief Wiggum reporting for duty."
+
 Clancy pulls tickets from your Kanban board, implements them, commits, and squash-merges — one ticket per run, fresh context every time.
 
 Let's get you set up.
+```
 
 ---
 
@@ -79,13 +86,12 @@ Clancy currently supports Jira, GitHub Issues, and Linear out of the box.
 
 Your board isn't supported yet — but you can add it:
   · Open an issue:   github.com/Pushedskydiver/clancy/issues
-  · Contribute one:  see CONTRIBUTING.md — adding a board is just a script template + a boards.json entry
+  · Contribute one:  see CONTRIBUTING.md — adding a board is a TypeScript module + a boards.json entry
 
 In the meantime, you can still use Clancy manually:
   · Run /clancy:map-codebase to scan and document your codebase
-  · Use the clancy-once.sh template from the GitHub repo as a starting point
-  · Implement your board's API fetch, store credentials in .clancy/.env
-  · Point clancy-afk.sh at your custom script via CLANCY_ONCE_SCRIPT in .clancy/.env
+  · Add `chief-clancy` as a devDependency and implement your board's API module
+  · Store credentials in .clancy/.env
 
 Do not scaffold anything after this message. Stop completely.
 
@@ -124,6 +130,65 @@ If enter is pressed with no value: skip — omit the label clause entirely (Clan
 
 ---
 
+### Q2b: Board credential verification
+
+After collecting all credentials for the chosen board, verify the connection before continuing.
+
+**Jira** — call `GET {JIRA_BASE_URL}/rest/api/3/project/{JIRA_PROJECT_KEY}` with basic auth (`{JIRA_USER}:{JIRA_API_TOKEN}` base64-encoded in the `Authorization: Basic` header).
+
+On success (HTTP 200), show:
+```
+✅ Jira connected — project {JIRA_PROJECT_KEY} reachable.
+```
+
+On failure, show:
+```
+❌ Couldn't connect to Jira (HTTP {status}).
+Check your credentials in the values you just entered.
+
+[1] Re-enter credentials
+```
+
+If [1]: go back to Q2 and re-ask all Jira questions. If the user wants to abandon setup entirely, they can Ctrl+C.
+
+**GitHub Issues** — call `GET https://api.github.com/repos/{GITHUB_REPO}` with `Authorization: Bearer {GITHUB_TOKEN}` and `X-GitHub-Api-Version: 2022-11-28`.
+
+On success (HTTP 200), show:
+```
+✅ GitHub connected — {GITHUB_REPO} reachable.
+```
+
+On failure, show:
+```
+❌ Couldn't connect to GitHub (HTTP {status}).
+Check your token has `repo` scope and the repo name is correct.
+
+[1] Re-enter credentials
+```
+
+If [1]: go back to Q2 and re-ask all GitHub questions. If the user wants to abandon setup entirely, they can Ctrl+C.
+
+**Linear** — call `POST https://api.linear.app/graphql` with `Authorization: {LINEAR_API_KEY}` (no Bearer prefix) and body `{"query": "{ viewer { id name } }"}`.
+
+On success (HTTP 200 with `data.viewer`), show:
+```
+✅ Linear connected — {viewer.name}.
+```
+
+On failure, show:
+```
+❌ Couldn't connect to Linear.
+Check your API key at linear.app/settings/api.
+
+[1] Re-enter credentials
+```
+
+If [1]: go back to Q2 and re-ask all Linear questions. If the user wants to abandon setup entirely, they can Ctrl+C.
+
+Never silently continue with unverified credentials — the user must fix their credentials or exit with Ctrl+C.
+
+---
+
 ### Q3 (Jira only): Status name
 
 Output:
@@ -134,7 +199,7 @@ Common values: To Do, Selected for Development, Ready, Open
 [1] To Do (default)
 [2] Enter a different value
 
-Store as `CLANCY_JQL_STATUS` in `.clancy/.env`. Always wrap the value in double quotes — status names often contain spaces (e.g. `CLANCY_JQL_STATUS="Selected for Development"`) and unquoted values with spaces cause bash parse errors when the file is sourced.
+Store as `CLANCY_JQL_STATUS` in `.clancy/.env`. Always wrap the value in double quotes — status names often contain spaces (e.g. `CLANCY_JQL_STATUS="Selected for Development"`).
 
 ---
 
@@ -176,9 +241,9 @@ Store the detected (or confirmed) value as `CLANCY_BASE_BRANCH` in `.clancy/.env
 
 Create `.clancy/` directory and the following:
 
-1. Write the correct `clancy-once.sh` for the chosen board to `.clancy/clancy-once.sh` — use the exact script content from scaffold.md, do not generate or modify it
-2. Write `clancy-afk.sh` to `.clancy/clancy-afk.sh` — use the exact script content from scaffold.md, do not generate or modify it
-3. Make both scripts executable: `chmod +x .clancy/*.sh`
+1. Ensure `chief-clancy` is installed as a devDependency: `npm install --save-dev chief-clancy` (skip if already installed)
+2. Write `.clancy/clancy-once.js` — use the exact shim content from scaffold.md, do not generate or modify it
+3. Write `.clancy/clancy-afk.js` — use the exact shim content from scaffold.md, do not generate or modify it
 4. Create `.clancy/docs/` with 10 empty template files (UPPERCASE.md with section headings only):
    - STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, CONVENTIONS.md, TESTING.md
    - GIT.md, DESIGN-SYSTEM.md, ACCESSIBILITY.md, DEFINITION-OF-DONE.md, CONCERNS.md
@@ -198,7 +263,7 @@ Create `.clancy/` directory and the following:
 After scaffolding, commit everything created (excluding `.clancy/.env` which contains credentials):
 
 ```bash
-git add .clancy/clancy-once.sh .clancy/clancy-afk.sh .clancy/.env.example .clancy/docs/ CLAUDE.md .gitignore
+git add .clancy/clancy-once.js .clancy/clancy-afk.js .clancy/.env.example .clancy/docs/ CLAUDE.md .gitignore
 git commit -m "chore(clancy): initialise — scaffold scripts, docs templates, and config"
 ```
 
@@ -240,7 +305,7 @@ If a key is entered:
 1. Verify the key by calling `GET https://api.figma.com/v1/me` with `X-Figma-Token: {key}`
 2. On success, show:
    ```
-   ✓ Figma connected: {email}
+   ✅ Figma connected: {email}
 
    Note: Figma's API does not expose plan information.
    Clancy uses 3 MCP calls per ticket (metadata, design context, screenshot).
@@ -252,7 +317,7 @@ If a key is entered:
 
 If `GET /v1/me` fails (non-200), show:
 ```
-✗ Couldn't verify Figma API key (HTTP {status}).
+❌ Couldn't verify Figma API key (HTTP {status}).
 Double-check it at figma.com/settings → Personal access tokens.
 
 [1] Try a different key
@@ -413,11 +478,15 @@ If no: output "Run /clancy:map-codebase when you're ready." then continue to fin
 
 Output:
 
-Clancy is ready.
+```
+╔═══════════════════════════════════════════════════════════╗
+║  ✅ Clancy is ready.                                     ║
+╚═══════════════════════════════════════════════════════════╝
 
-- Scripts: `.clancy/clancy-once.sh`, `.clancy/clancy-afk.sh`
+- Scripts: `.clancy/clancy-once.js`, `.clancy/clancy-afk.js`
 - Docs: `.clancy/docs/` (10 files)
 - Config: `.clancy/.env`
 - CLAUDE.md: updated
 
-Run `/clancy:dry-run` to preview the first ticket without making changes, `/clancy:once` to pick it up, or `/clancy:run` to process the full queue.
+"Clancy's on the beat." — Run /clancy:dry-run to preview, /clancy:once to pick up a ticket, or /clancy:run to process the queue.
+```

package/src/workflows/logs.md

@@ -10,7 +10,12 @@ Read `.clancy/progress.txt` and present a formatted summary.
 
 If `.clancy/progress.txt` does not exist:
 ```
-No progress logged yet. Run /clancy:once or /clancy:run to get started.
+🚨 Clancy — Logs
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+No progress logged yet.
+
+"The law is powerless to help you... but not for long." — Run /clancy:once or /clancy:run to get started.
 ```
 Stop.
 
@@ -43,15 +48,16 @@ If only 1–3 DONE entries: show a flat list, skip grouping.
 If 4+ entries, show the full grouped display:
 
 ```
-Clancy Progress Log
-───────────────────────────────────────
+🚨 Clancy — Logs
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
 Total tickets completed: {count}
 First run: {YYYY-MM-DD}
 Latest run: {YYYY-MM-DD}
 
 This week ({Mon date}–{Sun date or today}):
-  ✓ {TICKET-KEY}  {Summary}
-  ✓ {TICKET-KEY}  {Summary}
+  ✅ {TICKET-KEY}  {Summary}
+  ✅ {TICKET-KEY}  {Summary}
   ...
 
 By epic:
@@ -59,9 +65,10 @@ By epic:
   {EPIC-KEY} {Epic name or prefix}  {bar}  {count} tickets
   (other)                           {bar}  {count} tickets
 
+Reviews run: {N}
 Full log: .clancy/progress.txt
 
-Reviews run: {N}
+"The law is powerless to help you, but here's what Clancy's done."
 ```
 
 ### Display rules

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 JS shim imports from the installed `chief-clancy` package — ensure it's installed as a devDependency.

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 JS shims import from the installed `chief-clancy` package — ensure it's installed as a devDependency.