@cleocode/skills 2026.11.8 → 2026.11.9
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 +1 -1
- package/skills/_shared/__tests__/loom-adr-links.test.ts +12 -11
- package/skills/_shared/subagent-protocol-base.md +1 -1
- package/skills/ct-adr-recorder/SKILL.md +4 -4
- package/skills/ct-consensus-voter/SKILL.md +4 -4
- package/skills/ct-contribution/SKILL.md +5 -5
- package/skills/ct-epic-architect/SKILL.md +10 -8
- package/skills/ct-orchestrator/SKILL.md +12 -3
- package/skills/ct-release-orchestrator/SKILL.md +5 -5
- package/skills/ct-research-agent/SKILL.md +5 -5
- package/skills/ct-spec-writer/SKILL.md +5 -5
- package/skills/ct-task-executor/SKILL.md +5 -5
- package/skills/ct-validator/SKILL.md +5 -5
- package/skills/manifest.json +10 -10
package/package.json
CHANGED
|
@@ -5,7 +5,8 @@
|
|
|
5
5
|
* `packages/skills/skills/manifest.json`:
|
|
6
6
|
*
|
|
7
7
|
* 1. The skill entry declares a non-empty `adrRefs[]` array of ADR IDs.
|
|
8
|
-
* 2. Every ADR id in the array resolves to a real file under
|
|
8
|
+
* 2. Every ADR id in the array resolves to a real file under `docs/adr/`
|
|
9
|
+
* (the ADR mirror; `.cleo/adrs/` was retired in T14108).
|
|
9
10
|
*
|
|
10
11
|
* The mapping of (stage -> required adrRefs minimum) is the authoritative
|
|
11
12
|
* source-of-truth defined in `docs/reference/loom-coverage-matrix.md` under
|
|
@@ -26,7 +27,7 @@ import { describe, expect, it } from 'vitest';
|
|
|
26
27
|
|
|
27
28
|
const thisDir = dirname(fileURLToPath(import.meta.url));
|
|
28
29
|
const manifestPath = resolve(thisDir, '../../manifest.json');
|
|
29
|
-
const adrDir = resolve(thisDir, '
|
|
30
|
+
const adrDir = resolve(thisDir, '../../../../../docs/adr');
|
|
30
31
|
|
|
31
32
|
interface SkillEntry {
|
|
32
33
|
name: string;
|
|
@@ -76,15 +77,15 @@ const REQUIRED_ADR_REFS: Record<(typeof CANONICAL_LOOM_STAGES)[number], string[]
|
|
|
76
77
|
};
|
|
77
78
|
|
|
78
79
|
/**
|
|
79
|
-
* Build a set of ADR-id prefixes from
|
|
80
|
-
* with `ADR-NNN-...`; we extract
|
|
80
|
+
* Build a set of ADR-id prefixes from docs/adr/. Each filename starts
|
|
81
|
+
* with `adr-NNN-...` or `ADR-NNN-...`; we extract `ADR-NNN`.
|
|
81
82
|
*/
|
|
82
83
|
function loadAdrIdSet(): Set<string> {
|
|
83
84
|
const files = readdirSync(adrDir);
|
|
84
85
|
const ids = new Set<string>();
|
|
85
86
|
for (const file of files) {
|
|
86
|
-
const match = file.match(/^(
|
|
87
|
-
if (match) ids.add(match[1]);
|
|
87
|
+
const match = file.match(/^adr-(\d{3})-/i);
|
|
88
|
+
if (match) ids.add(`ADR-${match[1]}`);
|
|
88
89
|
}
|
|
89
90
|
return ids;
|
|
90
91
|
}
|
|
@@ -123,12 +124,12 @@ describe('LOOM ADR links — adrRefs[] declared on every LOOM-stage skill', () =
|
|
|
123
124
|
});
|
|
124
125
|
|
|
125
126
|
// ---------------------------------------------------------------------------
|
|
126
|
-
// Gate 2: every adrRef resolves to a real file under
|
|
127
|
+
// Gate 2: every adrRef resolves to a real file under docs/adr/
|
|
127
128
|
// ---------------------------------------------------------------------------
|
|
128
129
|
|
|
129
|
-
describe('LOOM ADR links — every adrRefs entry resolves to
|
|
130
|
-
it('
|
|
131
|
-
expect(existsSync(adrDir),
|
|
130
|
+
describe('LOOM ADR links — every adrRefs entry resolves to docs/adr/<id>-*.md', () => {
|
|
131
|
+
it('docs/adr/ exists and was loaded', () => {
|
|
132
|
+
expect(existsSync(adrDir), `docs/adr/ not found at ${adrDir}`).toBe(true);
|
|
132
133
|
expect(adrIds.size).toBeGreaterThan(0);
|
|
133
134
|
});
|
|
134
135
|
|
|
@@ -139,7 +140,7 @@ describe('LOOM ADR links — every adrRefs entry resolves to .cleo/adrs/<id>-*.m
|
|
|
139
140
|
it(`stage "${stage}" skill ${skill?.name} references real ADR file "${ref}"`, () => {
|
|
140
141
|
expect(
|
|
141
142
|
adrIds.has(ref),
|
|
142
|
-
`${ref} not found under
|
|
143
|
+
`${ref} not found under docs/adr/ — known prefixes: ${[...adrIds].sort().join(', ')}`,
|
|
143
144
|
).toBe(true);
|
|
144
145
|
});
|
|
145
146
|
}
|
|
@@ -97,7 +97,7 @@ See the reference above for:
|
|
|
97
97
|
|
|
98
98
|
## Task Lifecycle Integration (LOOM)
|
|
99
99
|
|
|
100
|
-
All work follows the **LOOM** (Logical Order of Operations Methodology) framework through the RCASD-IVTR+C pipeline stages. See `docs/
|
|
100
|
+
All work follows the **LOOM** (Logical Order of Operations Methodology) framework through the RCASD-IVTR+C pipeline stages. See `docs/reference/loom-coverage-matrix.md` for the stages and the skills that cover them.
|
|
101
101
|
|
|
102
102
|
Reference: @skills/_shared/task-system-integration.md
|
|
103
103
|
|
|
@@ -6,14 +6,14 @@ adrRefs:
|
|
|
6
6
|
- ADR-053
|
|
7
7
|
- ADR-070
|
|
8
8
|
metadata:
|
|
9
|
-
version: 1.0
|
|
9
|
+
version: 1.1.0
|
|
10
10
|
tier: on-demand
|
|
11
11
|
install: harness
|
|
12
12
|
covers:
|
|
13
13
|
- packages/core/src/validation/protocols/cant/architecture-decision.cant
|
|
14
14
|
- packages/core/src/validation/protocols/protocols-markdown/architecture-decision.md
|
|
15
15
|
loomStage: architecture_decision
|
|
16
|
-
lastReviewed: 2026-11-
|
|
16
|
+
lastReviewed: 2026-11-14
|
|
17
17
|
stability: stable
|
|
18
18
|
---
|
|
19
19
|
|
|
@@ -282,8 +282,8 @@ Exit code 0 = valid. Exit code 65 = `HANDOFF_REQUIRED`. Exit code 18 = `CASCADE_
|
|
|
282
282
|
|
|
283
283
|
This skill binds to the **architecture_decision** LOOM lifecycle stage (underscored canonical form — `cleo lifecycle` source of truth). Governing ADRs:
|
|
284
284
|
|
|
285
|
-
- [ADR-053 — playbook runtime](
|
|
286
|
-
- [ADR-070 — three-tier orchestration](
|
|
285
|
+
- [ADR-053 — playbook runtime](../../../../docs/adr/adr-053-playbook-runtime.md) — defines the lifecycle state machine; the ADR stage is one of its 10 nodes.
|
|
286
|
+
- [ADR-070 — three-tier orchestration](../../../../docs/adr/adr-070-three-tier-orchestration.md) — defines the Orchestrator HITL gate that owns the `proposed → accepted` ADR transition.
|
|
287
287
|
|
|
288
288
|
### Naming Note (T9672)
|
|
289
289
|
|
|
@@ -6,14 +6,14 @@ adrRefs:
|
|
|
6
6
|
- ADR-015
|
|
7
7
|
- ADR-023
|
|
8
8
|
metadata:
|
|
9
|
-
version: 1.0
|
|
9
|
+
version: 1.1.0
|
|
10
10
|
tier: on-demand
|
|
11
11
|
install: harness
|
|
12
12
|
covers:
|
|
13
13
|
- packages/core/src/validation/protocols/cant/consensus.cant
|
|
14
14
|
- packages/core/src/validation/protocols/protocols-markdown/consensus.md
|
|
15
15
|
loomStage: consensus
|
|
16
|
-
lastReviewed: 2026-11-
|
|
16
|
+
lastReviewed: 2026-11-14
|
|
17
17
|
stability: stable
|
|
18
18
|
---
|
|
19
19
|
|
|
@@ -174,7 +174,7 @@ This skill typically hands off to ct-adr-recorder on a `PROVEN` verdict so the d
|
|
|
174
174
|
|
|
175
175
|
This skill binds to the **consensus** LOOM lifecycle stage. Governing ADRs:
|
|
176
176
|
|
|
177
|
-
- [ADR-015 — multi-contributor architecture](
|
|
178
|
-
- [ADR-023 — protocol validation dispatch](
|
|
177
|
+
- [ADR-015 — multi-contributor architecture](../../../../docs/adr/adr-015-multi-contributor-architecture.md) — defines the consensus framework that this skill implements.
|
|
178
|
+
- [ADR-023 — protocol validation dispatch](../../../../docs/adr/adr-023-protocol-validation-dispatch.md) — defines how consensus output is validated before downstream stages consume it.
|
|
179
179
|
|
|
180
180
|
LOOM coverage matrix: [docs/reference/loom-coverage-matrix.md](../../../../docs/reference/loom-coverage-matrix.md).
|
|
@@ -6,7 +6,7 @@ description: >-
|
|
|
6
6
|
"consensus workflow", "multi-agent decision", "create contribution",
|
|
7
7
|
"contribution start", "contribution submit", "detect conflicts",
|
|
8
8
|
"weighted consensus", "decision tracking", "conflict resolution".
|
|
9
|
-
version: 1.0
|
|
9
|
+
version: 1.1.0
|
|
10
10
|
protocol: contribution
|
|
11
11
|
adrRefs:
|
|
12
12
|
- ADR-015
|
|
@@ -21,14 +21,14 @@ compatibility:
|
|
|
21
21
|
- gemini-cli
|
|
22
22
|
license: MIT
|
|
23
23
|
metadata:
|
|
24
|
-
version: 1.0
|
|
24
|
+
version: 1.1.0
|
|
25
25
|
tier: on-demand
|
|
26
26
|
install: harness
|
|
27
27
|
covers:
|
|
28
28
|
- packages/core/src/validation/protocols/cant/contribution.cant
|
|
29
29
|
- packages/core/src/validation/protocols/protocols-markdown/contribution.md
|
|
30
30
|
loomStage: contribution
|
|
31
|
-
lastReviewed: 2026-11-
|
|
31
|
+
lastReviewed: 2026-11-14
|
|
32
32
|
stability: stable
|
|
33
33
|
---
|
|
34
34
|
|
|
@@ -601,7 +601,7 @@ Until that ADR lands, contribution gates derive from ADR-015 (multi-contributor
|
|
|
601
601
|
|
|
602
602
|
This skill binds to the **contribution** LOOM lifecycle stage (the final stage of the RCASD-IVTR+C pipeline). Governing ADRs:
|
|
603
603
|
|
|
604
|
-
- [ADR-015 — multi-contributor architecture](
|
|
605
|
-
- [ADR-053 — playbook runtime](
|
|
604
|
+
- [ADR-015 — multi-contributor architecture](../../../../docs/adr/adr-015-multi-contributor-architecture.md) — defines the multi-contributor consensus mechanics that this stage formalizes for an Epic's downstream return path.
|
|
605
|
+
- [ADR-053 — playbook runtime](../../../../docs/adr/adr-053-playbook-runtime.md) — defines the lifecycle state machine; contribution is its terminal node.
|
|
606
606
|
|
|
607
607
|
LOOM coverage matrix: [docs/reference/loom-coverage-matrix.md](../../../../docs/reference/loom-coverage-matrix.md).
|
|
@@ -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
|
|
4
|
+
version: 3.2.0
|
|
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
|
|
20
|
+
version: 3.2.0
|
|
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-11-
|
|
27
|
+
lastReviewed: 2026-11-14
|
|
28
28
|
stability: stable
|
|
29
29
|
---
|
|
30
30
|
|
|
@@ -94,7 +94,7 @@ Epic (type: epic, size: large)
|
|
|
94
94
|
|
|
95
95
|
### Tier Sizing & Scope (canonical source: ADR-073 §1.1)
|
|
96
96
|
|
|
97
|
-
**DO NOT redefine here.** The strict definitions live in
|
|
97
|
+
**DO NOT redefine here.** The strict definitions live in `docs/adr/adr-073-above-epic-naming.md`
|
|
98
98
|
§1.1 (tier table) + §1.2 (8 invariants I1–I8) + §1.3 (lifecycle decision table).
|
|
99
99
|
|
|
100
100
|
Quick reference for decomposition:
|
|
@@ -209,10 +209,12 @@ cleo update T001 --files "additional-context.md"
|
|
|
209
209
|
| Constraint | Value | Enforcement |
|
|
210
210
|
|------------|-------|-------------|
|
|
211
211
|
| Max depth | 3 | epic (0) → task (1) → subtask (2) |
|
|
212
|
-
| Max active siblings |
|
|
213
|
-
| Max siblings |
|
|
212
|
+
| Max active siblings | 0 (unlimited); `human-cognitive`: 3 | `hierarchy.maxActiveSiblings` |
|
|
213
|
+
| Max siblings | 0 (unlimited); `human-cognitive`: 7 | `hierarchy.maxSiblings` |
|
|
214
214
|
| Parent must exist | Validated | `cleo exists {{PARENT_ID}}` |
|
|
215
215
|
|
|
216
|
+
No profile selects `llm-agent-first` (both sibling caps unlimited). Explicit project caps override the profile, including `0` to disable either limit.
|
|
217
|
+
|
|
216
218
|
**Validation Before Creation:**
|
|
217
219
|
|
|
218
220
|
```bash
|
|
@@ -348,7 +350,7 @@ Recommendation: [Your recommendation]
|
|
|
348
350
|
|
|
349
351
|
This skill binds to the **decomposition** LOOM lifecycle stage. Governing ADRs:
|
|
350
352
|
|
|
351
|
-
- [ADR-066 — task taxonomy consolidation](
|
|
352
|
-
- [ADR-073 — above-epic naming](
|
|
353
|
+
- [ADR-066 — task taxonomy consolidation](../../../../docs/adr/adr-066-task-taxonomy-consolidation.md) — defines the Type/Kind/Severity axes the decomposer must populate on every leaf task.
|
|
354
|
+
- [ADR-073 — above-epic naming](../../../../docs/adr/adr-073-above-epic-naming.md) — defines the Saga/Epic/Task/Subtask hierarchy that decomposition produces.
|
|
353
355
|
|
|
354
356
|
LOOM coverage matrix: [docs/reference/loom-coverage-matrix.md](../../../../docs/reference/loom-coverage-matrix.md).
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: ct-orchestrator
|
|
3
3
|
description: "Pipeline-aware orchestration skill for managing complex workflows through subagent delegation. Use when the user asks to \"orchestrate\", \"orchestrator mode\", \"run as orchestrator\", \"delegate to subagents\", \"coordinate agents\", \"spawn subagents\", \"multi-agent workflow\", \"context-protected workflow\", \"agent farm\", \"HITL orchestration\", \"pipeline management\", or needs to manage complex workflows by delegating work to subagents while protecting the main context window. Enforces ORC-001 through ORC-009 constraints. Provider-neutral — works with any AI agent runtime."
|
|
4
4
|
metadata:
|
|
5
|
-
version: 4.
|
|
5
|
+
version: 4.23.0
|
|
6
6
|
tier: core
|
|
7
7
|
install: harness
|
|
8
8
|
covers:
|
|
@@ -10,7 +10,7 @@ metadata:
|
|
|
10
10
|
- packages/core/src/orchestration/spawn-prompt.ts
|
|
11
11
|
- packages/core/src/orchestrate/orca-routing.ts
|
|
12
12
|
- packages/core/src/orchestrate/spawn-ops.ts
|
|
13
|
-
lastReviewed: 2026-11-
|
|
13
|
+
lastReviewed: 2026-11-14
|
|
14
14
|
stability: stable
|
|
15
15
|
---
|
|
16
16
|
|
|
@@ -157,7 +157,7 @@ its own PR it MUST be a Task, not a Subtask.
|
|
|
157
157
|
- Epic spans >1 release → regroup under a Saga
|
|
158
158
|
|
|
159
159
|
Full charter (8 invariants I1–I8 + prefix registry) lives in
|
|
160
|
-
|
|
160
|
+
`docs/adr/adr-073-above-epic-naming.md` §1–§2.
|
|
161
161
|
|
|
162
162
|
## The Work Loop
|
|
163
163
|
|
|
@@ -378,6 +378,15 @@ mailbox in it. Tier-0 prompts stay minimal and have no such section; with
|
|
|
378
378
|
and asking for a report of at most 100 words (conclusion, blocker, proof) (T14429). The conduit messaging verbs, including the `conduit-*` sub-commands of
|
|
379
379
|
orchestrate, were removed (T13955).
|
|
380
380
|
|
|
381
|
+
`--lead-mbx` can name the held owner-designated project mailbox or an epic
|
|
382
|
+
coordinator mailbox; the destination does not change AgentMBX's owner designation.
|
|
383
|
+
Spawn verifies the registered holder and its exact provider session through the
|
|
384
|
+
read-only CLI, including identities held by MCP. Atomicity-only prechecks do not
|
|
385
|
+
resolve mailboxes. An unverified destination reports the failed CLI check and
|
|
386
|
+
recovery command: register a missing identity through `mbx_identity` (which also
|
|
387
|
+
holds it), or claim an existing available identity in the lead's provider session.
|
|
388
|
+
Never claim, release or send as another session's live holder to verify it.
|
|
389
|
+
|
|
381
390
|
Spawn adapter discovery uses the installed `@cleocode/adapters` package, including in
|
|
382
391
|
projects without `packages/`. Session adapter activation still discovers only
|
|
383
392
|
explicit project adapters, so session start does not install bundled provider hooks. Both `orchestrate lead` and `orchestrate spawn-execute`
|
|
@@ -7,7 +7,7 @@ adrRefs:
|
|
|
7
7
|
- ADR-063
|
|
8
8
|
- ADR-065
|
|
9
9
|
metadata:
|
|
10
|
-
version: 3.
|
|
10
|
+
version: 3.9.0
|
|
11
11
|
tier: on-demand
|
|
12
12
|
install: harness
|
|
13
13
|
covers:
|
|
@@ -17,7 +17,7 @@ metadata:
|
|
|
17
17
|
- packages/core/src/release/cut.ts
|
|
18
18
|
- packages/core/src/release/authorization.ts
|
|
19
19
|
loomStage: release
|
|
20
|
-
lastReviewed: 2026-11-
|
|
20
|
+
lastReviewed: 2026-11-14
|
|
21
21
|
stability: stable
|
|
22
22
|
---
|
|
23
23
|
|
|
@@ -215,9 +215,9 @@ Consult the inventory whenever:
|
|
|
215
215
|
|
|
216
216
|
This skill binds to the **release** LOOM lifecycle stage. Governing ADRs:
|
|
217
217
|
|
|
218
|
-
- [ADR-053 — project-agnostic release pipeline](
|
|
219
|
-
- [ADR-063 — release pipeline](
|
|
220
|
-
- [ADR-065 — PR-required release flow](
|
|
218
|
+
- [ADR-053 — project-agnostic release pipeline](../../../../docs/adr/adr-053-project-agnostic-release-pipeline.md) — language-agnostic version bump → changelog → tag flow.
|
|
219
|
+
- [ADR-063 — release pipeline](../../../../docs/adr/adr-063-release-pipeline.md) — original 12-step pipeline (historical; superseded by SPEC-T9345 §4).
|
|
220
|
+
- [ADR-065 — PR-required release flow](../../../../docs/adr/adr-065-pr-required-release-flow.md) — direct pushes to `main` are prohibited.
|
|
221
221
|
|
|
222
222
|
Live verb matrix: [docs/reference/verb-matrix.md](../../../../docs/reference/verb-matrix.md) — the single source of truth for verb-to-state mapping.
|
|
223
223
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: ct-research-agent
|
|
3
3
|
description: Multi-source research and investigation combining web search, documentation lookup via Context7, and codebase analysis. Synthesizes findings into actionable recommendations with proper citation and task traceability. Use when conducting research, investigating best practices, gathering technical information, or analyzing existing implementations. Triggers on research tasks, investigation needs, or information discovery requests.
|
|
4
|
-
version: 2.0
|
|
4
|
+
version: 2.1.0
|
|
5
5
|
protocol: research
|
|
6
6
|
adrRefs:
|
|
7
7
|
- ADR-023
|
|
@@ -17,14 +17,14 @@ compatibility:
|
|
|
17
17
|
- gemini-cli
|
|
18
18
|
license: MIT
|
|
19
19
|
metadata:
|
|
20
|
-
version: 2.0
|
|
20
|
+
version: 2.1.0
|
|
21
21
|
tier: on-demand
|
|
22
22
|
install: harness
|
|
23
23
|
covers:
|
|
24
24
|
- packages/core/src/validation/protocols/cant/research.cant
|
|
25
25
|
- packages/core/src/validation/protocols/protocols-markdown/research.md
|
|
26
26
|
loomStage: research
|
|
27
|
-
lastReviewed: 2026-11-
|
|
27
|
+
lastReviewed: 2026-11-14
|
|
28
28
|
stability: stable
|
|
29
29
|
---
|
|
30
30
|
|
|
@@ -241,8 +241,8 @@ If research cannot proceed (access denied, topic too broad, etc.):
|
|
|
241
241
|
|
|
242
242
|
This skill binds to the **research** LOOM lifecycle stage. Governing ADRs:
|
|
243
243
|
|
|
244
|
-
- [ADR-023 — protocol validation dispatch](
|
|
245
|
-
- [ADR-070 — three-tier orchestration](
|
|
244
|
+
- [ADR-023 — protocol validation dispatch](../../../../docs/adr/adr-023-protocol-validation-dispatch.md) — defines how research output is validated before downstream stages consume it.
|
|
245
|
+
- [ADR-070 — three-tier orchestration](../../../../docs/adr/adr-070-three-tier-orchestration.md) — defines the Orchestrator → Phase Lead → Worker tiers; research runs as a leaf Worker.
|
|
246
246
|
|
|
247
247
|
LOOM coverage matrix: [docs/reference/loom-coverage-matrix.md](../../../../docs/reference/loom-coverage-matrix.md).
|
|
248
248
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: ct-spec-writer
|
|
3
3
|
description: Technical specification writing using RFC 2119 language for clear, unambiguous requirements. Creates protocol specifications, technical requirements, API specifications, and architecture documents with testable requirements and compliance criteria. Use when writing specifications, defining protocols, documenting requirements, or creating API contracts. Triggers on specification tasks, protocol definition needs, or requirement documentation.
|
|
4
|
-
version: 2.
|
|
4
|
+
version: 2.2.0
|
|
5
5
|
protocol: specification
|
|
6
6
|
adrRefs:
|
|
7
7
|
- ADR-014
|
|
@@ -17,14 +17,14 @@ compatibility:
|
|
|
17
17
|
- gemini-cli
|
|
18
18
|
license: MIT
|
|
19
19
|
metadata:
|
|
20
|
-
version: 2.
|
|
20
|
+
version: 2.2.0
|
|
21
21
|
tier: on-demand
|
|
22
22
|
install: harness
|
|
23
23
|
covers:
|
|
24
24
|
- packages/core/src/validation/protocols/cant/specification.cant
|
|
25
25
|
- packages/core/src/validation/protocols/protocols-markdown/specification.md
|
|
26
26
|
loomStage: specification
|
|
27
|
-
lastReviewed: 2026-11-
|
|
27
|
+
lastReviewed: 2026-11-14
|
|
28
28
|
stability: stable
|
|
29
29
|
---
|
|
30
30
|
|
|
@@ -274,8 +274,8 @@ Spec blobs live in the docs SSoT; published copies on disk go in
|
|
|
274
274
|
|
|
275
275
|
This skill binds to the **specification** LOOM lifecycle stage. Governing ADRs:
|
|
276
276
|
|
|
277
|
-
- [ADR-014 — RCASD rename and protocol validation](
|
|
278
|
-
- [ADR-023 — protocol validation dispatch](
|
|
277
|
+
- [ADR-014 — RCASD rename and protocol validation](../../../../docs/adr/adr-014-rcasd-rename-and-protocol-validation.md) — defines the specification stage's role inside the RCASD-IVTR+C lifecycle.
|
|
278
|
+
- [ADR-023 — protocol validation dispatch](../../../../docs/adr/adr-023-protocol-validation-dispatch.md) — defines how specifications are validated before decomposition.
|
|
279
279
|
|
|
280
280
|
LOOM coverage matrix: [docs/reference/loom-coverage-matrix.md](../../../../docs/reference/loom-coverage-matrix.md).
|
|
281
281
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: ct-task-executor
|
|
3
3
|
description: General implementation task execution for completing assigned CLEO tasks by following instructions and producing concrete deliverables. Handles coding, configuration, documentation work with quality verification against acceptance criteria and progress reporting. Use when executing implementation tasks, completing assigned work, or producing task deliverables. Triggers on implementation tasks, general execution needs, or task completion work.
|
|
4
|
-
version: 2.
|
|
4
|
+
version: 2.14.0
|
|
5
5
|
protocol: implementation
|
|
6
6
|
adrRefs:
|
|
7
7
|
- ADR-070
|
|
@@ -17,7 +17,7 @@ compatibility:
|
|
|
17
17
|
- gemini-cli
|
|
18
18
|
license: MIT
|
|
19
19
|
metadata:
|
|
20
|
-
version: 2.
|
|
20
|
+
version: 2.14.0
|
|
21
21
|
tier: core
|
|
22
22
|
install: harness
|
|
23
23
|
covers:
|
|
@@ -29,7 +29,7 @@ metadata:
|
|
|
29
29
|
- packages/core/src/validation/protocols/cant/implementation.cant
|
|
30
30
|
- packages/core/src/validation/protocols/protocols-markdown/implementation.md
|
|
31
31
|
loomStage: implementation
|
|
32
|
-
lastReviewed: 2026-11-
|
|
32
|
+
lastReviewed: 2026-11-14
|
|
33
33
|
stability: stable
|
|
34
34
|
---
|
|
35
35
|
|
|
@@ -437,8 +437,8 @@ cleo session gc --max-age 1
|
|
|
437
437
|
|
|
438
438
|
This skill binds to the **implementation** LOOM lifecycle stage. Governing ADRs:
|
|
439
439
|
|
|
440
|
-
- [ADR-070 — three-tier orchestration](
|
|
441
|
-
- [ADR-062 — worktree merge, not cherry-pick](
|
|
440
|
+
- [ADR-070 — three-tier orchestration](../../../../docs/adr/adr-070-three-tier-orchestration.md) — defines the Worker tier that ct-task-executor occupies.
|
|
441
|
+
- [ADR-062 — worktree merge, not cherry-pick](../../../../docs/adr/adr-062-worktree-merge-not-cherry-pick.md) — defines the integration path that preserves the executor's commit SHAs end-to-end.
|
|
442
442
|
|
|
443
443
|
LOOM coverage matrix: [docs/reference/loom-coverage-matrix.md](../../../../docs/reference/loom-coverage-matrix.md).
|
|
444
444
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: ct-validator
|
|
3
3
|
description: Compliance validation for verifying systems, documents, or code against requirements, schemas, or standards. Performs schema validation, code compliance checks, document validation, and protocol compliance verification with detailed pass/fail reporting. Use when validating compliance, checking schemas, verifying code standards, or auditing protocol implementations. Triggers on validation tasks, compliance checks, or quality verification needs.
|
|
4
|
-
version: 2.
|
|
4
|
+
version: 2.2.0
|
|
5
5
|
protocol: validation
|
|
6
6
|
adrRefs:
|
|
7
7
|
- ADR-051
|
|
@@ -18,7 +18,7 @@ compatibility:
|
|
|
18
18
|
- gemini-cli
|
|
19
19
|
license: MIT
|
|
20
20
|
metadata:
|
|
21
|
-
version: 2.
|
|
21
|
+
version: 2.2.0
|
|
22
22
|
tier: on-demand
|
|
23
23
|
install: harness
|
|
24
24
|
covers:
|
|
@@ -27,7 +27,7 @@ metadata:
|
|
|
27
27
|
- packages/core/src/validation/protocols/cant/testing.cant
|
|
28
28
|
- packages/core/src/validation/protocols/protocols-markdown/testing.md
|
|
29
29
|
loomStage: validation
|
|
30
|
-
lastReviewed: 2026-11-
|
|
30
|
+
lastReviewed: 2026-11-14
|
|
31
31
|
stability: stable
|
|
32
32
|
---
|
|
33
33
|
|
|
@@ -301,8 +301,8 @@ When invoked by orchestrator, expect these context tokens:
|
|
|
301
301
|
|
|
302
302
|
This skill binds to the **validation** LOOM lifecycle stage. Governing ADRs:
|
|
303
303
|
|
|
304
|
-
- [ADR-051 — programmatic gate integrity](
|
|
305
|
-
- [ADR-023 — protocol validation dispatch](
|
|
304
|
+
- [ADR-051 — programmatic gate integrity](../../../../docs/adr/adr-051-programmatic-gate-integrity.md) — defines the evidence-atom grammar that the validator emits and re-validates.
|
|
305
|
+
- [ADR-023 — protocol validation dispatch](../../../../docs/adr/adr-023-protocol-validation-dispatch.md) — defines the protocol-validation routing layer that dispatches to this skill.
|
|
306
306
|
|
|
307
307
|
LOOM coverage matrix: [docs/reference/loom-coverage-matrix.md](../../../../docs/reference/loom-coverage-matrix.md).
|
|
308
308
|
|
package/skills/manifest.json
CHANGED
|
@@ -73,7 +73,7 @@
|
|
|
73
73
|
"skills": [
|
|
74
74
|
{
|
|
75
75
|
"name": "ct-adr-recorder",
|
|
76
|
-
"version": "1.0
|
|
76
|
+
"version": "1.1.0",
|
|
77
77
|
"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.",
|
|
78
78
|
"path": "skills/ct-adr-recorder",
|
|
79
79
|
"tier": 1,
|
|
@@ -326,7 +326,7 @@
|
|
|
326
326
|
},
|
|
327
327
|
{
|
|
328
328
|
"name": "ct-consensus-voter",
|
|
329
|
-
"version": "1.0
|
|
329
|
+
"version": "1.1.0",
|
|
330
330
|
"description": "Runs structured multi-agent voting for decision tasks with confidence scores, conflict detection, and HITL escalation when the threshold is not met. Use when two or more agents must vote on options: architecture choices, tool selection, policy decisions, when a task carries agent_type:analysis, or on phrases like 'reach consensus', 'vote on options', 'resolve the debate', 'pick the best approach'. Produces a voting matrix JSON, enforces the 0.5 threshold, flags ties within 0.1 confidence as contested and escalates to human tiebreak.",
|
|
331
331
|
"path": "skills/ct-consensus-voter",
|
|
332
332
|
"tier": 1,
|
|
@@ -404,7 +404,7 @@
|
|
|
404
404
|
},
|
|
405
405
|
{
|
|
406
406
|
"name": "ct-contribution",
|
|
407
|
-
"version": "1.0
|
|
407
|
+
"version": "1.1.0",
|
|
408
408
|
"description": "Guided workflow for multi-agent consensus contributions. Use when user says \"/contribution\", \"contribution protocol\", \"submit contribution\", \"consensus workflow\", \"multi-agent decision\", \"create contribution\", \"contribution start\", \"contribution submit\", \"detect conflicts\", \"weighted consensus\", \"decision tracking\", \"conflict resolution\".",
|
|
409
409
|
"path": "skills/ct-contribution",
|
|
410
410
|
"tier": 1,
|
|
@@ -729,7 +729,7 @@
|
|
|
729
729
|
},
|
|
730
730
|
{
|
|
731
731
|
"name": "ct-epic-architect",
|
|
732
|
-
"version": "3.0
|
|
732
|
+
"version": "3.2.0",
|
|
733
733
|
"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.",
|
|
734
734
|
"path": "skills/ct-epic-architect",
|
|
735
735
|
"tier": 1,
|
|
@@ -922,7 +922,7 @@
|
|
|
922
922
|
},
|
|
923
923
|
{
|
|
924
924
|
"name": "ct-orchestrator",
|
|
925
|
-
"version": "4.
|
|
925
|
+
"version": "4.23.0",
|
|
926
926
|
"description": "Pipeline-aware orchestration skill for managing complex workflows through subagent delegation. Use when the user asks to \\\"orchestrate\\\", \\\"orchestrator mode\\\", \\\"run as orchestrator\\\", \\\"delegate to subagents\\\", \\\"coordinate agents\\\", \\\"spawn subagents\\\", \\\"multi-agent workflow\\\", \\\"context-protected workflow\\\", \\\"agent farm\\\", \\\"HITL orchestration\\\", \\\"pipeline management\\\", or needs to manage complex workflows by delegating work to subagents while protecting the main context window. Enforces ORC-001 through ORC-009 constraints. Provider-neutral — works with any AI agent runtime.",
|
|
927
927
|
"path": "skills/ct-orchestrator",
|
|
928
928
|
"tier": 0,
|
|
@@ -1088,7 +1088,7 @@
|
|
|
1088
1088
|
},
|
|
1089
1089
|
{
|
|
1090
1090
|
"name": "ct-release-orchestrator",
|
|
1091
|
-
"version": "3.
|
|
1091
|
+
"version": "3.9.0",
|
|
1092
1092
|
"description": "Orchestrates CLEO releases. Default (T14102): cleo release cut {version} tags the newest main commit with green CI, and release.yml writes the CHANGELOG from changesets, publishes, and opens an auto-merging CHANGELOG + version PR; cleo release reconcile records provenance. The SPEC-T9345 4-verb pipeline (cleo release plan, cleo release open, PR + tag) stays one release as a fallback (T14114). The deprecated cleo release ship monolith was deleted in T10103 — do not invoke it. Use ship-e2e-smoke to validate the full pipeline end-to-end (dry-run by default). The full verb-to-state map is in docs/reference/verb-matrix.md. Use when shipping a new version, validating the release pipeline end-to-end, or promoting a completed epic to released status.",
|
|
1093
1093
|
"path": "skills/ct-release-orchestrator",
|
|
1094
1094
|
"tier": 1,
|
|
@@ -1170,7 +1170,7 @@
|
|
|
1170
1170
|
},
|
|
1171
1171
|
{
|
|
1172
1172
|
"name": "ct-research-agent",
|
|
1173
|
-
"version": "2.0
|
|
1173
|
+
"version": "2.1.0",
|
|
1174
1174
|
"description": "Multi-source research and investigation combining web search, documentation lookup via Context7, and codebase analysis. Synthesizes findings into actionable recommendations with proper citation and task traceability. Use when conducting research, investigating best practices, gathering technical information, or analyzing existing implementations. Triggers on research tasks, investigation needs, or information discovery requests.",
|
|
1175
1175
|
"path": "skills/ct-research-agent",
|
|
1176
1176
|
"tier": 1,
|
|
@@ -1325,7 +1325,7 @@
|
|
|
1325
1325
|
},
|
|
1326
1326
|
{
|
|
1327
1327
|
"name": "ct-spec-writer",
|
|
1328
|
-
"version": "2.
|
|
1328
|
+
"version": "2.2.0",
|
|
1329
1329
|
"description": "Technical specification writing using RFC 2119 language for clear, unambiguous requirements. Creates protocol specifications, technical requirements, API specifications, and architecture documents with testable requirements and compliance criteria. Use when writing specifications, defining protocols, documenting requirements, or creating API contracts. Triggers on specification tasks, protocol definition needs, or requirement documentation.",
|
|
1330
1330
|
"path": "skills/ct-spec-writer",
|
|
1331
1331
|
"tier": 1,
|
|
@@ -1410,7 +1410,7 @@
|
|
|
1410
1410
|
},
|
|
1411
1411
|
{
|
|
1412
1412
|
"name": "ct-task-executor",
|
|
1413
|
-
"version": "2.
|
|
1413
|
+
"version": "2.14.0",
|
|
1414
1414
|
"description": "General implementation task execution for completing assigned CLEO tasks by following instructions and producing concrete deliverables. Handles coding, configuration, documentation work with quality verification against acceptance criteria and progress reporting. Use when executing implementation tasks, completing assigned work, or producing task deliverables. Triggers on implementation tasks, general execution needs, or task completion work.",
|
|
1415
1415
|
"path": "skills/ct-task-executor",
|
|
1416
1416
|
"tier": 0,
|
|
@@ -1498,7 +1498,7 @@
|
|
|
1498
1498
|
},
|
|
1499
1499
|
{
|
|
1500
1500
|
"name": "ct-validator",
|
|
1501
|
-
"version": "2.
|
|
1501
|
+
"version": "2.2.0",
|
|
1502
1502
|
"description": "Compliance validation for verifying systems, documents, or code against requirements, schemas, or standards. Performs schema validation, code compliance checks, document validation, and protocol compliance verification with detailed pass/fail reporting. Use when validating compliance, checking schemas, verifying code standards, or auditing protocol implementations. Triggers on validation tasks, compliance checks, or quality verification needs.",
|
|
1503
1503
|
"path": "skills/ct-validator",
|
|
1504
1504
|
"tier": 1,
|