chief-clancy 0.7.1 → 0.7.2

package/README.md

@@ -143,6 +143,9 @@ npx chief-clancy
 
 # 6. Go AFK
 /clancy:run
+
+# Fully autonomous (no prompts at any step):
+# /clancy:brief --afk #42 → /clancy:approve-brief --afk → /clancy:run
 ```
 
 ---

package/package.json

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

package/src/roles/planner/commands/approve-plan.md

@@ -2,6 +2,9 @@
 
 Promote an approved Clancy plan to the ticket description. Accepts an optional ticket key argument (e.g. `/clancy:approve-plan PROJ-123`). When no key is provided, auto-selects the oldest planned-but-unapproved ticket.
 
+Optional flags:
+- **Skip confirmation:** `--afk` — auto-confirm without prompting (for automation)
+
 @.claude/clancy/workflows/approve-plan.md
 
 Follow the approve-plan workflow above. Fetch the plan comment, confirm with the user, append it to the ticket description, and transition the ticket to the implementation queue.

package/src/roles/planner/commands/plan.md

@@ -6,6 +6,7 @@ Accepts optional arguments:
 - **Batch mode:** `/clancy:plan 3` — plan up to 3 tickets from the queue
 - **Specific ticket:** `/clancy:plan PROJ-123`, `/clancy:plan #42`, `/clancy:plan ENG-42` — plan a single ticket by key
 - **Fresh start:** `--fresh` — discard any existing plan and start over
+- **Skip confirmations:** `--afk` — auto-confirm all prompts (for automation)
 
 Examples:
 - `/clancy:plan` — plan 1 ticket from queue

package/src/roles/planner/workflows/approve-plan.md

@@ -154,6 +154,8 @@ If the user picks [2], stop: `Cancelled. No changes made.`
 
 **If the user already confirmed via auto-select in Step 2, SKIP this step entirely** (avoid double-confirmation).
 
+**AFK mode:** If running in AFK mode (`--afk` flag or `CLANCY_MODE=afk`), skip the confirmation prompt and auto-confirm. Display the summary for logging purposes but proceed without waiting for input.
+
 Display a summary and ask for confirmation:
 
 ```
@@ -166,7 +168,7 @@ Planned: {date from plan}
 Promote this plan to the ticket description? [Y/n]
 ```
 
-If the user declines, stop:
+If the user declines (interactive only), stop:
 ```
 Cancelled. No changes made.
 ```

package/src/roles/planner/workflows/plan.md

@@ -66,7 +66,7 @@ Parse the arguments passed to the command:
 
 If N > 10: `Maximum batch size is 10. Planning 10 tickets.`
 
-If N >= 5: display a confirmation:
+If N >= 5: display a confirmation (skip in AFK mode — `--afk` flag or `CLANCY_MODE=afk`):
 ```
 Planning {N} tickets — each requires codebase exploration. Continue? [Y/n]
 ```
@@ -92,7 +92,7 @@ RESPONSE=$(curl -s \
 
 Validate the response:
 - If `pull_request` field is present (not null): `#{N} is a PR, not an issue.` Stop.
-- If `state` is `closed`: warn `Issue #${N} is closed. Plan anyway? [y/N]`
+- If `state` is `closed`: warn `Issue #${N} is closed. Plan anyway? [y/N]` (in AFK mode: skip this ticket — do not plan closed issues unattended)
 
 #### Jira — Fetch specific ticket
 
@@ -104,7 +104,7 @@ RESPONSE=$(curl -s \
 ```
 
 Validate the response:
-- If `fields.status.statusCategory.key` is `done`: warn `Ticket is done. Plan anyway? [y/N]`
+- If `fields.status.statusCategory.key` is `done`: warn `Ticket is done. Plan anyway? [y/N]` (in AFK mode: skip this ticket)
 - If `fields.issuetype.name` is `Epic`: note `This is an epic.` (continue normally)
 
 #### Linear — Fetch specific issue
@@ -124,8 +124,8 @@ query {
 
 Validate the response:
 - If `nodes` is empty: `Issue {KEY} not found on Linear.` Stop.
-- If `state.type` is `completed`: warn `Issue is completed. Plan anyway? [y/N]`
-- If `state.type` is `canceled`: warn `Issue is canceled. Plan anyway? [y/N]`
+- If `state.type` is `completed`: warn `Issue is completed. Plan anyway? [y/N]` (in AFK mode: skip this ticket)
+- If `state.type` is `canceled`: warn `Issue is canceled. Plan anyway? [y/N]` (in AFK mode: skip this ticket)
 
 Then skip to Step 3b with this single ticket.
 

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

@@ -8,6 +8,7 @@ Accepts optional arguments:
 - **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)

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

@@ -130,7 +130,9 @@ AFK-ready: {X} | Needs human: {Y}
 Create {N} tickets? [Y/n]
 ```
 
-If user declines: `Cancelled. No changes made.` Stop.
+**AFK mode:** If running in AFK mode (`--afk` flag OR `CLANCY_MODE=afk`), skip the confirmation prompt and auto-confirm. Display the ticket list for logging purposes but proceed without waiting for input.
+
+If user declines (interactive only): `Cancelled. No changes made.` Stop.
 
 ---
 

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

@@ -50,7 +50,9 @@ Parse the arguments passed to the command. Arguments can appear in any order.
 
 ### Input modes
 
-- **No input (no flags that consume arguments):** Interactive mode — prompt `What's the idea?` and parse the response. If the response looks like a ticket reference (`#42`, `PROJ-123`, `ENG-42`), switch to board ticket mode. Otherwise treat as inline text.
+- **No input (no flags that consume arguments):** Interactive mode — but first check for `--afk`:
+  - If running in AFK mode (`--afk` flag OR `CLANCY_MODE=afk`): there is no human to answer. Display: `✗ Cannot run /clancy:brief in AFK mode without a ticket or idea. Use: /clancy:brief --afk #42 (GitHub) or PROJ-123 (Jira) or ENG-42 (Linear), or /clancy:brief --afk "Add dark mode", or /clancy:brief 3 (batch mode — implies --afk).` Stop.
+  - Otherwise: prompt `What's the idea?` and parse the response. If the response looks like a ticket reference (`#42`, `PROJ-123`, `ENG-42`), switch to board ticket mode. Otherwise treat as inline text.
 - **Ticket key** (`PROJ-123`, `#42`, `ENG-42`): Board ticket mode — fetch the ticket from the board API. Validate format per platform:
   - `#N` — valid for GitHub only. If board is Jira or Linear: `The #N format is for GitHub Issues. Use a ticket key like PROJ-123.` Stop.
   - `PROJ-123` / `ENG-42` (letters-dash-number) — valid for Jira and Linear. If board is GitHub: `Use #N format for GitHub Issues (e.g. #42).` Stop.
@@ -355,7 +357,7 @@ Scan `.clancy/briefs/` for an existing brief matching this idea:
 
 1. **Local brief file** — check for `## Feedback` section appended to `.clancy/briefs/{date}-{slug}.md`
 2. **Companion file** — check for `.clancy/briefs/{date}-{slug}.feedback.md`
-3. **Board comments** (board-sourced only) — find the most recent `Clancy Strategic Brief` comment on the source ticket. Collect all comments posted AFTER it.
+3. **Board comments** (board-sourced only) — fetch ALL comments on the source ticket. Scan each comment body for the text `Clancy Strategic Brief` (case-insensitive, match anywhere in the body — it may appear as `# Clancy Strategic Brief`, `## Clancy Strategic Brief`, or just the text). The most recent matching comment is the brief. Collect all comments posted AFTER it as feedback.
 
 Board comment feedback filtering per platform:
 - **GitHub:** comments where `created_at` > brief comment's `created_at` AND `user.login` != resolved username (via `GET /user`)
@@ -490,7 +492,7 @@ Using all gathered context (idea, grill output, research findings), generate the
 - {Specific risk and mitigation strategy}
 
 ---
-*Generated by [Clancy](https://github.com/Pushedskydiver/clancy). To request changes: comment on the source ticket or add a ## Feedback section to the brief file, then re-run `/clancy:brief` to revise. To approve: `/clancy:approve-brief`. To start over: `/clancy:brief --fresh`.*
+*Generated by [Clancy](https://github.com/Pushedskydiver/clancy). To answer open questions or request changes: comment on the source ticket or add a ## Feedback section to the brief file, then re-run `/clancy:brief` to revise. To approve: `/clancy:approve-brief`. To start over: `/clancy:brief --fresh`.*
 ```
 
 ### Source field format
@@ -518,11 +520,18 @@ Using all gathered context (idea, grill output, research findings), generate the
 
 ### Re-brief revision
 
-If revising from feedback (Step 5), prepend a section before Problem Statement:
+If revising from feedback (Step 5):
+
+1. **Cross-reference feedback against Open Questions.** For each Open Question in the existing brief, check if the feedback contains an answer (exact or paraphrased — match by intent, not syntax). Resolved questions move to `## Discovery` with `(Source: human)` tag. Unresolved questions stay in `## Open Questions`.
+
+2. **Apply all other feedback** — changes to scope, goals, decomposition, user stories, etc.
+
+3. **Prepend a section** before Problem Statement:
 
 ```markdown
 ### Changes From Previous Brief
-{What feedback was addressed and how the brief changed}
+{What feedback was addressed and how the brief changed.
+ List resolved open questions explicitly.}
 ```
 
 ---
@@ -657,27 +666,36 @@ Print the full brief to stdout, followed by the sign-off:
 ### Next steps (board-sourced)
 
 ```
-Next steps:
-  To request changes:
-    • Comment on {KEY} on your board, then re-run /clancy:brief {KEY} to revise
-    • Or add a ## Feedback section to the brief file and re-run
-  To approve: /clancy:approve-brief {KEY}
-  To start over: /clancy:brief --fresh {KEY}
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Next Steps
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+  Answer open questions or request changes:
+    • Comment on {KEY} on your board
+    • Or add a ## Feedback section to the brief file
+    Then re-run: /clancy:brief {KEY}
+
+  Approve:       /clancy:approve-brief {KEY}
+  Start over:    /clancy:brief --fresh {KEY}
 ```
 
 ### Next steps (inline text / from file)
 
 ```
-Next steps:
-  To request changes:
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Next Steps
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+  Answer open questions or request changes:
     • Add a ## Feedback section to:
-      .clancy/briefs/{date}-{slug}.md
+        .clancy/briefs/{date}-{slug}.md
     • Or create a companion file:
-      .clancy/briefs/{date}-{slug}.feedback.md
-    Then re-run /clancy:brief to revise.
-  To approve: /clancy:approve-brief {slug}
-  To attach to a parent: /clancy:approve-brief {slug} --epic {KEY}
-  To start over: /clancy:brief --fresh
+        .clancy/briefs/{date}-{slug}.feedback.md
+    Then re-run: /clancy:brief
+
+  Approve:       /clancy:approve-brief {slug}
+  With parent:   /clancy:approve-brief {slug} --epic {KEY}
+  Start over:    /clancy:brief --fresh
 ```
 
 ---
@@ -726,7 +744,7 @@ Briefs saved to .clancy/briefs/. Run /clancy:approve-brief to create tickets.
 - The `--list` flag is an inventory display only — no brief generated, no API calls beyond the local filesystem.
 - Batch mode (`/clancy:brief 3`) implies AI-grill — each ticket is briefed autonomously.
 - All board API calls are best-effort — if a comment fails to post, print the brief and warn. The local file is the source of truth.
-- The `## Clancy Strategic Brief` marker in comments is used by both `/clancy:brief` (to detect existing briefs) and `/clancy:approve-brief` (to find the brief).
+- The `Clancy Strategic Brief` text in comments is the marker used by both `/clancy:brief` (to detect existing briefs and feedback) and `/clancy:approve-brief` (to find the brief). Search case-insensitively and match regardless of heading level (`#`, `##`, or plain text).
 - Jira uses ADF for comments (with `codeBlock` fallback). GitHub and Linear accept Markdown directly.
 - Linear personal API keys do NOT use `Bearer` prefix.
 - Jira uses the new `POST /rest/api/3/search/jql` endpoint (old GET `/search` removed Aug 2025).