@chief-clancy/terminal 0.1.0

package/src/roles/setup/commands/map-codebase.md

@@ -0,0 +1,17 @@
+# /clancy:map-codebase
+
+Scan your codebase with 5 parallel specialist agents and write 10 structured docs to .clancy/docs/.
+
+Agents run simultaneously:
+
+- 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
+
+Takes approximately 2 minutes for a typical codebase.
+
+@.claude/clancy/workflows/map-codebase.md
+
+Run the 5-agent scan as documented in the workflow above. Spawn all agents simultaneously.

package/src/roles/setup/commands/settings.md

@@ -0,0 +1,7 @@
+# /clancy:settings
+
+View and change Clancy configuration without re-running init.
+
+@.claude/clancy/workflows/settings.md
+
+Run the settings workflow as documented above.

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

@@ -0,0 +1,5 @@
+# /clancy:uninstall
+
+Remove Clancy's slash commands from this project or your global Claude Code installation.
+
+@.claude/clancy/workflows/uninstall.md

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

@@ -0,0 +1,9 @@
+# /clancy:update-docs
+
+Incrementally refresh .clancy/docs/ — re-runs only the agents covering areas that have changed since the last scan.
+
+Faster than a full map-codebase when you've made targeted changes (new dependency, design system update, new test strategy, etc.).
+
+@.claude/clancy/workflows/update-docs.md
+
+Run the incremental update as documented in the workflow above.

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

@@ -0,0 +1,13 @@
+# /clancy:update
+
+Update Clancy itself to the latest version via npx and show what changed.
+
+This re-runs the installer, which copies the latest command files from the npm package into your .claude/commands/clancy/ directory. Your .clancy/ project folder (scripts, docs, progress log) is never touched.
+
+**Supported flags:**
+
+- `--afk` — skip the confirmation prompt and auto-approve the update (for autonomous setups)
+
+@.claude/clancy/workflows/update.md
+
+Run the update as documented in the workflow above. If `--afk` is passed, skip all confirmation prompts.

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

@@ -0,0 +1,131 @@
+## Update check
+
+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.
+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.
+
+---
+
+# Clancy Doctor Workflow
+
+## Overview
+
+Diagnose your Clancy setup — test every configured integration and report what's working, what's broken, and how to fix it. Never modifies any files or state.
+
+---
+
+## Step 1 — Check install
+
+- 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})`
+
+---
+
+## Step 2 — Check prerequisites
+
+Test each required binary:
+
+| Binary | Check             | Fix hint                |
+| ------ | ----------------- | ----------------------- |
+| `node` | `command -v node` | Install Node.js 24+     |
+| `git`  | `command -v git`  | Install git for your OS |
+
+Print `✅` or `❌` for each.
+
+---
+
+## Step 3 — Check project setup
+
+- `.clancy/` exists → `✅ .clancy/ found`
+- `.clancy/clancy-implement.js` exists → `✅ clancy-implement.js`
+- `.clancy/clancy-autopilot.js` exists → `✅ clancy-autopilot.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`
+
+---
+
+## Step 4 — Check board credentials
+
+Source `.clancy/.env` and detect which board is configured:
+
+**Jira** — if `JIRA_BASE_URL` is set:
+
+1. Check all required vars are non-empty: `JIRA_BASE_URL`, `JIRA_USER`, `JIRA_API_TOKEN`, `JIRA_PROJECT_KEY`
+2. Ping: `GET {JIRA_BASE_URL}/rest/api/3/project/{JIRA_PROJECT_KEY}` with basic auth
+3. Report HTTP status with specific guidance for each failure code
+
+**GitHub Issues** — if `GITHUB_TOKEN` is set:
+
+1. Check: `GITHUB_TOKEN`, `GITHUB_REPO`
+2. Ping: `GET https://api.github.com/repos/{GITHUB_REPO}` with bearer token
+3. Report status
+
+**Linear** — if `LINEAR_API_KEY` is set:
+
+1. Check: `LINEAR_API_KEY`, `LINEAR_TEAM_ID`
+2. Ping: `POST https://api.linear.app/graphql` with `{ viewer { id } }` — no Bearer prefix
+3. Report status
+
+---
+
+## Step 5 — Check optional integrations
+
+**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.`
+- Note: Figma's API does not expose plan information — check your plan at figma.com/settings
+
+**Playwright** — if `PLAYWRIGHT_ENABLED=true`:
+
+- Check `.clancy/docs/PLAYWRIGHT.md` exists
+- Verify `PLAYWRIGHT_DEV_COMMAND` and `PLAYWRIGHT_DEV_PORT` are set
+- Check port is not currently in use (just a status, not a blocker)
+
+**Notifications** — if `CLANCY_NOTIFY_WEBHOOK` is set:
+
+- Detect platform from URL (Slack/Teams)
+- Send a test ping: `"Clancy doctor — webhook test from {project dir}"`
+- Report success or failure
+
+---
+
+## Step 6 — Summary
+
+```
+🚨 Clancy — Doctor
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+{N} checks passed, {N} warnings, {N} failures
+
+✅ 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:implement to verify end-to-end.
+
+"We've got a 415 in progress — a config disturbance."
+```
+
+If all checks pass:
+
+```
+🚨 Clancy — Doctor
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+All {N} checks passed.
+
+"Nothing to see here, folks. Move along." — Run /clancy:implement to pick up your first ticket.
+```