chief-clancy 0.7.3 → 0.7.4

package/package.json

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

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

@@ -314,25 +314,29 @@ Could not update plan comment. The plan is still promoted to the description.
 
 ---
 
-## Step 6 — Post-approval transition
+## Step 6 — Post-approval label transition
 
-Transition the ticket from the planning queue to the implementation queue. This is **best-effort** — warn on failure, continue.
+Transition the ticket from the planning queue to the implementation queue via pipeline labels. This is **best-effort** — warn on failure, continue.
 
-### GitHub (always, not configurable)
+**Crash safety:** Add the new label BEFORE removing the old one. A ticket briefly has two labels (harmless) rather than zero labels (ticket lost).
 
-1. **Remove planning label:**
+Read `CLANCY_LABEL_BUILD` from `.clancy/.env` (default: `clancy:build`). Read `CLANCY_LABEL_PLAN` from `.clancy/.env` (default: `clancy:plan`, falls back to `CLANCY_PLAN_LABEL`).
+
+### GitHub
+
+1. **Add build label** (ensure it exists first):
    ```bash
+   # Ensure label exists (ignore 422 = already exists)
    curl -s \
      -H "Authorization: Bearer $GITHUB_TOKEN" \
      -H "Accept: application/vnd.github+json" \
      -H "X-GitHub-Api-Version: 2022-11-28" \
-     -X DELETE \
-     "https://api.github.com/repos/$GITHUB_REPO/issues/$ISSUE_NUMBER/labels/$CLANCY_PLAN_LABEL"
-   ```
-   `CLANCY_PLAN_LABEL` defaults to `needs-refinement`. URL-encode the label name. Ignore 404 (label not on issue). If `CLANCY_PLAN_LABEL` is not set, use the default `needs-refinement`.
+     -H "Content-Type: application/json" \
+     -X POST \
+     "https://api.github.com/repos/$GITHUB_REPO/labels" \
+     -d '{"name": "$CLANCY_LABEL_BUILD", "color": "0075ca"}'
 
-2. **Add implementation label** (only if `CLANCY_LABEL` is set — skip if unset):
-   ```bash
+   # Add to issue
    curl -s \
      -H "Authorization: Bearer $GITHUB_TOKEN" \
      -H "Accept: application/vnd.github+json" \
@@ -340,38 +344,68 @@ Transition the ticket from the planning queue to the implementation queue. This
      -H "Content-Type: application/json" \
      -X POST \
      "https://api.github.com/repos/$GITHUB_REPO/issues/$ISSUE_NUMBER/labels" \
-     -d '{"labels": ["$CLANCY_LABEL"]}'
+     -d '{"labels": ["$CLANCY_LABEL_BUILD"]}'
    ```
-   If `CLANCY_LABEL` is not set, skip this step entirely (only the plan label removal is done). `CLANCY_LABEL` has no default — it is fully optional. When set (e.g. `clancy`), use its value. If the label does not exist on the repo, attempt to create it:
+
+2. **Remove plan label:**
    ```bash
    curl -s \
      -H "Authorization: Bearer $GITHUB_TOKEN" \
      -H "Accept: application/vnd.github+json" \
+     -H "X-GitHub-Api-Version: 2022-11-28" \
+     -X DELETE \
+     "https://api.github.com/repos/$GITHUB_REPO/issues/$ISSUE_NUMBER/labels/$(echo $CLANCY_LABEL_PLAN | jq -Rr @uri)"
+   ```
+   Ignore 404 (label not on issue).
+
+### Jira
+
+1. **Add build label** (Jira auto-creates labels):
+   ```bash
+   # Fetch current labels
+   CURRENT_LABELS=$(curl -s \
+     -u "$JIRA_USER:$JIRA_API_TOKEN" \
+     -H "Accept: application/json" \
+     "$JIRA_BASE_URL/rest/api/3/issue/$TICKET_KEY?fields=labels" | jq -r '.fields.labels')
+
+   # Add build label
+   UPDATED_LABELS=$(echo "$CURRENT_LABELS" | jq --arg build "$CLANCY_LABEL_BUILD" '. + [$build] | unique')
+
+   curl -s \
+     -u "$JIRA_USER:$JIRA_API_TOKEN" \
+     -X PUT \
      -H "Content-Type: application/json" \
-     -X POST \
-     "https://api.github.com/repos/$GITHUB_REPO/labels" \
-     -d '{"name": "$CLANCY_LABEL", "color": "0075ca"}'
+     "$JIRA_BASE_URL/rest/api/3/issue/$TICKET_KEY" \
+     -d "{\"fields\": {\"labels\": $UPDATED_LABELS}}"
    ```
-   If 403 (no admin access) or 422 (invalid name): warn, continue without label.
 
-### Jira (only if `CLANCY_STATUS_PLANNED` is set)
+2. **Remove plan label:**
+   ```bash
+   # Re-fetch labels (may have changed), remove plan label
+   CURRENT_LABELS=$(curl -s \
+     -u "$JIRA_USER:$JIRA_API_TOKEN" \
+     -H "Accept: application/json" \
+     "$JIRA_BASE_URL/rest/api/3/issue/$TICKET_KEY?fields=labels" | jq -r '.fields.labels')
 
-If `CLANCY_STATUS_PLANNED` is not set: skip transition, no warning needed.
+   UPDATED_LABELS=$(echo "$CURRENT_LABELS" | jq --arg plan "$CLANCY_LABEL_PLAN" '[.[] | select(. != $plan)]')
 
-If `CLANCY_STATUS_PLANNED` is set:
+   curl -s \
+     -u "$JIRA_USER:$JIRA_API_TOKEN" \
+     -X PUT \
+     -H "Content-Type: application/json" \
+     "$JIRA_BASE_URL/rest/api/3/issue/$TICKET_KEY" \
+     -d "{\"fields\": {\"labels\": $UPDATED_LABELS}}"
+   ```
 
-1. **Fetch transitions:**
+3. **Status transition** (only if `CLANCY_STATUS_PLANNED` is set — skip if unset):
    ```bash
+   # Fetch transitions
    curl -s \
      -u "$JIRA_USER:$JIRA_API_TOKEN" \
      -H "Accept: application/json" \
      "$JIRA_BASE_URL/rest/api/3/issue/$TICKET_KEY/transitions"
-   ```
 
-2. **Find matching transition:** Look for a transition where `.name` matches `CLANCY_STATUS_PLANNED` (case-insensitive). This matches the pattern used in the runtime Jira module.
-
-3. **Execute transition:**
-   ```bash
+   # Find matching transition and execute
    curl -s \
      -u "$JIRA_USER:$JIRA_API_TOKEN" \
      -X POST \
@@ -385,23 +419,50 @@ On failure:
 Could not transition ticket. Move it manually to your implementation queue.
 ```
 
-### Linear (always)
+### Linear
+
+1. **Add build label** (ensure it exists, then add):
+   ```graphql
+   # Ensure label exists — check team labels, workspace labels, create if missing
+   mutation {
+     issueLabelCreate(input: {
+       teamId: "$LINEAR_TEAM_ID"
+       name: "$CLANCY_LABEL_BUILD"
+       color: "#0075ca"
+     }) { success issueLabel { id } }
+   }
+
+   # Fetch current label IDs on the issue, add build label ID
+   mutation {
+     issueUpdate(
+       id: "$ISSUE_UUID"
+       input: { labelIds: [...currentLabelIds, buildLabelId] }
+     ) { success }
+   }
+   ```
+
+2. **Remove plan label:**
+   ```graphql
+   # Fetch current label IDs, filter out plan label ID
+   mutation {
+     issueUpdate(
+       id: "$ISSUE_UUID"
+       input: { labelIds: [currentLabelIds without planLabelId] }
+     ) { success }
+   }
+   ```
 
-1. **Resolve "unstarted" state:**
+3. **State transition** (always):
    ```graphql
+   # Resolve "unstarted" state
    query {
      workflowStates(filter: {
        team: { id: { eq: "$LINEAR_TEAM_ID" } }
        type: { eq: "unstarted" }
-     }) {
-       nodes { id name }
-     }
+     }) { nodes { id name } }
    }
-   ```
-   Use `nodes[0].id` as the target state. If nodes is empty: warn `No 'unstarted' state found for team.` Skip transition.
 
-2. **Transition:**
-   ```graphql
+   # Transition
    mutation {
      issueUpdate(
        id: "$ISSUE_UUID"
@@ -409,6 +470,7 @@ Could not transition ticket. Move it manually to your implementation queue.
      ) { success }
    }
    ```
+   If no `unstarted` state found: warn, skip transition.
 
 On failure:
 ```
@@ -421,20 +483,13 @@ Could not transition ticket. Move it manually to your implementation queue.
 
 On success, display a board-specific message:
 
-**GitHub (with CLANCY_LABEL set):**
+**GitHub:**
 ```
-Plan promoted. Label swapped: {plan_label} → {impl_label}. Ready for /clancy:once.
+Plan promoted. Label swapped: {CLANCY_LABEL_PLAN} → {CLANCY_LABEL_BUILD}. Ready for /clancy:once.
 
 "Book 'em, Lou." — The ticket is ready for /clancy:once.
 ```
 
-**GitHub (without CLANCY_LABEL):**
-```
-Plan promoted. Label removed: {plan_label}. Add your implementation label manually, or run /clancy:once.
-
-"Book 'em, Lou."
-```
-
 **Jira (with transition):**
 ```
 Plan promoted. Ticket transitioned to {CLANCY_STATUS_PLANNED}.

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

@@ -136,9 +136,9 @@ Then skip to Step 3b with this single ticket.
 Build the JQL using planning-specific env vars:
 - `CLANCY_PLAN_STATUS` defaults to `Backlog` if not set
 - Sprint clause: include `AND sprint in openSprints()` if `CLANCY_JQL_SPRINT` is set
-- Label clause: include `AND labels = "$CLANCY_LABEL"` if `CLANCY_LABEL` is set
+- Label clause: include `AND labels = "$CLANCY_LABEL_PLAN"` if `CLANCY_LABEL_PLAN` is set (falls back to `CLANCY_PLAN_LABEL` if `CLANCY_LABEL_PLAN` is not set). If neither is set, include `AND labels = "$CLANCY_LABEL"` if `CLANCY_LABEL` is set.
 
-Full JQL: `project=$JIRA_PROJECT_KEY [AND sprint in openSprints()] [AND labels = "$CLANCY_LABEL"] AND assignee=currentUser() AND status="$CLANCY_PLAN_STATUS" ORDER BY priority ASC`
+Full JQL: `project=$JIRA_PROJECT_KEY [AND sprint in openSprints()] [AND labels = "$CLANCY_LABEL_PLAN"] AND assignee=currentUser() AND status="$CLANCY_PLAN_STATUS" ORDER BY priority ASC`
 
 ```bash
 RESPONSE=$(curl -s \
@@ -164,16 +164,16 @@ Then fetch issues:
 RESPONSE=$(curl -s \
   -H "Authorization: Bearer $GITHUB_TOKEN" \
   -H "X-GitHub-Api-Version: 2022-11-28" \
-  "https://api.github.com/repos/$GITHUB_REPO/issues?state=open&assignee=$GITHUB_USERNAME&labels=$CLANCY_PLAN_LABEL&per_page=<N>")
+  "https://api.github.com/repos/$GITHUB_REPO/issues?state=open&assignee=$GITHUB_USERNAME&labels=$CLANCY_LABEL_PLAN&per_page=<N>")
 ```
 
-- `CLANCY_PLAN_LABEL` defaults to `needs-refinement` if not set
+- `CLANCY_LABEL_PLAN` is the pipeline label for the planning queue (default: `clancy:plan`). Falls back to `CLANCY_PLAN_LABEL` if `CLANCY_LABEL_PLAN` is not set. If neither is set, defaults to `needs-refinement`.
 - Filter out PRs (entries with `pull_request` key)
 - For each issue, fetch comments: `GET /repos/$GITHUB_REPO/issues/{number}/comments`
 
 #### Linear
 
-Build the filter using `CLANCY_PLAN_STATE_TYPE` (defaults to `backlog` if not set):
+Build the filter using `CLANCY_PLAN_STATE_TYPE` (defaults to `backlog` if not set). If `CLANCY_LABEL_PLAN` is set (falls back to `CLANCY_PLAN_LABEL`), add a label filter to the query:
 
 ```graphql
 query {
@@ -182,6 +182,7 @@ query {
       filter: {
         state: { type: { eq: "$CLANCY_PLAN_STATE_TYPE" } }
         team: { id: { eq: "$LINEAR_TEAM_ID" } }
+        labels: { name: { eq: "$CLANCY_LABEL_PLAN" } }  # Only if CLANCY_LABEL_PLAN is set
       }
       first: $N
       orderBy: priority
@@ -214,7 +215,7 @@ If no tickets found:
 
 Then display board-specific guidance:
 
-- **GitHub:** `For GitHub: planning uses the "$CLANCY_PLAN_LABEL" label (default: needs-refinement), not "clancy". Apply that label to issues you want planned.`
+- **GitHub:** `For GitHub: planning uses the "$CLANCY_LABEL_PLAN" label (default: clancy:plan, fallback: $CLANCY_PLAN_LABEL or needs-refinement). Apply that label to issues you want planned.`
 - **Jira:** `Check that CLANCY_PLAN_STATUS (currently: "$CLANCY_PLAN_STATUS") matches a status in your Jira project, and that tickets in that status are assigned to you.`
 - **Linear:** `Check that CLANCY_PLAN_STATE_TYPE (currently: "$CLANCY_PLAN_STATE_TYPE") is a valid Linear state type (backlog, unstarted, started, completed, canceled, triage), and that tickets in that state are assigned to you in team $LINEAR_TEAM_ID.`
 

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

@@ -592,6 +592,74 @@ Note: as more roles are added in future versions, they appear as additional numb
 
 ---
 
+## Step 4c-2 — Pipeline labels (conditional)
+
+Only ask this if any optional role was enabled in Step 4c. If neither Planner nor Strategist was selected, skip this section entirely. If `CLANCY_LABEL` or `CLANCY_PLAN_LABEL` are already set in `.clancy/.env`, show:
+
+```
+Note: CLANCY_LABEL and CLANCY_PLAN_LABEL are deprecated.
+Use CLANCY_LABEL_BUILD and CLANCY_LABEL_PLAN instead.
+Your existing values will continue to work as fallbacks.
+```
+
+**If the user enabled Strategist (or both Strategist + Planner):**
+
+Output:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Pipeline Labels
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Clancy uses labels to move tickets through pipeline stages:
+  brief → plan → build
+
+Each label marks which queue a ticket belongs to.
+```
+
+Then ask each label in order:
+
+```
+What label marks tickets that have been briefed (awaiting approval)?
+[clancy:brief]
+```
+
+If a value is entered: store as `CLANCY_LABEL_BRIEF` in `.clancy/.env`. Wrap in double quotes.
+If enter is pressed: use default — store `CLANCY_LABEL_BRIEF="clancy:brief"` in `.clancy/.env`.
+
+```
+What label marks tickets that need planning?
+[clancy:plan]
+```
+
+If a value is entered: store as `CLANCY_LABEL_PLAN` in `.clancy/.env`. Wrap in double quotes.
+If enter is pressed: use default — store `CLANCY_LABEL_PLAN="clancy:plan"` in `.clancy/.env`.
+
+```
+What label marks tickets ready to build?
+[clancy:build]
+```
+
+If a value is entered: store as `CLANCY_LABEL_BUILD` in `.clancy/.env`. Wrap in double quotes.
+If enter is pressed: use default — store `CLANCY_LABEL_BUILD="clancy:build"` in `.clancy/.env`.
+
+**If the user enabled Planner only (no Strategist):**
+
+Skip `CLANCY_LABEL_BRIEF` (no `/clancy:brief` command). Ask only:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Pipeline Labels
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Clancy uses labels to move tickets through pipeline stages:
+  plan → build
+```
+
+Then ask `CLANCY_LABEL_PLAN` and `CLANCY_LABEL_BUILD` using the same prompts and defaults as above.
+
+---
+
 ## Step 4d (if Planner role selected): Planning queue config
 
 Only ask this if the user selected Planner in Step 4c above (or if re-running init and `CLANCY_ROLES` already includes `planner`).

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

@@ -396,6 +396,16 @@ MAX_ITERATIONS=5
 # CLANCY_GIT_PLATFORM=gitlab               # override auto-detection (github/gitlab/bitbucket)
 # CLANCY_GIT_API_URL=https://gitlab.example.com/api/v4  # self-hosted git API base URL
 
+# ─── Optional: Pipeline labels ────────────────────────────────────────────────
+# Labels that control ticket flow through pipeline stages.
+# CLANCY_LABEL_BRIEF marks tickets that have been briefed (awaiting approval).
+# CLANCY_LABEL_PLAN marks tickets that need planning.
+# CLANCY_LABEL_BUILD marks tickets ready for implementation.
+# Deprecated: CLANCY_LABEL (use CLANCY_LABEL_BUILD), CLANCY_PLAN_LABEL (use CLANCY_LABEL_PLAN)
+# CLANCY_LABEL_BRIEF="clancy:brief"
+# CLANCY_LABEL_PLAN="clancy:plan"
+# CLANCY_LABEL_BUILD="clancy:build"
+
 # ─── Optional: Rework loop ──────────────────────────────────────────────────
 # PR-based rework is automatic — when a reviewer leaves inline comments or
 # a conversation comment prefixed with "Rework:", Clancy picks it up on the
@@ -502,6 +512,16 @@ MAX_ITERATIONS=20
 # PLAYWRIGHT_STORYBOOK_PORT=6006
 # PLAYWRIGHT_STARTUP_WAIT=15
 
+# ─── Optional: Pipeline labels ────────────────────────────────────────────────
+# Labels that control ticket flow through pipeline stages.
+# CLANCY_LABEL_BRIEF marks tickets that have been briefed (awaiting approval).
+# CLANCY_LABEL_PLAN marks tickets that need planning.
+# CLANCY_LABEL_BUILD marks tickets ready for implementation.
+# Deprecated: CLANCY_LABEL (use CLANCY_LABEL_BUILD), CLANCY_PLAN_LABEL (use CLANCY_LABEL_PLAN)
+# CLANCY_LABEL_BRIEF="clancy:brief"
+# CLANCY_LABEL_PLAN="clancy:plan"
+# CLANCY_LABEL_BUILD="clancy:build"
+
 # ─── Optional: Rework loop ──────────────────────────────────────────────────
 # PR-based rework is automatic — when a reviewer leaves inline comments or
 # a conversation comment prefixed with "Rework:", Clancy picks it up on the
@@ -636,6 +656,16 @@ MAX_ITERATIONS=20
 # CLANCY_GIT_PLATFORM=gitlab               # override auto-detection (github/gitlab/bitbucket)
 # CLANCY_GIT_API_URL=https://gitlab.example.com/api/v4  # self-hosted git API base URL
 
+# ─── Optional: Pipeline labels ────────────────────────────────────────────────
+# Labels that control ticket flow through pipeline stages.
+# CLANCY_LABEL_BRIEF marks tickets that have been briefed (awaiting approval).
+# CLANCY_LABEL_PLAN marks tickets that need planning.
+# CLANCY_LABEL_BUILD marks tickets ready for implementation.
+# Deprecated: CLANCY_LABEL (use CLANCY_LABEL_BUILD), CLANCY_PLAN_LABEL (use CLANCY_LABEL_PLAN)
+# CLANCY_LABEL_BRIEF="clancy:brief"
+# CLANCY_LABEL_PLAN="clancy:plan"
+# CLANCY_LABEL_BUILD="clancy:build"
+
 # ─── Optional: Reliable autonomous mode ───────────────────────────────────────
 # Max self-healing attempts after verification failure (default: 2, range 0-5)
 # CLANCY_FIX_RETRIES=2

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

@@ -86,6 +86,14 @@ Strategist
   [T2] Issue type        {CLANCY_BRIEF_ISSUE_TYPE:-Task}
   [T3] Component         {CLANCY_COMPONENT if set, else "off"}
 
+{If Planner or Strategist enabled:}
+Pipeline Labels
+  [L1] Brief label         {CLANCY_LABEL_BRIEF if set, else "clancy:brief"}    (Strategist only)
+  [L2] Plan label          {CLANCY_LABEL_PLAN if set, else "clancy:plan"}
+  [L3] Build label         {CLANCY_LABEL_BUILD if set, else "clancy:build"}
+  {If CLANCY_LABEL or CLANCY_PLAN_LABEL set:}
+  ⚠ CLANCY_LABEL and CLANCY_PLAN_LABEL are deprecated. Use CLANCY_LABEL_BUILD and CLANCY_LABEL_PLAN.
+
 {If Planner enabled:}
 Planner
 {If Jira:}
@@ -539,6 +547,60 @@ If [2]: remove `CLANCY_COMPONENT` from `.clancy/.env`.
 
 ---
 
+### [L1] Brief label
+
+Only shown when Strategist is enabled.
+
+```
+Brief label — current: {value or "clancy:brief"}
+Label applied to tickets after /clancy:brief. Removed when the brief is approved.
+
+[1] clancy:brief (default)
+[2] Enter a different value
+[3] Cancel
+```
+
+If [1]: remove `CLANCY_LABEL_BRIEF` from `.clancy/.env` (uses default).
+If [2]: prompt `What label should /clancy:brief apply?` then write `CLANCY_LABEL_BRIEF=<value>` to `.clancy/.env`. Wrap in double quotes.
+
+---
+
+### [L2] Plan label
+
+Only shown when Planner or Strategist is enabled.
+
+```
+Plan label — current: {value or "clancy:plan"}
+Label applied to tickets that need planning. Removed when the plan is approved.
+
+[1] clancy:plan (default)
+[2] Enter a different value
+[3] Cancel
+```
+
+If [1]: remove `CLANCY_LABEL_PLAN` from `.clancy/.env` (uses default).
+If [2]: prompt `What label should mark tickets needing planning?` then write `CLANCY_LABEL_PLAN=<value>` to `.clancy/.env`. Wrap in double quotes.
+
+---
+
+### [L3] Build label
+
+Only shown when Planner or Strategist is enabled.
+
+```
+Build label — current: {value or "clancy:build"}
+Label applied to tickets ready for implementation. Used by /clancy:once and /clancy:run to filter the queue.
+
+[1] clancy:build (default)
+[2] Enter a different value
+[3] Cancel
+```
+
+If [1]: remove `CLANCY_LABEL_BUILD` from `.clancy/.env` (uses default).
+If [2]: prompt `What label should mark tickets ready to build?` then write `CLANCY_LABEL_BUILD=<value>` to `.clancy/.env`. Wrap in double quotes.
+
+---
+
 ### [P1] Plan queue status (Jira only)
 
 ```

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

@@ -218,13 +218,19 @@ Platform-specific pre-creation lookups.
 
 ### GitHub
 
+**Pipeline label for children:** Determine the pipeline label based on planner role and flags:
+- `--skip-plan` flag → `CLANCY_LABEL_BUILD` (default: `clancy:build`)
+- Planner role enabled (`CLANCY_ROLES` includes `planner`) → `CLANCY_LABEL_PLAN` (default: `clancy:plan`)
+- Planner role NOT enabled → `CLANCY_LABEL_BUILD` (default: `clancy:build`)
+
 **Labels to apply per ticket:**
-- `CLANCY_PLAN_LABEL` (default: `needs-refinement`) — planning queue
-- `CLANCY_LABEL` (if set) — Clancy identifier
+- The pipeline label determined above (`CLANCY_LABEL_PLAN` or `CLANCY_LABEL_BUILD`) — replaces `CLANCY_LABEL` on children
 - `component:{CLANCY_COMPONENT}` (if `CLANCY_COMPONENT` set)
 - `size:{S|M|L}` — from decomposition table
 - `clancy:afk` or `clancy:hitl` — from Mode column
 
+Note: `CLANCY_LABEL` is NOT applied to child tickets when pipeline labels are active. The pipeline label (`clancy:plan` or `clancy:build`) serves as the queue identifier.
+
 **Label pre-creation:** For each unique label, attempt to create it on the repo. If it already exists, GitHub returns 422 — ignore that error. If 403 (no admin access), note the label as unavailable.
 
 ```bash
@@ -266,7 +272,9 @@ Set CLANCY_BRIEF_ISSUE_TYPE in .clancy/.env.
 ```
 Stop.
 
-**Labels:** Jira auto-creates labels — no pre-creation needed. Apply: `CLANCY_LABEL` (if set), `clancy:afk` or `clancy:hitl`.
+**Pipeline label for children:** Same logic as GitHub — determine the pipeline label from `--skip-plan` flag and planner role.
+
+**Labels:** Jira auto-creates labels — no pre-creation needed. Apply: the pipeline label (`CLANCY_LABEL_PLAN` or `CLANCY_LABEL_BUILD`), `clancy:afk` or `clancy:hitl`. `CLANCY_LABEL` is NOT applied to children when pipeline labels are active.
 
 **Components:** If `CLANCY_COMPONENT` is set, it maps to the Jira `components` field.
 
@@ -297,7 +305,9 @@ query {
 }
 ```
 
-For each required label (`CLANCY_LABEL`, `component:{CLANCY_COMPONENT}`, `clancy:afk`, `clancy:hitl`): search by exact name. If not found in team labels, check workspace labels:
+**Pipeline label for children:** Same logic as GitHub/Jira — determine the pipeline label from `--skip-plan` flag and planner role.
+
+For each required label (the pipeline label, `component:{CLANCY_COMPONENT}`, `clancy:afk`, `clancy:hitl`): search by exact name. `CLANCY_LABEL` is NOT applied to children when pipeline labels are active. If not found in team labels, check workspace labels:
 
 ```graphql
 query {
@@ -370,7 +380,7 @@ curl -s \
   -d '{
     "title": "{ticket title}",
     "body": "Epic: #{parent_number}\n\n## {Title}\n\n{Description}\n\n---\n\n**Parent:** #{parent_number}\n**Brief:** {slug}\n**Size:** {S|M|L}\n\n### Dependencies\n\n{Depends on #NN lines or None}\n\n---\n\n*Created by Clancy from strategic brief.*",
-    "labels": ["{CLANCY_PLAN_LABEL}", "size:{size}", "clancy:{mode}", ...],
+    "labels": ["{PIPELINE_LABEL}", "size:{size}", "clancy:{mode}", ...],
     "assignees": ["{resolved_username}"]
   }'
 ```
@@ -412,7 +422,7 @@ curl -s \
       },
       "issuetype": { "name": "{CLANCY_BRIEF_ISSUE_TYPE or Task}" },
       "parent": { "key": "{PARENT_KEY}" },
-      "labels": ["{CLANCY_LABEL}", "clancy:{mode}"]
+      "labels": ["{PIPELINE_LABEL}", "clancy:{mode}"]
     }
   }'
 ```
@@ -631,6 +641,60 @@ Created by Clancy on {YYYY-MM-DD}.
 
 ---
 
+## Step 11a — Remove brief label from parent
+
+Only if a parent ticket exists AND all tickets were created successfully. Remove `CLANCY_LABEL_BRIEF` from the parent ticket. Best-effort — warn on failure, never stop.
+
+Read `CLANCY_LABEL_BRIEF` from `.clancy/.env`. Default: `clancy:brief`.
+
+### GitHub
+
+```bash
+curl -s \
+  -H "Authorization: Bearer $GITHUB_TOKEN" \
+  -H "Accept: application/vnd.github+json" \
+  -H "X-GitHub-Api-Version: 2022-11-28" \
+  -X DELETE \
+  "https://api.github.com/repos/$GITHUB_REPO/issues/$PARENT_NUMBER/labels/$(echo $CLANCY_LABEL_BRIEF | jq -Rr @uri)"
+```
+
+Ignore 404 (label may not be present on the parent).
+
+### Jira
+
+```bash
+CURRENT_LABELS=$(curl -s \
+  -u "$JIRA_USER:$JIRA_API_TOKEN" \
+  -H "Accept: application/json" \
+  "$JIRA_BASE_URL/rest/api/3/issue/$PARENT_KEY?fields=labels" | jq -r '.fields.labels')
+
+UPDATED_LABELS=$(echo "$CURRENT_LABELS" | jq --arg brief "$CLANCY_LABEL_BRIEF" '[.[] | select(. != $brief)]')
+
+curl -s \
+  -u "$JIRA_USER:$JIRA_API_TOKEN" \
+  -X PUT \
+  -H "Content-Type: application/json" \
+  "$JIRA_BASE_URL/rest/api/3/issue/$PARENT_KEY" \
+  -d "{\"fields\": {\"labels\": $UPDATED_LABELS}}"
+```
+
+### Linear
+
+```bash
+# Fetch current label IDs on the parent, remove the brief label ID, issueUpdate
+# Use the same pattern as brief.md Step 10a — query labels, filter, update
+```
+
+### On failure
+
+```
+⚠️  Could not remove brief label from {PARENT_KEY}. Remove it manually if needed.
+```
+
+Continue — do not stop.
+
+---
+
 ## Step 12 — Display summary
 
 Show the final result: