chief-clancy 0.9.23 → 0.9.25

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +14 -4
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Clancy
2
2
 
3
- **Autonomous, board-driven development for Claude Code.**
3
+ **Autonomous development for Claude Code — driven by your Kanban board, or by local plan files.**
4
4
 
5
5
  [![npm](https://img.shields.io/npm/v/chief-clancy?style=for-the-badge&color=cb3837)](https://www.npmjs.com/package/chief-clancy) [![License: MIT](https://img.shields.io/badge/License-MIT-blue?style=for-the-badge)](https://github.com/Pushedskydiver/chief-clancy/blob/main/LICENSE)
6
6
 
@@ -15,12 +15,22 @@ Clancy scaffolds slash commands, hooks, and board integrations into your Claude
15
15
 
16
16
  ## How it works
17
17
 
18
+ **With a board:**
19
+
18
20
  1. **Install:** `npx chief-clancy` — choose global or local install
19
- 2. **Configure:** `/clancy:init` — choose your board, enter credentials
21
+ 2. **Configure:** `/clancy:init` — connect your board, enter credentials
20
22
  3. **Scan:** `/clancy:map-codebase` — 5 parallel agents document your codebase
21
23
  4. **Run:** `/clancy:implement` — pick up one ticket, implement, create PR
22
- 5. **Or use local plans:** `/clancy:implement --from plan.md` — execute a plan file without board credentials
23
- 6. **Go AFK:** `/clancy:autopilot` — loop through your backlog unattended
24
+ 5. **Go AFK:** `/clancy:autopilot` — loop through your backlog unattended
25
+
26
+ **Without a board — local plan-driven flow:**
27
+
28
+ 1. **Install:** `npx chief-clancy`
29
+ 2. **Configure:** `/clancy:init` — answer "No" when asked about a board. When prompted for optional roles, enable **both Strategist and Planner** — the local flow uses `/clancy:brief` and `/clancy:plan`, which only install when their roles are enabled.
30
+ 3. **Scan:** `/clancy:map-codebase`
31
+ 4. **Draft:** `/clancy:brief --from outline.md` → `/clancy:plan --from <brief>` → `/clancy:approve-plan <plan>` (writes a `.approved` marker file — a write-side contract; a future PR will wire a runtime gate that re-hashes the plan and refuses to run on mismatch)
32
+ 5. **Run one plan:** `/clancy:implement --from .clancy/plans/<plan>.md`
33
+ 6. **Go AFK:** `/clancy:implement --from .clancy/plans/ --afk` — batch-executes every plan in the directory that has a sibling `.approved` marker, naturally sorted. Unapproved plans are skipped with a warning. (Marker SHA-256 verification is deferred — only marker existence is currently checked.)
24
34
 
25
35
  ## Packages
26
36
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "chief-clancy",
3
- "version": "0.9.23",
3
+ "version": "0.9.25",
4
4
  "description": "Autonomous, board-driven development for Claude Code",
5
5
  "author": "Alex Clapperton",
6
6
  "license": "MIT",
@@ -33,6 +33,6 @@
33
33
  "@chief-clancy/brief": "0.4.3",
34
34
  "@chief-clancy/plan": "0.7.1",
35
35
  "@chief-clancy/scan": "0.2.3",
36
- "@chief-clancy/terminal": "0.1.14"
36
+ "@chief-clancy/terminal": "0.2.0"
37
37
  }
38
38
  }