@cleocode/skills 2026.9.21 → 2026.9.22

package/skills/_shared/manifest-operations.md

@@ -15,7 +15,7 @@ The manifest system provides O(1) append operations and race-condition-free conc
 **Default Paths**:
 - Output directory: `.cleo/agent-outputs/` (configurable via `agentOutputs.directory`)
 - Manifest store: `pipeline_manifest` SQLite table (canonical per ADR-027)
-- CLI: `cleo manifest append <json>` — the only supported write path
+- CLI: `cleo manifest append --entry '<json>'` — the only supported write path
 
 **Design Principles**:
 - Append-only writes preserve audit trail
@@ -239,12 +239,9 @@ cleo research show jwt-auth-2026-02-07  # Check linked_tasks
 
 ---
 
-### cleo research unlink
+### research unlink (retired)
 
-> **Note**: Not currently implemented in the CLI. To disassociate research from a task, use
-> `cleo research update <id>` to change status, or remove the link manually from the task record.
-
----
+Retired. Link edits go through `cleo research link`; there is no unlink verb.
 
 ### cleo research links
 
@@ -322,19 +319,13 @@ cleo research archive --before-date 2026-01-01
 
 ---
 
-### cleo research archive-list
+### research archive-list (retired)
 
-> **Note**: Not currently implemented in the CLI. To list archived entries, use
-> `cleo research list --status archived` or query the archive file directly.
-
----
+Retired. List archived entries with `cleo manifest list --filter archived`.
 
-### cleo research status
+### research status (retired)
 
-> **Note**: Not currently implemented as a separate CLI command. Use `cleo research stats`
-> for manifest statistics.
-
----
+Retired. Use `cleo research stats` or `cleo manifest stats`.
 
 ### cleo research stats
 
@@ -369,33 +360,21 @@ cleo research stats
 
 ---
 
-### cleo research validate
-
-> **Note**: Not currently implemented in the CLI. Manifest validation occurs automatically
-> when entries are created via `cleo research add`.
-
----
-
-### cleo research compact
+### research validate (retired)
 
-> **Note**: Not currently implemented in the CLI. Use `cleo research archive` to manage
-> manifest size.
+Retired. Validate a subagent's output with `cleo orchestrate validate <taskId>` or `cleo check output`.
 
----
+### research compact (retired)
 
-### cleo research get
+Retired. The pipeline_manifest table needs no compaction (ADR-027).
 
-> **Note**: Not currently implemented as a separate CLI command. Use `cleo research show <id>`
-> for entry details.
+### research get (retired)
 
----
-
-### cleo research inject
+Retired. Use `cleo research show <id>` or `cleo manifest show <id>`.
 
-> **Note**: Not currently implemented in the CLI. The orchestrator generates fully-resolved
-> subagent prompts via `cleo orchestrator spawn <taskId>`.
+### research inject (retired)
 
----
+Retired. `cleo orchestrate spawn <taskId>` embeds the subagent protocol in the prompt it returns.
 
 ## Manifest Entry Schema
 
@@ -454,7 +433,7 @@ When present, the `audit` field provides operational metadata:
 | `{{EPIC_ID}}` | Parent epic identifier | `T3147` |
 | `{{DATE}}` | Current date | `2026-02-07` |
 | `{{TOPIC_SLUG}}` | URL-safe topic name | `jwt-authentication` |
-| `{{OUTPUT_DIR}}` | Output directory | `.cleo/agent-outputs` |
+| `{{OUTPUT_DIR}}` | Output directory | `.cleo/agent-outputs` (legacy token — do not write there; record output with `cleo docs add`) |
 
 
 ### Command Tokens (CLEO Defaults)
@@ -477,7 +456,7 @@ When present, the `audit` field provides operational metadata:
 ```markdown
 ## Output Requirements
 
-1. Write findings to `{{OUTPUT_DIR}}/{{DATE}}_{{TOPIC_SLUG}}.md`
+1. Record findings with `cleo docs add {{TASK_ID}} --content - --type <kind> --slug {{TOPIC_SLUG}}`
 2. Create manifest entry:
 
 ```bash
@@ -526,7 +505,7 @@ echo '{"id": "test", "title": "Test"}' >> .cleo/agent-outputs/legacy-manifest.js
 
 **Solution**: Use `cleo manifest append`
 ```bash
-cleo manifest append '{"id":"test","task_id":"T###","type":"research","status":"complete","output":"path/to/output.md","summary":"brief","key_findings":["..."]}'
+cleo manifest append --entry '{"id":"test","task_id":"T###","type":"research","status":"complete","output":"path/to/output.md","summary":"brief","key_findings":["..."]}'
 ```
 
 ---
@@ -542,7 +521,7 @@ echo "$json" >> .cleo/agent-outputs/legacy-manifest.jsonl
 
 **Solution**: Use `cleo manifest append`
 ```bash
-cleo manifest append '{"id":"...","task_id":"T####","type":"...","status":"complete","output":"...","summary":"...","key_findings":["..."]}'
+cleo manifest append --entry '{"id":"...","task_id":"T####","type":"...","status":"complete","output":"...","summary":"...","key_findings":["..."]}'
 ```
 
 ---

package/skills/_shared/skill-chaining-patterns.md

@@ -41,7 +41,7 @@ The orchestrator delegates work to a subagent via `orchestrate.spawn` with skill
 
 ```bash
 # Generate fully-resolved spawn prompt
-cleo orchestrator spawn T1234 --json
+cleo orchestrate spawn T1234 --json
 
 # Provider adapter executes the prompt using its native mechanism
 #    - Claude Code: Task tool with cleo-subagent type
@@ -84,14 +84,10 @@ A skill invokes other skills to complete workflow phases. The loaded skill maint
 
 ```markdown
 # Via Skill tool (programmatic)
-Skill(skill="ct-docs-lookup")
-Skill(skill="ct-docs-write")
-Skill(skill="ct-docs-review")
+Skill(skill="ct-documentor")   # writing + review references
 
 # Via slash command (user-facing)
-/ct-docs-lookup
-/ct-docs-write
-/ct-docs-review
+/ct-documentor
 ```
 
 ### When to Use Skill Chaining
@@ -180,7 +176,7 @@ Subagent MUST NOT return output content in response.
 ### Rule 3: File-Based Details (MUST)
 
 Detailed findings go to output files, not manifest or response:
-- Full analysis → `{{OUTPUT_DIR}}/YYYY-MM-DD_topic.md`
+- Full analysis → `cleo docs add <taskId> --content - --type research --slug <topic>`
 - Summary only → pipeline_manifest key_findings (via `cleo manifest append`)
 
 ### Rule 4: Token Injection (SHOULD)
@@ -213,7 +209,7 @@ TOPIC_SLUG    # URL-safe topic name
 Before spawning subagent:
 - [ ] Identify appropriate skill for task type
 - [ ] Prepare token context (TASK_ID, DATE, TOPIC_SLUG)
-- [ ] `cleo orchestrator spawn <taskId> --json`
+- [ ] `cleo orchestrate spawn <taskId> --json`
 - [ ] Verify token resolution is complete (`tokenResolution.fullyResolved`)
 
 Before chaining to another skill:

package/skills/_shared/subagent-protocol-base.md

@@ -15,8 +15,8 @@ All subagents operating under an orchestrator MUST follow this protocol.
 
 | ID | Rule | Compliance |
 |----|------|------------|
-| OUT-001 | MUST write findings to `{{OUTPUT_DIR}}/{{DATE}}_{{TOPIC_SLUG}}.md` | Required |
-| OUT-002 | MUST append ONE entry via `cleo manifest append <json>` (writes to pipeline_manifest table per ADR-027/T1093) | Required |
+| OUT-001 | MUST record findings with `cleo docs add {{TASK_ID}} --content - --type <kind> --slug {{TOPIC_SLUG}}` (never a raw file under `.cleo/agent-outputs/`) | Required |
+| OUT-002 | MUST append ONE entry via `cleo manifest append --entry '<json>'` (writes to pipeline_manifest table per ADR-027/T1093) | Required |
 | OUT-003 | MUST return ONLY: "[Type] complete. Manifest appended to pipeline_manifest." | Required |
 | OUT-004 | MUST NOT return output content in response | Required |
 
@@ -36,7 +36,7 @@ Valid return messages:
 
 ## Output File Format
 
-Write to `{{OUTPUT_DIR}}/{{DATE}}_{{TOPIC_SLUG}}.md`:
+Record it with `cleo docs add {{TASK_ID}} --content - --type <kind> --slug {{TOPIC_SLUG}}`, using this body:
 
 ```markdown
 # {{TITLE}}
@@ -107,7 +107,7 @@ Reference: @skills/_shared/task-system-integration.md
 1. Read task:    {{TASK_SHOW_CMD}} {{TASK_ID}}
 2. Start task:   {{TASK_START_CMD}} {{TASK_ID}}
 3. Do work:      [skill-specific execution]
-4. Write output: {{OUTPUT_DIR}}/{{DATE}}_{{TOPIC_SLUG}}.md
+4. Record output: `cleo docs add {{TASK_ID}} --content - --type <kind> --slug {{TOPIC_SLUG}}`
 5. Create manifest entry: cleo research add [flags]
 6. Complete:     {{TASK_COMPLETE_CMD}} {{TASK_ID}}
 7. Return:       "[Type] complete. Manifest appended to pipeline_manifest."
@@ -154,7 +154,7 @@ Reference: @skills/_shared/task-system-integration.md
 Before returning, verify:
 
 - [ ] Task started via `{{TASK_START_CMD}}`
-- [ ] Output file written to `{{OUTPUT_DIR}}/`
+- [ ] Output recorded with `cleo docs add` (slug in the return message)
 - [ ] Manifest entry created via `cleo research add`
 - [ ] Task completed via `{{TASK_COMPLETE_CMD}}`
 - [ ] Response is ONLY the summary message
@@ -177,7 +177,7 @@ Before returning, verify:
 |-------|---------|-------------|
 | `{{EPIC_ID}}` | `""` | Parent epic ID |
 | `{{SESSION_ID}}` | `""` | Session identifier |
-| `{{OUTPUT_DIR}}` | `.cleo/agent-outputs` | Output directory |
+| `{{OUTPUT_DIR}}` | `.cleo/agent-outputs` | Output directory (legacy token — do not write there; record output with `cleo docs add`) |
 
 ### Task System Tokens (CLEO defaults)
 

package/skills/_shared/task-system-integration.md

@@ -133,24 +133,24 @@ Sessions persist across Claude conversations and support long-running work.
 - Sessions receive timeout warning after **72 hours** of inactivity
 - Active sessions are auto-ended after **7 days** (configurable via `retention.autoEndActiveAfterDays`)
 - Ended/suspended sessions can be cleaned up with `cleo session gc`
-- Stale active sessions (72h+) cleaned with `cleo session gc --include-active`
+- Stale active sessions cleaned with `cleo session gc --max-age <days>`
 
 **Session Commands**:
 
 | Command | Purpose |
 |---------|---------|
-| `cleo session start --scope epic:{{EPIC_ID}}` | Begin scoped session |
+| `cleo session start --scope epic:{{EPIC_ID}} --name "..."` | Begin scoped session (`--name` is required) |
 | `cleo session end --note "summary"` | End session properly |
 | `cleo session list` | Check existing sessions |
 | `cleo session resume <id>` | Resume previous session |
 | `cleo session gc` | Clean up ended/suspended sessions |
-| `cleo session gc --include-active` | Also clean stale active sessions |
+| `cleo session gc --max-age <days>` | Also end active sessions older than N days |
 
 **Best Practices**:
 - **MUST** check `cleo session list` before starting new sessions
 - **SHOULD** end sessions properly with `cleo session end --note "summary"` to avoid accumulation
 - **SHOULD** use `cleo session gc` periodically to clean up old ended/suspended sessions
-- **MAY** use `cleo session gc --include-active` to clean stale active sessions (72h+ inactive)
+- **MAY** use `cleo session gc --max-age <days>` to end stale active sessions
 - Long-running sessions (multi-day work) are expected and supported
 
 ---
@@ -168,7 +168,7 @@ When tokens are not explicitly configured, assume CLEO defaults:
 | `{{TASK_LIST_CMD}}` | `cleo list` |
 | `{{TASK_FIND_CMD}}` | `cleo find` |
 | `{{TASK_ADD_CMD}}` | `cleo add` |
-| `{{OUTPUT_DIR}}` | `.cleo/agent-outputs` |
+| `{{OUTPUT_DIR}}` | `.cleo/agent-outputs` (legacy token — do not write there; record output with `cleo docs add`) |
 
 
 ---

package/skills/ct-adr-recorder/SKILL.md

@@ -2,14 +2,18 @@
 name: ct-adr-recorder
 description: "Records Architecture Decision Records from accepted consensus verdicts. Use when promoting a consensus outcome to a formal ADR: drafts the document in the proposed-then-accepted HITL lifecycle, links to the originating consensus manifest, persists the decision to the canonical SQLite decisions table, and triggers downstream invalidation when an accepted ADR is later superseded. Triggers on phrases like 'write ADR', 'record architecture decision', 'formalize this decision', 'lock in the choice', 'create ADR-XXX', or when a consensus task reaches completed status and needs formalization."
 protocol: architecture_decision
-loomStage: architecture_decision
 adrRefs:
   - ADR-053
   - ADR-070
 metadata:
-  version: 1.0.0
+  version: 1.0.2
   tier: on-demand
   install: harness
+  covers:
+    - packages/core/src/validation/protocols/cant/architecture-decision.cant
+    - packages/core/src/validation/protocols/protocols-markdown/architecture-decision.md
+  loomStage: architecture_decision
+  lastReviewed: 2026-09-28
   stability: stable
 ---
 
@@ -229,27 +233,24 @@ Validate every ADR manifest entry through `cleo check protocol`:
 
 ```bash
 # Draft reaches proposed: runs inside the skill, before HITL hand-off.
-cleo check protocol \
-  --protocolType architecture-decision \
-  --taskId T4798 \
+cleo check protocol architecture-decision \
+  --task-id T4798 \
   --status proposed \
-  --persistedInDb true \
-  --adrContent "$(cat docs/adr/ADR-0042.md)"
+  --persisted-in-db true \
+  --adr-content "$(cat docs/adr/ADR-0042.md)"
 
 # HITL accepts the ADR: rerun with the review flag.
-cleo check protocol \
-  --protocolType architecture-decision \
-  --taskId T4798 \
+cleo check protocol architecture-decision \
+  --task-id T4798 \
   --status accepted \
-  --hitlReviewed true \
-  --persistedInDb true
+  --hitl-reviewed true \
+  --persisted-in-db true
 
 # Later supersession: include the cascade flag.
-cleo check protocol \
-  --protocolType architecture-decision \
-  --taskId T4798 \
+cleo check protocol architecture-decision \
+  --task-id T4798 \
   --status superseded \
-  --downstreamFlagged true
+  --downstream-flagged true
 ```
 
 Exit code 0 = valid. Exit code 65 = `HANDOFF_REQUIRED`. Exit code 18 = `CASCADE_FAILED`. Exit code 84 = `PROVENANCE_REQUIRED` (attempted ADR without a linked consensus).
@@ -275,7 +276,7 @@ Exit code 0 = valid. Exit code 65 = `HANDOFF_REQUIRED`. Exit code 18 = `CASCADE_
 5. The manifest entry MUST set `agent_type: "decision"` and reference the output markdown file.
 6. Superseding an accepted ADR MUST trigger the downstream cascade over linked specs, decomps, and impls.
 7. Agents MUST NOT retry the HITL handoff on a loop; wait for the human reviewer.
-8. Always validate via `cleo check protocol --protocolType architecture-decision` before exiting.
+8. Always validate via `cleo check protocol architecture-decision` before exiting.
 
 ## See also / References
 

package/skills/ct-artifact-publisher/SKILL.md

@@ -2,9 +2,13 @@
 name: ct-artifact-publisher
 description: "Builds and publishes artifacts to registries (npm, PyPI, cargo, docker, GitHub releases, generic tarballs) following the validate, then dry-run, then build, then publish, then record-provenance pipeline. Invoked by ct-release-orchestrator as a sub-skill when a release has artifact config. Never stores credentials in output or manifest (ARTP-008), always dry-runs first (ARTP-002), halts and attempts rollback on failure (ARTP-009). Triggers when a release config has at least one enabled artifact handler."
 metadata:
-  version: 1.0.0
+  version: 1.0.2
   tier: on-demand
   install: harness
+  covers:
+    - packages/core/src/validation/protocols/cant/artifact-publish.cant
+    - packages/core/src/validation/protocols/protocols-markdown/artifact-publish.md
+  lastReviewed: 2026-09-28
   stability: stable
 ---
 
@@ -114,11 +118,10 @@ Missing credentials exit 90 (`E_PROVENANCE_CONFIG_INVALID` bubbled from provenan
 Validate the sub-protocol entry through `cleo check protocol`:
 
 ```bash
-cleo check protocol \
-  --protocolType artifact-publish \
-  --taskId T4901 \
-  --artifactType npm-package \
-  --buildPassed true
+cleo check protocol artifact-publish \
+  --task-id T4901 \
+  --artifact-type npm-package \
+  --build-passed true
 ```
 
 Exit code 0 = artifact published successfully. Exit code 85 = unknown artifact type. Exit code 86 = validation failed. Exit code 87 = build failed. Exit code 88 = publish failed, rollback attempted. Exit code 89 = rollback failed, dirty state.
@@ -148,4 +151,4 @@ This skill always hands off to ct-provenance-keeper after publish, before writin
 5. SHA-256 checksums are mandatory for every build output.
 6. Provenance MUST be recorded via `record_release()` after publish, via ct-provenance-keeper.
 7. On first publish failure, halt and attempt rollback; exit 88 on clean rollback, 89 on dirty.
-8. Validate every run via `cleo check protocol --protocolType artifact-publish`.
+8. Validate every run via `cleo check protocol artifact-publish`.

package/skills/ct-cleo/SKILL.md

@@ -2,9 +2,13 @@
 name: ct-cleo
 description: CLEO task management protocol - session, task, and workflow guidance. Use when managing tasks, sessions, or multi-agent workflows with the CLEO CLI protocol.
 metadata:
-  version: 2.21.0
+  version: 2.22.2
   tier: core
   install: harness
+  covers:
+    - packages/cleo/src/cli/commands/session.ts
+    - packages/cleo/src/cli/commands/focus.ts
+    - packages/cleo/src/cli/commands/sticky.ts
   lastReviewed: 2026-09-28
   stability: stable
 ---
@@ -225,6 +229,17 @@ This internal budget contract does not add a `--token-budget` flag to add/update
 
 ## Skill-Specific Extensions
 
+### Reference files
+
+| File | Load it when you |
+|------|------------------|
+| `references/session-protocol.md` | start, resume or end sessions; pick skills |
+| `references/orchestrator-constraints.md` | spawn subagents from an orchestrator |
+| `references/loom-lifecycle.md` | move an epic through the LOOM stages |
+| `references/anti-patterns.md` | check a plan against known mistakes |
+| `references/memory.md` | recall or record BRAIN memory (progressive disclosure) |
+| `references/sticky-notes.md` | capture a thought before it is a task: `cleo sticky jot "..."`, then `cleo sticky convert <id> --to-task` |
+
 - Task hierarchy, Saga commands, add-batch decomposition, docs policy, and evidence detail live in the on-demand reference; emit `task-creation`, `documents`, and `evidence` when needed.
 - For add-batch input, The top-level JSON MUST be an array of task objects, not an object wrapper like `{ "tasks": [...] }`.
 - Dry-run count semantics: `/data/count` and `/data/wouldCreate` predict writes; `/data/insertedCount` must be `0` for dry-run.
@@ -390,11 +405,12 @@ and planning document generation (T10634):
 
 Example — dry-run a scaffold before applying:
 ```bash
-# Validate scaffold payload
-cleo workgraph validate --file scaffold.json --dry-run
+# Validate scaffold payload (read-only)
+cleo workgraph validate scaffold.json
 
-# Apply validated scaffold atomically
-cleo workgraph apply --file scaffold.json
+# Preview, then apply the validated scaffold atomically
+cleo workgraph apply scaffold.json --dry-run
+cleo workgraph apply scaffold.json
 ```
 
 ## Task Context (PM-Core V2 — T10629/T10630/T10631)
@@ -428,11 +444,11 @@ cite decisions by durable BRAIN decision IDs.
 
 | Need | Command |
 |------|---------|
-| Store a decision | `cleo memory store --type decision --content "..." --title "..."` |
+| Store a decision | `cleo memory decision-store --decision "..." --rationale "..."` |
 | Search decisions | `cleo memory decision-find --query <term>` |
 | Find by type | `cleo memory find <term> --type decision` |
 | Fetch full record | `cleo memory fetch <decisionId>` |
-| List by epic | `cleo memory decision-find --epic <epicId>` |
+| Find by epic | `cleo memory decision-find "<epicId>"` (no epic filter — query text, then verify `source_table`/`source_rowid`) |
 | Check status | `cleo memory fetch <id>` → check `confirmation_state` field |
 
 **Why BRAIN decisions over markdown ledgers:**
@@ -443,7 +459,8 @@ cite decisions by durable BRAIN decision IDs.
 
 **Migration rule:** When you encounter a decision ONLY in a markdown ledger
 (`.cleo/adrs/`, `.cleo/agent-outputs/`), store it in the BRAIN with
-`cleo memory store --type decision` and cite the BRAIN ID going forward.
+`cleo memory decision-store --decision "..." --rationale "..."` and cite the
+BRAIN ID going forward.
 
 ## Evidence must prove task criteria
 

package/skills/ct-cleo/references/loom-lifecycle.md

@@ -107,7 +107,7 @@ Every spawn combines two layers:
 
 | ID | Rule | Enforcement |
 |----|------|-------------|
-| BASE-001 | MUST append ONE entry via `cleo manifest append <json>` (writes to pipeline_manifest table per ADR-027/T1093) | Required |
+| BASE-001 | MUST append ONE entry via `cleo manifest append --entry '<json>'` (writes to pipeline_manifest table per ADR-027/T1093) | Required |
 | BASE-002 | MUST NOT return content in response | Required |
 | BASE-003 | MUST complete task via `cleo complete` | Required |
 | BASE-004 | MUST write output file before manifest | Required |

package/skills/{ct-memory/SKILL.md → ct-cleo/references/memory.md}

@@ -1,21 +1,6 @@
----
-name: ct-memory
-version: 1.0.0
-description: Brain memory protocol with progressive disclosure for anti-hallucination and context recall
-triggers:
-  - memory
-  - brain
-  - recall
-  - remember
-  - anti-hallucination
-metadata:
-  version: 1.0.0
-  tier: internal
-  install: internal
-  stability: deprecated
----
-
-# ct-memory -- Brain Memory Protocol
+<!-- Merged from the ct-memory skill into ct-cleo (T12649, D11157). -->
+
+# Memory (BRAIN) — progressive recall
 
 ## Purpose
 
@@ -25,8 +10,10 @@ Ensures LLM agents never start conversations with amnesia. Provides structured m
 
 Use CLI (`cleo`) for all memory operations.
 
-1. The memory bridge (.cleo/memory-bridge.md) is already loaded via CLEO-INJECTION.md @-reference
-2. If the bridge content feels stale (>2 hours old), refresh:
+1. `cleo briefing` (or `cleo memory digest`) gives the live project memory summary.
+   The file bridge (`.cleo/memory-bridge.md`) is a legacy opt-in
+   (`brain.memoryBridge.mode = "file"`); do not assume it was loaded.
+2. For the task at hand, search:
    - `cleo memory find "session task decision" --limit 10`
 3. Check for anti-patterns to avoid:
    - `cleo memory find "mistake error avoid warning" --limit 5`
@@ -67,14 +54,14 @@ Before stating facts about the codebase or project:
 
 ### Cross-Project Knowledge (via NEXUS)
 
-- `cleo nexus search "pattern" --scope global`
-- Search across all CLEO-managed projects
+- `cleo nexus search "pattern"` (add `--project <id>` to narrow to one project)
+- Search the symbol graph across CLEO-managed projects
 
 ## Token Budget Guidelines
 
 | Operation | ~Tokens | When |
 |-----------|---------|------|
-| memory-bridge.md (auto-loaded) | 200-400 | Always (free) |
+| `cleo memory digest` | 200-400 | Session start |
 | `cleo memory find` | 50/hit | Discovery |
 | `cleo memory fetch` | 500/entry | Details |
 | `cleo memory timeline` | 200-500 | Context |

package/skills/ct-cleo/references/orchestrator-constraints.md

@@ -18,11 +18,11 @@
 ### CLI Spawn Operations
 
 ```bash
-cleo orchestrator start --epic T001
-cleo orchestrator analyze T001
-cleo orchestrator ready --epic T001
-cleo orchestrator next --epic T001
-cleo orchestrator spawn T002
+cleo orchestrate start T001
+cleo orchestrate analyze T001
+cleo orchestrate ready T001
+cleo orchestrate next T001
+cleo orchestrate spawn T002
 ```
 
 ### Spawn Workflow

package/skills/ct-cleo/references/session-protocol.md

@@ -97,8 +97,7 @@ Orchestrators resolve ALL tokens before spawning subagents. Subagents CANNOT res
 | `{{EPIC_ID}}` | Parent epic identifier |
 | `{{DATE}}` | Current date (ISO) |
 | `{{TOPIC_SLUG}}` | URL-safe topic name |
-| `{{OUTPUT_DIR}}` | Output directory |
-| `{{MANIFEST_PATH}}` | Manifest file path |
+| `{{OUTPUT_DIR}}` | Legacy output directory — record output with `cleo docs add` instead |
 | `{{TASK_TITLE}}` | Task title |
 | `{{TASK_DESCRIPTION}}` | Task description |
 
@@ -118,8 +117,8 @@ Skills are **context injections, NOT agents**. The orchestrator selects and inje
 ### Discovery
 
 ```bash
-cleo skill list
-cleo skill show ct-orchestrator
+cleo skills list
+cleo skills info ct-orchestrator
 ```
 
 ### Key Skills
@@ -145,12 +144,16 @@ cleo skill show ct-orchestrator
 
 ## Release Workflow
 
-**CRITICAL**: `release ship` only commits version metadata. All code changes MUST be committed BEFORE running `release ship`.
+Releases are PR-gated (ADR-065). Commit and merge all code through PRs first; the
+release verbs are `plan` → `open` → `reconcile`. The legacy `create`/`ship`
+verbs were removed (T9540, T10103).
 
 ```bash
-git add <files> && git commit -m "feat(T####): description"
-cleo release create v1.0.0
-cleo release ship v1.0.0 --bump-version --create-tag --push
+cleo release plan v2026.MM.N --epic T####     # or --tasks T1,T2
+cleo release open v2026.MM.N                  # dispatches release-prepare
+cleo release pr-status v2026.MM.N             # poll the release PR + CI
+git tag -a v2026.MM.N -m "Release v2026.MM.N" && git push origin v2026.MM.N
+cleo release reconcile v2026.MM.N             # backfill provenance
 ```
 
 ## Project Context

package/skills/{ct-stickynote/SKILL.md → ct-cleo/references/sticky-notes.md}

@@ -1,23 +1,6 @@
----
-name: ct-stickynote
-description: Quick ephemeral sticky notes for project-wide capture before formal classification
-version: 1.0.0
-category: productivity
-protocol: null
-tags: [sticky, notes, capture, quick, ephemeral]
-triggers: [note, sticky, jot, capture]
-compatibility: [claude-code, gemini-cli, codex-cli, opencode]
-dependencies: []
-sharedResources: []
-license: MIT
-metadata:
-  version: 1.0.0
-  tier: internal
-  install: internal
-  stability: deprecated
----
-
-# Sticky Notes Skill
+<!-- Merged from the ct-stickynote skill into ct-cleo (T12649, D11157). -->
+
+# Sticky notes — capture before you classify
 
 Quick capture ephemeral notes that fill the gap between session notes and formal tasks.
 
@@ -36,15 +19,10 @@ Use sticky notes for:
 | `sticky.add` | Create sticky | `cleo sticky add "Refactor auth middleware" --tag bug --color red` |
 | `sticky.list` | List active | `cleo sticky list --tag bug` |
 | `sticky.show` | Show details | `cleo sticky show SN-001` |
-| `sticky.convert` | Promote to task/memory | `cleo sticky convert SN-001 --to-task` |
+| `sticky.convert` | Promote to task/memory | `cleo sticky convert SN-001 --to-task --title "..."` or `--to-memory --type learning` |
 | `sticky.archive` | Archive | `cleo sticky archive SN-001` |
 
-## Installation
-
-```bash
-cleo skill install library:ct-stickynote
-```
-
-## Auto-Archive
 
-Stickies auto-archive after 30 days if not converted.
+Also: `cleo sticky jot "..."` (alias of add), `cleo sticky ls`, and
+`cleo sticky purge <id>` (permanent). Sticky notes are a core CLEO feature, so
+this guide ships inside ct-cleo rather than as a separate skill.