@cleocode/skills 2026.9.25 → 2026.9.26

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cleocode/skills",
3
- "version": "2026.9.25",
3
+ "version": "2026.9.26",
4
4
  "description": "CLEO skill definitions - bundled with CLEO monorepo",
5
5
  "main": "index.js",
6
6
  "types": "index.d.ts",
@@ -221,5 +221,5 @@ If work cannot proceed:
221
221
  | Returning full content | Bloats orchestrator context | Return only summary message |
222
222
  | Manual JSONL append | No validation, race conditions | Use `cleo research add` |
223
223
  | Missing manifest entry | Orchestrator can't find findings | Always create manifest entry |
224
- | Skipping task start | Protocol violation | Always `cleo start` before work |
224
+ | Skipping task start | Protocol violation | Always `cleo start` before work. If `cleo start` fails with `E_SESSION_UNBOUND` (spawned workers and subagents are already bound), run `cleo session start --scope global --name "<name>"` or `cleo session resume <id>` first. |
225
225
  | Incomplete checklist | Protocol violation | Verify all items before return |
@@ -25,7 +25,7 @@ Skills and templates SHOULD reference this file instead of hardcoding CLEO comma
25
25
 
26
26
  **Purpose**: Mark task as active/in-progress.
27
27
 
28
- **CLEO Default**: `cleo start {{TASK_ID}}`
28
+ **CLEO Default**: `cleo start {{TASK_ID}}`. If `cleo start` fails with `E_SESSION_UNBOUND` (spawned workers and subagents are already bound), run `cleo session start --scope global --name "<name>"` or `cleo session resume <id>` first.
29
29
 
30
30
  ### Complete Task
31
31
 
@@ -2,14 +2,14 @@
2
2
  name: ct-cleo
3
3
  description: CLEO task management protocol - session, task, and workflow guidance. Use when managing tasks, sessions, or multi-agent workflows with the CLEO CLI protocol.
4
4
  metadata:
5
- version: 2.24.1
5
+ version: 2.24.3
6
6
  tier: core
7
7
  install: harness
8
8
  covers:
9
9
  - packages/cleo/src/cli/commands/session.ts
10
10
  - packages/cleo/src/cli/commands/focus.ts
11
11
  - packages/cleo/src/cli/commands/sticky.ts
12
- lastReviewed: 2026-09-29
12
+ lastReviewed: 2026-09-30
13
13
  stability: stable
14
14
  ---
15
15
 
@@ -124,13 +124,13 @@ Code-graph answers (`cleo nexus impact`, `context`, `full-context`, `why`, `sear
124
124
 
125
125
  ## Sessions are terminal-bound (T12500)
126
126
 
127
- `cleo session start` binds the calling agent process (`CLAUDE_CODE_SESSION_ID`,
128
- `CODEX_THREAD_ID`, …), pane (`TMUX_PANE`, …) or tab (`TERM_SESSION_ID`, …). Session
129
- mutations from an unbound caller fail with `E_SESSION_UNBOUND` instead of
127
+ `cleo session start` binds the calling agent process (`CLAUDE_CODE_SESSION_ID`, `CODEX_THREAD_ID`, …), pane (`TMUX_PANE`, …), tab (`TERM_SESSION_ID`, …), CI job (`GITHUB_RUN_ID`+`GITHUB_RUN_ATTEMPT`+`GITHUB_JOB`, `CI_JOB_ID`) or ssh login tty (`SSH_TTY`+`SSH_CONNECTION`).
128
+ With no provider key it also walks the process tree (T12864): a known single-agent harness (Kimi, aider, amp, cursor-agent, … — past its per-call `bash -c` shells) or an interactive / script shell becomes the identity, so `session start` then `cleo start` in separate `bash -c` calls share one session; a harness below a human's tab / pane, an ssh login or a CI job gets its own, more specific key, so it must run `cleo session start` itself.
129
+ Any other host (a node / python orchestrator, an IDE extension host, a daemon, anything under pid 1) identifies nobody and keeps the single-session guard: multi-agent hosts and multi-step scripts must set `CLEO_SESSION_ID` (or `CLEO_AGENT_ID`, only in a long-lived host process: under a short-lived one such as `make` the key changes per call) per agent.
130
+ Session mutations from an unbound caller fail with `E_SESSION_UNBOUND` instead of
130
131
  guessing the newest session; bind with `cleo session start`, `cleo session resume
131
- <id>` or `CLEO_SESSION_ID=<id>`, or name the target with `--session <id>`. CI and
132
- multi-step scripts must export `CLEO_SESSION_ID`. Unattributed mutations warn on
133
- stderr; `session status` / `briefing` label a guessed session `unbound: true`.
132
+ <id>` or `CLEO_SESSION_ID=<id>`, or name the target with `--session <id>`. Separate one-shot `ssh host 'cleo …'` calls are separate callers: export `CLEO_SESSION_ID` there.
133
+ Unattributed mutations warn on stderr; `session status` / `briefing` label a guessed session `unbound: true`.
134
134
 
135
135
  - A session a human started in a tab is adopted by Claude Code in that tab
136
136
  (also after a Claude restart). An adopter works in it but cannot end it without
@@ -16,4 +16,4 @@
16
16
  | Returning content | Context bloat | Return only summary message |
17
17
  | Pretty-printed JSON | Invalid manifest | Single-line JSON |
18
18
  | Loading skills via `@` | Cannot resolve | Skills injected by orchestrator |
19
- | Skipping task start | Protocol violation | Always `cleo start` first |
19
+ | Skipping task start | Protocol violation | Always `cleo start` first. If `cleo start` fails with `E_SESSION_UNBOUND` (spawned workers and subagents are already bound), run `cleo session start --scope global --name "<name>"` or `cleo session resume <id>` first. |
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: ct-dev-workflow
3
3
  description: Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches, or following contribution protocols. Triggers on commit operations, release preparation, or workflow compliance needs.
4
- version: 3.1.4
4
+ version: 3.1.5
5
5
  protocol: contribution
6
6
  dependencies: []
7
7
  sharedResources:
@@ -14,12 +14,12 @@ compatibility:
14
14
  - gemini-cli
15
15
  license: MIT
16
16
  metadata:
17
- version: 3.1.4
17
+ version: 3.1.5
18
18
  tier: core
19
19
  install: harness
20
20
  covers:
21
21
  - .github/workflows/release-prepare.yml
22
- lastReviewed: 2026-09-29
22
+ lastReviewed: 2026-09-30
23
23
  stability: stable
24
24
  ---
25
25
 
@@ -80,6 +80,10 @@ cleo current
80
80
  cleo find "relevant query"
81
81
  cleo add "Task title" --description "What you're doing" --parent T001
82
82
  cleo start T123
83
+ # 3. If 'cleo start' fails with E_SESSION_UNBOUND (spawned workers and
84
+ # subagents are already bound), bind first, then retry:
85
+ # cleo session start --scope global --name "<what you are doing>"
86
+ # (or: cleo session resume <id>)
83
87
  ```
84
88
 
85
89
  ### Commit Message Format
@@ -329,7 +333,7 @@ head SHA is green: `gh pr merge <n> --admin --merge` — see
329
333
  ```bash
330
334
  # Task lifecycle
331
335
  cleo current # Current task
332
- cleo start T123 # Start task
336
+ cleo start T123 # Start task (on E_SESSION_UNBOUND: bind a session, see above)
333
337
  cleo complete T123 # Mark done
334
338
 
335
339
  # Find existing work
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: ct-documentor
3
3
  description: Documentation coordinator with CLEO style guide compliance. Routes every canonical-doc write (spec, adr, research, handoff, note, llm-readme) through the docs SSoT via `cleo docs add` / `cleo docs publish` / `cleo docs fetch` — never raw filesystem writes. Carries the CLEO writing and review guides as references and coordinates ct-spec-writer and ct-adr-recorder. Use when creating or updating documentation files, consolidating scattered documentation, or validating documentation against style standards. Triggers on documentation tasks, doc update requests, or style guide compliance checks.
4
- version: 3.17.3
4
+ version: 3.17.4
5
5
  protocol: null
6
6
  dependencies:
7
7
  - ct-spec-writer
@@ -16,13 +16,13 @@ compatibility:
16
16
  - gemini-cli
17
17
  license: MIT
18
18
  metadata:
19
- version: 3.17.3
19
+ version: 3.17.4
20
20
  tier: core
21
21
  install: harness
22
22
  covers:
23
23
  - packages/cleo/src/cli/commands/docs.ts
24
24
  - packages/contracts/src/docs-taxonomy.ts
25
- lastReviewed: 2026-09-28
25
+ lastReviewed: 2026-09-30
26
26
  stability: stable
27
27
  ---
28
28
 
@@ -851,7 +851,10 @@ Before completing, verify:
851
851
  # 1. Read task details
852
852
  cleo show {TASK_ID}
853
853
 
854
- # 2. Start task
854
+ # 2. Start task. If it fails with E_SESSION_UNBOUND (spawned workers and
855
+ # subagents are already bound), run
856
+ # 'cleo session start --scope global --name "<what you are doing>"'
857
+ # or 'cleo session resume <id>' first, then retry.
855
858
  cleo start {TASK_ID}
856
859
 
857
860
  # 3. Execute documentation workflow (phases 1-4)
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: ct-epic-architect
3
3
  description: Epic planning and task decomposition for breaking down large initiatives into atomic, executable tasks. Provides dependency analysis, wave-based parallel execution planning, hierarchy management, and research linking. Use when creating epics, decomposing initiatives into task trees, planning parallel workflows, or analyzing task dependencies. Triggers on epic creation, task decomposition requests, or planning phase work.
4
- version: 3.0.3
4
+ version: 3.0.4
5
5
  protocol: decomposition
6
6
  adrRefs:
7
7
  - ADR-066
@@ -17,14 +17,14 @@ compatibility:
17
17
  - gemini-cli
18
18
  license: MIT
19
19
  metadata:
20
- version: 3.0.3
20
+ version: 3.0.4
21
21
  tier: on-demand
22
22
  install: harness
23
23
  covers:
24
24
  - packages/core/src/validation/protocols/cant/decomposition.cant
25
25
  - packages/core/src/validation/protocols/protocols-markdown/decomposition.md
26
26
  loomStage: decomposition
27
- lastReviewed: 2026-09-28
27
+ lastReviewed: 2026-09-30
28
28
  stability: stable
29
29
  ---
30
30
 
@@ -59,7 +59,7 @@ Context injection for epic planning and task decomposition tasks spawned via cle
59
59
  ### Execution Sequence
60
60
 
61
61
  1. Read task: `cleo show {{TASK_ID}}`
62
- 2. Start task: `cleo start {{TASK_ID}}`
62
+ 2. Start task: `cleo start {{TASK_ID}}`. If `cleo start` fails with `E_SESSION_UNBOUND` (spawned workers and subagents are already bound), run `cleo session start --scope global --name "<name>"` or `cleo session resume <id>` first.
63
63
  3. Check existing work: `cleo find "keyword"`, `cleo list --type epic`
64
64
  4. Create epic and child tasks
65
65
  5. Attach files and link research
@@ -2,13 +2,13 @@
2
2
  name: ct-lead
3
3
  description: "Phase Lead orchestration playbook for spawning and supervising a parallel worker swarm in one wave. Use when spawned by ct-orchestrator with role=orchestrator to fan out N leaf workers via delegate_task, drain the epic-{TID}.wave-{n} conduit topic plus pipeline_manifest, await rollupWaveStatus convergence, and return ONE rolled-up contract string to the parent Orchestrator. Triggers: 'phase lead', 'wave lead', 'supervise wave', 'fan out workers', 'aggregate worker results', 'rollup wave', any task with role=orchestrator that is itself a child of another orchestrator. Implements ADR-070 hierarchical orchestration."
4
4
  metadata:
5
- version: 1.0.7
5
+ version: 1.0.8
6
6
  tier: core
7
7
  install: harness
8
8
  covers:
9
9
  - packages/core/src/orchestration/lead-rollup.ts
10
10
  - packages/core/src/orchestration/waves.ts
11
- lastReviewed: 2026-09-29
11
+ lastReviewed: 2026-09-30
12
12
  stability: stable
13
13
  ---
14
14
 
@@ -69,6 +69,9 @@ cleo orchestrate ready "${EPIC}"
69
69
  cleo orchestrate waves "${EPIC}"
70
70
  ```
71
71
 
72
+ Run these from the epic's project root (or a worktree of it): member order within
73
+ a wave uses the calling session's focus phase, resolved from that project (T12501).
74
+
72
75
  ### 2. Parallel Fanout (one batch)
73
76
 
74
77
  Issue ONE `delegate_task` call with the full worker list. Each worker gets
@@ -226,7 +226,7 @@
226
226
  },
227
227
  {
228
228
  "name": "ct-cleo",
229
- "version": "2.24.1",
229
+ "version": "2.24.3",
230
230
  "description": "CLEO task management protocol - session, task, and workflow guidance. Use when managing tasks, sessions, or multi-agent workflows with the CLEO CLI protocol.",
231
231
  "path": "skills/ct-cleo",
232
232
  "tier": 0,
@@ -566,7 +566,7 @@
566
566
  },
567
567
  {
568
568
  "name": "ct-dev-workflow",
569
- "version": "3.1.4",
569
+ "version": "3.1.5",
570
570
  "description": "Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches, or following contribution protocols. Triggers on commit operations, release preparation, or workflow compliance needs.",
571
571
  "path": "skills/ct-dev-workflow",
572
572
  "tier": 0,
@@ -642,7 +642,7 @@
642
642
  },
643
643
  {
644
644
  "name": "ct-documentor",
645
- "version": "3.17.3",
645
+ "version": "3.17.4",
646
646
  "description": "Documentation coordinator with CLEO style guide compliance. Routes every canonical-doc write (spec, adr, research, handoff, note, llm-readme) through the docs SSoT via `cleo docs add` / `cleo docs publish` / `cleo docs fetch` — never raw filesystem writes. Carries the CLEO writing and review guides as references and coordinates ct-spec-writer and ct-adr-recorder. Use when creating or updating documentation files, consolidating scattered documentation, or validating documentation against style standards. Triggers on documentation tasks, doc update requests, or style guide compliance checks.",
647
647
  "path": "skills/ct-documentor",
648
648
  "tier": 0,
@@ -728,7 +728,7 @@
728
728
  },
729
729
  {
730
730
  "name": "ct-epic-architect",
731
- "version": "3.0.3",
731
+ "version": "3.0.4",
732
732
  "description": "Epic planning and task decomposition for breaking down large initiatives into atomic, executable tasks. Provides dependency analysis, wave-based parallel execution planning, hierarchy management, and research linking. Use when creating epics, decomposing initiatives into task trees, planning parallel workflows, or analyzing task dependencies. Triggers on epic creation, task decomposition requests, or planning phase work.",
733
733
  "path": "skills/ct-epic-architect",
734
734
  "tier": 1,
@@ -965,7 +965,7 @@
965
965
  },
966
966
  {
967
967
  "name": "ct-lead",
968
- "version": "1.0.7",
968
+ "version": "1.0.8",
969
969
  "description": "Phase Lead orchestration playbook for spawning and supervising a parallel worker swarm in one wave. Use when spawned by ct-orchestrator with role=orchestrator to fan out N leaf workers via delegate_task, drain the epic-{TID}.wave-{n} conduit topic plus pipeline_manifest, await rollupWaveStatus convergence, and return ONE rolled-up contract string to the parent Orchestrator. Triggers: 'phase lead', 'wave lead', 'supervise wave', 'fan out workers', 'aggregate worker results', 'rollup wave', any task with role=orchestrator that is itself a child of another orchestrator. Implements ADR-070 hierarchical orchestration.",
970
970
  "path": "skills/ct-lead",
971
971
  "tier": 0,