chief-clancy 0.5.0 → 0.5.1

package/README.md

@@ -168,7 +168,30 @@ npx chief-clancy
 | `/clancy:uninstall`    | Remove Clancy commands — optionally remove `.clancy/` too               |
 | `/clancy:help`         | Command reference                                                        |
 
-¹ Planner is an optional role. Enable with `CLANCY_ROLES=planner` in `.clancy/.env` and re-run the installer.
+¹ Planner is an optional role — see [Roles](#roles) below.
+
+---
+
+## Roles
+
+Clancy organises its commands into **roles** — each role handles a different stage of the development workflow.
+
+| Role | Purpose | Commands |
+| --- | --- | --- |
+| **Implementer** | Plan → code. Picks up tickets, implements, commits, merges | `/clancy:once`, `/clancy:run`, `/clancy:dry-run` |
+| **Reviewer** | Score ticket readiness and track progress | `/clancy:review`, `/clancy:status`, `/clancy:logs` |
+| **Setup** | Configure and maintain Clancy | `/clancy:init`, `/clancy:settings`, `/clancy:doctor`, etc. |
+| **Planner** *(optional)* | Refine backlog tickets into structured implementation plans | `/clancy:plan`, `/clancy:approve` |
+
+**Core roles** (Implementer, Reviewer, Setup) are always installed. **Optional roles** (Planner) are opt-in — add them to `CLANCY_ROLES` in `.clancy/.env` and re-run the installer:
+
+```bash
+# Enable the Planner role
+echo 'CLANCY_ROLES="planner"' >> .clancy/.env
+npx chief-clancy@latest --local   # or --global
+```
+
+You can also toggle roles from within Claude Code using `/clancy:settings`.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chief-clancy",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "Autonomous, board-driven development for Claude Code — scaffolds docs, integrates Kanban boards, runs tickets in a loop.",
   "keywords": [
     "claude",

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

@@ -22,9 +22,9 @@ Before asking any questions, silently check:
 - Is this an existing project? Check for `package.json`, `.git`, `src/`, `app/`, `lib/`
 - Is a board already configured? Check `.clancy/.env` for `JIRA_BASE_URL`, `GITHUB_TOKEN`, `LINEAR_API_KEY`
 - Does `CLAUDE.md` already exist? Flag for merge — never overwrite
-- Does `.clancy/` already exist? Warn and offer re-init or abort
+- Does `.clancy/.env` already exist? This means init has been completed before — warn and offer re-init or abort. Note: `.clancy/` alone may exist from the installer (runtime scripts) without init having run.
 
-If `.clancy/` exists, output:
+If `.clancy/.env` exists, output:
 
 It looks like Clancy is already set up in this project.