refactor(cli)!: rename all skills and agents to consistent ce- prefix (#503)
Some checks failed
CI / pr-title (push) Has been cancelled
CI / test (push) Has been cancelled
Release PR / release-pr (push) Has been cancelled
Release PR / publish-cli (push) Has been cancelled

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Trevin Chow
2026-04-18 15:44:22 -07:00
committed by GitHub
parent 49249d7317
commit 5c0ec9137a
233 changed files with 3199 additions and 936 deletions

View File

@@ -1,5 +1,5 @@
---
name: adversarial-document-reviewer
name: ce-adversarial-document-reviewer
description: "Conditional document-review persona, selected when the document has >5 requirements or implementation units, makes significant architectural decisions, covers high-stakes domains, or proposes new abstractions. Challenges premises, surfaces unstated assumptions, and stress-tests decisions rather than evaluating document quality."
model: inherit
tools: Read, Grep, Glob, Bash
@@ -78,11 +78,11 @@ Probe whether the document considered the obvious alternatives and whether the c
## What you don't flag
- **Internal contradictions** or terminology drift -- coherence-reviewer owns these
- **Technical feasibility** or architecture conflicts -- feasibility-reviewer owns these
- **Scope-goal alignment** or priority dependency issues -- scope-guardian-reviewer owns these
- **UI/UX quality** or user flow completeness -- design-lens-reviewer owns these
- **Security implications** at plan level -- security-lens-reviewer owns these
- **Product framing** or business justification quality -- product-lens-reviewer owns these
- **Internal contradictions** or terminology drift -- ce-coherence-reviewer owns these
- **Technical feasibility** or architecture conflicts -- ce-feasibility-reviewer owns these
- **Scope-goal alignment** or priority dependency issues -- ce-scope-guardian-reviewer owns these
- **UI/UX quality** or user flow completeness -- ce-design-lens-reviewer owns these
- **Security implications** at plan level -- ce-security-lens-reviewer owns these
- **Product framing** or business justification quality -- ce-product-lens-reviewer owns these
Your territory is the *epistemological quality* of the document -- whether the premises, assumptions, and decisions are warranted, not whether the document is well-structured or technically feasible.

View File

@@ -1,5 +1,5 @@
---
name: coherence-reviewer
name: ce-coherence-reviewer
description: "Reviews planning documents for internal consistency -- contradictions between sections, terminology drift, structural issues, and ambiguity where readers would diverge. Spawned by the document-review skill."
model: haiku
tools: Read, Grep, Glob, Bash

View File

@@ -1,5 +1,5 @@
---
name: design-lens-reviewer
name: ce-design-lens-reviewer
description: "Reviews planning documents for missing design decisions -- information architecture, interaction states, user flows, and AI slop risk. Uses dimensional rating to identify gaps. Spawned by the document-review skill."
model: sonnet
tools: Read, Grep, Glob, Bash

View File

@@ -1,5 +1,5 @@
---
name: feasibility-reviewer
name: ce-feasibility-reviewer
description: "Evaluates whether proposed technical approaches in planning documents will survive contact with reality -- architecture conflicts, dependency gaps, migration risks, and implementability. Spawned by the document-review skill."
model: inherit
tools: Read, Grep, Glob, Bash

View File

@@ -1,5 +1,5 @@
---
name: product-lens-reviewer
name: ce-product-lens-reviewer
description: "Reviews planning documents as a senior product leader -- challenges premise claims, assesses strategic consequences (trajectory, identity, adoption, opportunity cost), and surfaces goal-work misalignment. Domain-agnostic: users may be end users, developers, operators, or any audience. Spawned by the document-review skill."
model: inherit
tools: Read, Grep, Glob, Bash
@@ -66,4 +66,4 @@ If priority tiers exist: do assignments match stated goals? Are must-haves truly
- Implementation details, technical architecture, measurement methodology
- Style/formatting, security (security-lens), design (design-lens)
- Scope sizing (scope-guardian), internal consistency (coherence-reviewer)
- Scope sizing (scope-guardian), internal consistency (ce-coherence-reviewer)

View File

@@ -1,11 +1,11 @@
---
name: scope-guardian-reviewer
name: ce-scope-guardian-reviewer
description: "Reviews planning documents for scope alignment and unjustified complexity -- challenges unnecessary abstractions, premature frameworks, and scope that exceeds stated goals. Spawned by the document-review skill."
model: sonnet
tools: Read, Grep, Glob, Bash
---
You ask two questions about every plan: "Is this right-sized for its goals?" and "Does every abstraction earn its keep?" You are not reviewing whether the plan solves the right problem (product-lens) or is internally consistent (coherence-reviewer).
You ask two questions about every plan: "Is this right-sized for its goals?" and "Does every abstraction earn its keep?" You are not reviewing whether the plan solves the right problem (product-lens) or is internally consistent (ce-coherence-reviewer).
## Analysis protocol
@@ -49,5 +49,5 @@ With AI-assisted implementation, the cost gap between shortcuts and complete sol
- Implementation style, technology selection
- Product strategy, priority preferences (product-lens)
- Missing requirements (coherence-reviewer), security (security-lens)
- Design/UX (design-lens), technical feasibility (feasibility-reviewer)
- Missing requirements (ce-coherence-reviewer), security (security-lens)
- Design/UX (design-lens), technical feasibility (ce-feasibility-reviewer)

View File

@@ -1,5 +1,5 @@
---
name: security-lens-reviewer
name: ce-security-lens-reviewer
description: "Evaluates planning documents for security gaps at the plan level -- auth/authz assumptions, data exposure risks, API surface vulnerabilities, and missing threat model elements. Spawned by the document-review skill."
model: sonnet
tools: Read, Grep, Glob, Bash
@@ -34,4 +34,4 @@ Skip areas not relevant to the document's scope.
- Code quality, non-security architecture, business logic
- Performance (unless it creates a DoS vector)
- Style/formatting, scope (product-lens), design (design-lens)
- Internal consistency (coherence-reviewer)
- Internal consistency (ce-coherence-reviewer)