@chief-clancy/terminal 0.1.0

package/src/roles/setup/workflows/uninstall.md

@@ -0,0 +1,170 @@
+# Clancy Uninstall Workflow
+
+## Overview
+
+Remove Clancy's slash commands from the local project, globally, or both. Optionally remove the `.clancy/` project folder (which includes `.clancy/.env`). Clean up CLAUDE.md, .gitignore, and .prettierignore changes made during init.
+
+---
+
+## Step 1 — Detect install locations
+
+Check both locations silently. Each install has two parts — commands and workflows:
+
+- **Project-local commands:** `.claude/commands/clancy/`
+- **Project-local workflows:** `.claude/clancy/`
+- **Global commands:** `~/.claude/commands/clancy/`
+- **Global workflows:** `~/.claude/clancy/`
+
+| Scenario              | Action                                                                                           |
+| --------------------- | ------------------------------------------------------------------------------------------------ |
+| Found in both         | Ask: "Remove from project, globally, or both?" → `[1] Project only` `[2] Global only` `[3] Both` |
+| Found in project only | Proceed with project removal                                                                     |
+| Found globally only   | Proceed with global removal                                                                      |
+| Found in neither      | Print "Clancy commands not found. Nothing to remove." and stop                                   |
+
+---
+
+## Step 2 — Confirm before removing commands
+
+Show exactly this message, filling in the detected location:
+
+```
+🚨 Clancy — Uninstall
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+This will remove Clancy's slash commands from [location].
+Your .clancy/ folder will not be touched.
+Continue? (yes / no)
+```
+
+- `no` → print "Nothing removed." and stop
+- `yes` → proceed to remove commands, workflows, hooks, and settings entries (Steps 2a–2c)
+
+If "Both" was chosen in Step 1: confirm once for both, remove everything for both locations.
+
+### Step 2a — Remove command and workflow directories
+
+Delete both the commands directory and the workflows directory for the chosen location(s):
+
+- Project-local: `.claude/commands/clancy/` and `.claude/clancy/`
+- Global: `~/.claude/commands/clancy/` and `~/.claude/clancy/`
+
+Print: `✅ Clancy commands removed from [location].`
+
+### Step 2b — Remove hooks
+
+For each location being removed, delete these hook files if they exist:
+
+- Project-local: `.claude/hooks/clancy-branch-guard.js`, `.claude/hooks/clancy-check-update.js`, `.claude/hooks/clancy-context-monitor.js`, `.claude/hooks/clancy-credential-guard.js`, `.claude/hooks/clancy-drift-detector.js`, `.claude/hooks/clancy-notification.js`, `.claude/hooks/clancy-post-compact.js`, `.claude/hooks/clancy-statusline.js`
+- Global: `~/.claude/hooks/clancy-branch-guard.js`, `~/.claude/hooks/clancy-check-update.js`, `~/.claude/hooks/clancy-context-monitor.js`, `~/.claude/hooks/clancy-credential-guard.js`, `~/.claude/hooks/clancy-drift-detector.js`, `~/.claude/hooks/clancy-notification.js`, `~/.claude/hooks/clancy-post-compact.js`, `~/.claude/hooks/clancy-statusline.js`
+
+Also remove the hooks `package.json` if it exists (`.claude/hooks/package.json` or `~/.claude/hooks/package.json`) — this was written by the installer for CJS compatibility.
+
+Then remove the Clancy hook registrations from the corresponding `settings.json` (`.claude/settings.json` for local, `~/.claude/settings.json` for global):
+
+- Remove any entry in `hooks.SessionStart` whose `command` contains `clancy-check-update`
+- Remove any entry in `hooks.PreToolUse` whose `command` contains `clancy-credential-guard`
+- Remove any entry in `hooks.PreToolUse` whose `command` contains `clancy-branch-guard`
+- Remove any entry in `hooks.PostToolUse` whose `command` contains `clancy-context-monitor`
+- Remove any entry in `hooks.PostToolUse` whose `command` contains `clancy-drift-detector`
+- Remove any entry in `hooks.PostCompact` whose `command` contains `clancy-post-compact`
+- Remove any entry in `hooks.Notification` whose `command` contains `clancy-notification`
+- Remove the `statusLine` key if its `command` value contains `clancy-statusline`
+- If removing an entry leaves any `hooks.*` array empty, remove the key entirely
+
+Also remove the update check cache if it exists: `~/.claude/cache/clancy-update-check.json`
+
+If `settings.json` does not exist or cannot be parsed, skip silently — do not create or overwrite it.
+
+---
+
+## Step 3 — Clean up CLAUDE.md
+
+Check whether `CLAUDE.md` exists in the current project directory.
+
+If it does, check for Clancy markers (`<!-- clancy:start -->` and `<!-- clancy:end -->`):
+
+**If markers found:**
+
+Read the full file content. Determine whether Clancy created the file or appended to an existing one:
+
+- **Clancy created it** (the file contains only whitespace outside the markers — no meaningful content before `<!-- clancy:start -->` or after `<!-- clancy:end -->`): delete the entire file.
+- **Clancy appended to an existing file** (there is meaningful content outside the markers): remove everything from `<!-- clancy:start -->` through `<!-- clancy:end -->` (inclusive), plus any blank lines immediately before the start marker that were added as spacing. Write the cleaned file back.
+
+Print `✅ CLAUDE.md cleaned up.` (or `✅ CLAUDE.md removed.` if deleted).
+
+**If no markers found:** skip — Clancy didn't modify this file.
+
+**If CLAUDE.md does not exist:** skip.
+
+---
+
+## Step 4 — Clean up .gitignore
+
+Check whether `.gitignore` exists in the current project directory.
+
+If it does, check whether it contains the Clancy entries (`# Clancy credentials` and/or `.clancy/.env`):
+
+**If found:** remove the `# Clancy credentials` comment line and the `.clancy/.env` line. Also remove any blank line immediately before or after the removed block to avoid leaving double blank lines. Write the cleaned file back.
+
+If the file is now empty (or contains only whitespace) after removal, delete it entirely — Clancy created it during init.
+
+Print `✅ .gitignore cleaned up.` (or `✅ .gitignore removed.` if deleted).
+
+**If not found:** skip — Clancy didn't modify this file.
+
+**If .gitignore does not exist:** skip.
+
+---
+
+## Step 5 — Clean up .prettierignore
+
+Check whether `.prettierignore` exists in the current project directory.
+
+If it does, check whether it contains Clancy entries (`# Clancy generated files` and/or `.clancy/` and/or `.claude/commands/clancy/`):
+
+**If found:** remove the `# Clancy generated files` comment line, the `.clancy/` line, and the `.claude/commands/clancy/` line. Also remove any blank line immediately before or after the removed block to avoid leaving double blank lines. Write the cleaned file back.
+
+If the file is now empty (or contains only whitespace) after removal, delete it entirely — Clancy added those entries during init.
+
+Print `✅ .prettierignore cleaned up.` (or `✅ .prettierignore removed.` if deleted).
+
+**If not found:** skip — Clancy didn't modify this file.
+
+**If .prettierignore does not exist:** skip.
+
+---
+
+## Step 6 — Offer to remove .clancy/ (if present)
+
+Check whether `.clancy/` exists in the current project directory.
+
+If it does, ask separately:
+
+```
+.clancy/ contains your codebase docs, progress log, and credentials (.env).
+Remove it too? This cannot be undone. (yes / no)
+```
+
+- `no` → print "✅ .clancy/ kept — your docs and progress log are safe."
+- `yes` → delete `.clancy/` and print "✅ .clancy/ removed."
+
+If `.clancy/` does not exist, skip this step entirely.
+
+---
+
+## Step 7 — Final message
+
+```
+✅ Clancy uninstalled.
+
+"You have the right to remain silent... goodbye, Clancy." — To reinstall: npx chief-clancy
+```
+
+---
+
+## Hard constraints
+
+- **Never touch any `.env` at the project root** — Clancy's credentials live in `.clancy/.env` and are only removed as part of `.clancy/` in Step 6
+- Steps 1–2 (commands removal), Steps 3–5 (CLAUDE.md, .gitignore, and .prettierignore cleanup), and Step 6 (`.clancy/` removal) are always asked separately — never bundle them into one confirmation
+- If the user says no to commands removal in Step 2, skip all remaining steps and stop

package/src/roles/setup/workflows/update-docs.md

@@ -0,0 +1,95 @@
+# Clancy Update-Docs Workflow
+
+## Overview
+
+Incrementally refresh `.clancy/docs/` by re-running only the agents covering areas that have changed. Faster than a full `map-codebase` when changes are targeted.
+
+---
+
+## Step 0 — Preflight
+
+Check `.clancy/` exists and `.clancy/.env` is present.
+
+If either is missing:
+
+```
+.clancy/ not found. Run /clancy:init to set up Clancy first.
+```
+
+Stop.
+
+---
+
+## Step 1 — Determine what changed
+
+Ask: "What changed since your last codebase scan? (or press Enter to auto-detect via git diff)"
+
+If the user describes changes, parse their description to identify affected areas.
+
+If Enter is pressed, run:
+
+```bash
+git diff --name-only HEAD~10 HEAD 2>/dev/null || git diff --name-only
+```
+
+---
+
+## Step 2 — Map changes to agents
+
+| Changed files / areas                                 | Re-run agent |
+| ----------------------------------------------------- | ------------ |
+| `package.json`, `*.lock`, deps, build config, env     | tech         |
+| `src/` structure, API routes, data models, services   | arch         |
+| test files, lint config, `.eslintrc`, `jest.config.*` | quality      |
+| CSS, tokens, Figma, component library, a11y           | design       |
+| Security, performance, infra, known issues            | concerns     |
+
+Multiple agents may need to re-run — run them in parallel.
+
+If `PLAYWRIGHT_ENABLED=true` and the tech agent is re-running: verify `PLAYWRIGHT.md` ports/commands still match what `STACK.md` now says. Update `PLAYWRIGHT.md` if they differ.
+
+---
+
+## Step 3 — Confirm before running
+
+```
+🚨 Clancy — Update Docs
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Based on your changes, I'll re-run:
+  - {agent list}
+
+This will update:
+  - {file list}
+
+Continue? [Y/n]:
+```
+
+---
+
+## Step 4 — Re-run selected agents in parallel
+
+Same as map-codebase Step 3, but only for the selected agents.
+
+---
+
+## Step 5 — Verify and commit
+
+Verify each updated file is non-empty.
+
+```bash
+git add .clancy/docs/
+git commit -m "docs(clancy): update-docs — refresh .clancy/docs/"
+```
+
+---
+
+## Step 6 — Final message
+
+```
+✅ Docs updated — {N} files refreshed.
+
+Updated: {file list}
+
+"Case files updated." — Run /clancy:implement or /clancy:autopilot when ready.
+```

package/src/roles/setup/workflows/update.md

@@ -0,0 +1,287 @@
+# Clancy Update Workflow
+
+## Overview
+
+Check for Clancy updates via npm, display changelog for versions between installed and latest, obtain user confirmation, and execute clean installation.
+
+---
+
+## Step 1 — Detect installed version
+
+Determine whether Clancy is installed locally or globally by checking both locations:
+
+```bash
+LOCAL_VERSION_FILE="./.claude/commands/clancy/VERSION"
+GLOBAL_VERSION_FILE="$HOME/.claude/commands/clancy/VERSION"
+
+if [ -f "$LOCAL_VERSION_FILE" ] && grep -Eq '^[0-9]+\.[0-9]+\.[0-9]+' "$LOCAL_VERSION_FILE"; then
+  INSTALLED=$(cat "$LOCAL_VERSION_FILE")
+  INSTALL_TYPE="LOCAL"
+elif [ -f "$GLOBAL_VERSION_FILE" ] && grep -Eq '^[0-9]+\.[0-9]+\.[0-9]+' "$GLOBAL_VERSION_FILE"; then
+  INSTALLED=$(cat "$GLOBAL_VERSION_FILE")
+  INSTALL_TYPE="GLOBAL"
+else
+  INSTALLED="unknown"
+  INSTALL_TYPE="UNKNOWN"
+fi
+
+echo "$INSTALLED"
+echo "$INSTALL_TYPE"
+```
+
+Parse output:
+
+- First line = installed version (or "unknown")
+- Second line = install type (LOCAL, GLOBAL, or UNKNOWN)
+
+**If version is unknown:**
+
+```
+## Clancy Update
+
+**Installed version:** Unknown
+
+Your installation doesn't include version tracking.
+
+Running fresh install...
+```
+
+Proceed to Step 4 (treat as version 0.0.0 for comparison).
+
+---
+
+## Step 2 — Check latest version
+
+Check npm for the latest published version:
+
+```bash
+npm view chief-clancy version 2>/dev/null
+```
+
+**If npm check fails:**
+
+```
+Couldn't check for updates (offline or npm unavailable).
+
+To update manually: `npx chief-clancy@latest`
+```
+
+Exit.
+
+---
+
+## Step 3 — Compare versions and confirm
+
+Compare installed vs latest:
+
+**If installed == latest:**
+
+```
+🚨 Clancy — Update
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Installed:** X.Y.Z
+**Latest:** X.Y.Z
+
+✅ You're already on the latest version. "Nothing to see here, folks."
+```
+
+Exit.
+
+**If update available**, fetch the changelog from GitHub and show what's new BEFORE updating:
+
+```bash
+curl -s https://raw.githubusercontent.com/Pushedskydiver/chief-clancy/main/CHANGELOG.md
+```
+
+The CHANGELOG uses `## [X.Y.Z]` headings. Extract all content from the `## [{latest}]` heading down to (but not including) the `## [{installed}]` heading.
+
+If the changelog fetch fails (network error, non-200), skip the "What's New" section and show: `Could not fetch changelog. View changes at github.com/Pushedskydiver/chief-clancy/blob/main/CHANGELOG.md`
+
+Display:
+
+```
+🚨 Clancy — Update
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Installed:** {installed}
+**Latest:** {latest}
+
+### What's New
+────────────────────────────────────────────────────────────
+
+{relevant CHANGELOG entries between installed and latest}
+
+────────────────────────────────────────────────────────────
+
+⚠️  **Note:** The update performs a clean install of Clancy command folders:
+- `.claude/commands/clancy/` will be replaced
+- `.claude/clancy/workflows/` will be replaced
+
+If you've modified any Clancy files directly, they'll be automatically backed up
+to `.claude/clancy/local-patches/` before overwriting.
+
+Your project files are preserved:
+- `.clancy/docs/`, `.clancy/.env`, `.clancy/progress.txt` ✅
+- `CLAUDE.md` ✅
+- Custom commands not in `commands/clancy/` ✅
+- Custom hooks ✅
+
+Note: `.clancy/clancy-implement.js` and `.clancy/clancy-autopilot.js` **will be replaced** with
+the latest bundled versions. The rest of `.clancy/` is untouched.
+```
+
+**AFK mode check:** If `--afk` flag is passed OR `CLANCY_MODE=afk` in `.clancy/.env`, **skip the confirmation and proceed automatically.** Do not prompt — auto-approve the update.
+
+**Interactive mode:** Ask the user: **"Proceed with update?"** with options:
+
+- "Yes, update now"
+- "No, cancel"
+
+**If user cancels:** Exit.
+
+---
+
+## Step 4 — Run the update
+
+Run the installer using the detected install type from Step 1. Pass `--global` or `--local` so the installer runs non-interactively (no prompts):
+
+- If `INSTALL_TYPE` is `LOCAL`: `npx -y chief-clancy@latest --local`
+- If `INSTALL_TYPE` is `GLOBAL`: `npx -y chief-clancy@latest --global`
+- If `INSTALL_TYPE` is `UNKNOWN`: `npx -y chief-clancy@latest` (falls back to interactive mode)
+
+```bash
+# Example for local install:
+npx -y chief-clancy@latest --local
+
+# Example for global install:
+npx -y chief-clancy@latest --global
+```
+
+The `--global`/`--local` flags skip the interactive install-type prompt and auto-accept the overwrite confirmation.
+
+This touches:
+
+- `.claude/commands/clancy/` — slash commands (replaced)
+- `.claude/clancy/workflows/` — workflow files (replaced)
+- `.clancy/clancy-implement.js` and `.clancy/clancy-autopilot.js` — bundled runtime scripts (replaced)
+
+It never modifies:
+
+- `.clancy/docs/` — codebase documentation
+- `.clancy/progress.txt` — progress log
+- `CLAUDE.md`
+
+It may **append** to:
+
+- `.clancy/.env` — adds missing env var defaults (see Step 4a)
+
+---
+
+## Step 4a — Backfill missing env var defaults
+
+After the installer finishes, read `.clancy/.env` and check for missing pipeline label variables. These were introduced in v0.7.4 and won't exist in `.env` files from earlier installs.
+
+**Check for and append if missing:**
+
+```
+# Pipeline labels (added in v0.7.4)
+CLANCY_LABEL_BRIEF=clancy:brief
+CLANCY_LABEL_PLAN=clancy:plan
+CLANCY_LABEL_BUILD=clancy:build
+```
+
+For each variable:
+
+1. Read `.clancy/.env` content
+2. If the variable name does NOT appear anywhere in the file (not even commented out), append it with its default value
+3. If the variable already exists (even with a different value), leave it untouched
+
+Add a blank line and a `# Pipeline labels (added in v0.7.4)` comment header before the new variables, but only if at least one variable was added.
+
+**Display what was added (if any):**
+
+```
+📋 Added missing env var defaults to .clancy/.env:
+   CLANCY_LABEL_BRIEF=clancy:brief
+   CLANCY_LABEL_PLAN=clancy:plan
+   CLANCY_LABEL_BUILD=clancy:build
+
+   Customise these via /clancy:settings → L1/L2/L3
+```
+
+If nothing was added, display nothing.
+
+---
+
+## Step 5 — Check for local patches
+
+After the update completes, check if the installer backed up any locally modified files:
+
+Check for `.claude/clancy/local-patches/backup-meta.json` (local install) or `~/.claude/clancy/local-patches/backup-meta.json` (global install).
+
+**If patches were found:**
+
+```
+Local patches were backed up before the update.
+Your modified files are in .claude/clancy/local-patches/
+
+To review what changed:
+  Compare each file in local-patches/ against its counterpart in
+  .claude/commands/clancy/ or .claude/clancy/workflows/ and manually
+  reapply any customisations you want to keep.
+
+Backed up files:
+{list from backup-meta.json}
+```
+
+**If no patches:** Continue normally (no message needed).
+
+---
+
+## Step 6 — Clear update cache and confirm
+
+Clear the update check cache so the statusline indicator disappears:
+
+```bash
+rm -f "$HOME/.claude/cache/clancy-update-check.json"
+rm -f "./.claude/cache/clancy-update-check.json"
+```
+
+Display completion message:
+
+```
+╔═══════════════════════════════════════════════════════════╗
+║  ✅ Clancy Updated: v{old} → v{new}                     ║
+╚═══════════════════════════════════════════════════════════╝
+
+"New badge, same Chief." — Start a new Claude Code session to pick up the updated commands.
+
+View full changelog: github.com/Pushedskydiver/chief-clancy/blob/main/CHANGELOG.md
+```
+
+### New role hints
+
+After the completion message, check `.clancy/.env` for `CLANCY_ROLES` and display hints for any optional roles that are available but not enabled:
+
+- If `CLANCY_ROLES` does not include `planner`:
+  ```
+  💡 Planner role available — refine vague tickets into structured plans.
+     Run /clancy:settings to enable it.
+  ```
+- If `CLANCY_ROLES` does not include `strategist`:
+  ```
+  💡 Strategist role available — generate briefs, grill requirements, create tickets.
+     Run /clancy:settings to enable it.
+  ```
+- If `CLANCY_ROLES` is not set at all (env var missing), show both hints.
+- If all optional roles are already enabled, show nothing.
+
+---
+
+## Notes
+
+- If the user installed globally, the update applies globally
+- If the user installed locally, the update applies locally
+- After updating, restart Claude Code for new commands to take effect
+- New role hints are shown post-update so existing users discover features added in newer versions

package/src/roles/strategist/commands/approve-brief.md

@@ -0,0 +1,23 @@
+# /clancy:approve-brief
+
+Convert an approved brief into real tickets on the board. Creates child tickets under the parent, links dependencies, and posts a tracking summary.
+
+Accepts optional arguments:
+
+- **By slug:** `/clancy:approve-brief auth-rework` — approve a specific brief
+- **By index:** `/clancy:approve-brief 2` — approve the 2nd unapproved brief
+- **By ticket:** `/clancy:approve-brief PROJ-123` — approve brief sourced from this ticket
+- **Set parent:** `--epic PROJ-50` — override or set the parent epic
+- **Preview:** `--dry-run` — show what would be created without making API calls
+- **Skip confirmation:** `--afk` — auto-confirm without prompting (for automation)
+
+Examples:
+
+- `/clancy:approve-brief` — auto-select (if only 1 unapproved brief)
+- `/clancy:approve-brief auth-rework` — approve by slug
+- `/clancy:approve-brief --dry-run` — preview ticket creation
+- `/clancy:approve-brief --epic PROJ-50` — set parent and approve
+
+@.claude/clancy/workflows/approve-brief.md
+
+Follow the approve-brief workflow above. Parse the decomposition, create tickets on the board, link dependencies, and post a tracking comment.

package/src/roles/strategist/commands/brief.md

@@ -0,0 +1,29 @@
+# /clancy:brief
+
+Generate a strategic brief for a feature idea. Researches the codebase, grills you (or itself) on requirements, and produces a decomposition into actionable tickets.
+
+Accepts optional arguments:
+
+- **Board ticket:** `/clancy:brief PROJ-123`, `/clancy:brief #42`, `/clancy:brief ENG-42` — brief from a board ticket
+- **Inline text:** `/clancy:brief "Add dark mode"` — brief from a description
+- **From file:** `/clancy:brief --from docs/rfc.md` — brief from a local file
+- **Batch mode:** `/clancy:brief 3` — brief up to 3 tickets from the queue
+- **Fresh start:** `--fresh` — discard existing brief and start over
+- **Force web research:** `--research` — include web research in analysis
+- **AFK mode:** `--afk` — use AI-grill instead of human grill
+- **Epic hint:** `--epic PROJ-50 "Add dark mode"` — set parent for approve step
+- **List briefs:** `--list` — show inventory of existing briefs
+
+Examples:
+
+- `/clancy:brief` — interactive mode (prompt for idea)
+- `/clancy:brief PROJ-200` — brief a Jira ticket
+- `/clancy:brief #42` — brief a GitHub issue
+- `/clancy:brief ENG-42` — brief a Linear issue
+- `/clancy:brief "Add dark mode support"` — brief from inline text
+- `/clancy:brief --afk PROJ-200` — brief with AI-grill (no human questions)
+- `/clancy:brief --list` — show all briefs
+
+@.claude/clancy/workflows/brief.md
+
+Follow the brief workflow above. Research the codebase, conduct the grill phase, generate the brief, and save it locally. Do not create tickets — briefing only.