refactor(cli)!: rename all skills and agents to consistent ce- prefix (#503)
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Trevin Chow
@@ -1,9 +1,9 @@
|
||||
---
|
||||
name: ce:compound
|
||||
name: ce-compound
|
||||
description: Document a recently solved problem to compound your team's knowledge
|
||||
---
|
||||
|
||||
# /compound
|
||||
# /ce-compound
|
||||
|
||||
Coordinate multiple subagents working in parallel to document a recently solved problem.
|
||||
|
||||
@@ -16,8 +16,8 @@ Captures problem solutions while context is fresh, creating structured documenta
|
||||
## Usage
|
||||
|
||||
```bash
|
||||
/ce:compound # Document the most recent fix
|
||||
/ce:compound [brief context] # Provide additional context hint
|
||||
/ce-compound # Document the most recent fix
|
||||
/ce-compound [brief context] # Provide additional context hint
|
||||
```
|
||||
|
||||
## Support Files
|
||||
@@ -94,7 +94,7 @@ Launch research subagents. Each returns text data to the orchestrator.
|
||||
|
||||
**Dispatch order:**
|
||||
- Launch `Context Analyzer`, `Solution Extractor`, and `Related Docs Finder` in parallel (background)
|
||||
- Then dispatch `session-historian` in foreground — it reads session files outside the working directory that background agents may not have access to
|
||||
- Then dispatch `ce-session-historian` in foreground — it reads session files outside the working directory that background agents may not have access to
|
||||
- The foreground dispatch runs while the background agents work, adding no wall-clock time
|
||||
|
||||
<parallel_tasks>
|
||||
@@ -168,7 +168,7 @@ Launch research subagents. Each returns text data to the orchestrator.
|
||||
|
||||
#### 4. **Session Historian** (foreground, after launching the above — only if the user opted in)
|
||||
- **Skip entirely** if the user declined session history in the follow-up question
|
||||
- Dispatched as `compound-engineering:research:session-historian`
|
||||
- Dispatched as `research:ce-session-historian`
|
||||
- Dispatch in **foreground** — this agent reads session files outside the working directory (`~/.claude/projects/`, `~/.codex/sessions/`, `~/.cursor/projects/`) which background agents may not have access to
|
||||
- Searches prior Claude Code, Codex, and Cursor sessions for the same project to find related investigation context
|
||||
- Correlates sessions by repo name across all platforms (matches sessions from main checkouts, worktrees, and Conductor workspaces)
|
||||
@@ -228,9 +228,9 @@ When creating a new doc, preserve the section order from `assets/resolution-temp
|
||||
|
||||
After writing the new learning, decide whether this new solution is evidence that older docs should be refreshed.
|
||||
|
||||
`ce:compound-refresh` is **not** a default follow-up. Use it selectively when the new learning suggests an older learning or pattern doc may now be inaccurate.
|
||||
`ce-compound-refresh` is **not** a default follow-up. Use it selectively when the new learning suggests an older learning or pattern doc may now be inaccurate.
|
||||
|
||||
It makes sense to invoke `ce:compound-refresh` when one or more of these are true:
|
||||
It makes sense to invoke `ce-compound-refresh` when one or more of these are true:
|
||||
|
||||
1. A related learning or pattern doc recommends an approach that the new fix now contradicts
|
||||
2. The new fix clearly supersedes an older documented solution
|
||||
@@ -239,7 +239,7 @@ It makes sense to invoke `ce:compound-refresh` when one or more of these are tru
|
||||
5. The Related Docs Finder surfaced high-confidence refresh candidates in the same problem space
|
||||
6. The Related Docs Finder reported **moderate overlap** with an existing doc — there may be consolidation opportunities that benefit from a focused review
|
||||
|
||||
It does **not** make sense to invoke `ce:compound-refresh` when:
|
||||
It does **not** make sense to invoke `ce-compound-refresh` when:
|
||||
|
||||
1. No related docs were found
|
||||
2. Related docs still appear consistent with the new learning
|
||||
@@ -248,11 +248,11 @@ It does **not** make sense to invoke `ce:compound-refresh` when:
|
||||
|
||||
Use these rules:
|
||||
|
||||
- If there is **one obvious stale candidate**, invoke `ce:compound-refresh` with a narrow scope hint after the new learning is written
|
||||
- If there is **one obvious stale candidate**, invoke `ce-compound-refresh` with a narrow scope hint after the new learning is written
|
||||
- If there are **multiple candidates in the same area**, ask the user whether to run a targeted refresh for that module, category, or pattern set
|
||||
- If context is already tight or you are in lightweight mode, do not expand into a broad refresh automatically; instead recommend `ce:compound-refresh` as the next step with a scope hint
|
||||
- If context is already tight or you are in lightweight mode, do not expand into a broad refresh automatically; instead recommend `ce-compound-refresh` as the next step with a scope hint
|
||||
|
||||
When invoking or recommending `ce:compound-refresh`, be explicit about the argument to pass. Prefer the narrowest useful scope:
|
||||
When invoking or recommending `ce-compound-refresh`, be explicit about the argument to pass. Prefer the narrowest useful scope:
|
||||
|
||||
- **Specific file** when one learning or pattern doc is the likely stale artifact
|
||||
- **Module or component name** when several related docs may need review
|
||||
@@ -261,14 +261,14 @@ When invoking or recommending `ce:compound-refresh`, be explicit about the argum
|
||||
|
||||
Examples:
|
||||
|
||||
- `/ce:compound-refresh plugin-versioning-requirements`
|
||||
- `/ce:compound-refresh payments`
|
||||
- `/ce:compound-refresh performance-issues`
|
||||
- `/ce:compound-refresh critical-patterns`
|
||||
- `/ce-compound-refresh plugin-versioning-requirements`
|
||||
- `/ce-compound-refresh payments`
|
||||
- `/ce-compound-refresh performance-issues`
|
||||
- `/ce-compound-refresh critical-patterns`
|
||||
|
||||
A single scope hint may still expand to multiple related docs when the change is cross-cutting within one domain, category, or pattern area.
|
||||
|
||||
Do not invoke `ce:compound-refresh` without an argument unless the user explicitly wants a broad sweep.
|
||||
Do not invoke `ce-compound-refresh` without an argument unless the user explicitly wants a broad sweep.
|
||||
|
||||
Always capture the new learning first. Refresh is a targeted maintenance follow-up, not a prerequisite for documentation.
|
||||
|
||||
@@ -314,13 +314,13 @@ After the learning is written and the refresh decision is made, check whether th
|
||||
|
||||
Based on problem type, optionally invoke specialized agents to review the documentation:
|
||||
|
||||
- **performance_issue** → `compound-engineering:review:performance-oracle`
|
||||
- **security_issue** → `compound-engineering:review:security-sentinel`
|
||||
- **database_issue** → `compound-engineering:review:data-integrity-guardian`
|
||||
- Any code-heavy issue → always run `compound-engineering:review:code-simplicity-reviewer`, and additionally run the kieran reviewer that matches the repo's primary stack:
|
||||
- Ruby/Rails → also run `compound-engineering:review:kieran-rails-reviewer`
|
||||
- Python → also run `compound-engineering:review:kieran-python-reviewer`
|
||||
- TypeScript/JavaScript → also run `compound-engineering:review:kieran-typescript-reviewer`
|
||||
- **performance_issue** → `review:ce-performance-oracle`
|
||||
- **security_issue** → `review:ce-security-sentinel`
|
||||
- **database_issue** → `review:ce-data-integrity-guardian`
|
||||
- Any code-heavy issue → always run `review:ce-code-simplicity-reviewer`, and additionally run the kieran reviewer that matches the repo's primary stack:
|
||||
- Ruby/Rails → also run `review:ce-kieran-rails-reviewer`
|
||||
- Python → also run `review:ce-kieran-python-reviewer`
|
||||
- TypeScript/JavaScript → also run `review:ce-kieran-typescript-reviewer`
|
||||
- Other stacks → no kieran reviewer needed
|
||||
|
||||
</parallel_tasks>
|
||||
@@ -358,12 +358,12 @@ a brief mention helps all agents discover these learnings.
|
||||
|
||||
Note: This was created in lightweight mode. For richer documentation
|
||||
(cross-references, detailed prevention strategies, specialized reviews),
|
||||
re-run /compound in a fresh session.
|
||||
re-run /ce-compound in a fresh session.
|
||||
```
|
||||
|
||||
**No subagents are launched. No parallel tasks. One file written.**
|
||||
|
||||
In lightweight mode, the overlap check is skipped (no Related Docs Finder subagent). This means lightweight mode may create a doc that overlaps with an existing one. That is acceptable — `ce:compound-refresh` will catch it later. Only suggest `ce:compound-refresh` if there is an obvious narrow refresh target. Do not broaden into a large refresh sweep from a lightweight session.
|
||||
In lightweight mode, the overlap check is skipped (no Related Docs Finder subagent). This means lightweight mode may create a doc that overlaps with an existing one. That is acceptable — `ce-compound-refresh` will catch it later. Only suggest `ce-compound-refresh` if there is an obvious narrow refresh target. Do not broaden into a large refresh sweep from a lightweight session.
|
||||
|
||||
---
|
||||
|
||||
@@ -438,9 +438,9 @@ Subagent Results:
|
||||
✓ Session History: 3 prior sessions on same branch, 2 failed approaches surfaced
|
||||
|
||||
Specialized Agent Reviews (Auto-Triggered):
|
||||
✓ performance-oracle: Validated query optimization approach
|
||||
✓ kieran-rails-reviewer: Code examples meet Rails conventions
|
||||
✓ code-simplicity-reviewer: Solution is appropriately minimal
|
||||
✓ ce-performance-oracle: Validated query optimization approach
|
||||
✓ ce-kieran-rails-reviewer: Code examples meet Rails conventions
|
||||
✓ ce-code-simplicity-reviewer: Solution is appropriately minimal
|
||||
|
||||
File created:
|
||||
- docs/solutions/performance-issues/n-plus-one-brief-generation.md
|
||||
@@ -494,7 +494,7 @@ Build → Test → Find Issue → Research → Improve → Document → Validate
|
||||
|
||||
<auto_invoke> <trigger_phrases> - "that worked" - "it's fixed" - "working now" - "problem solved" </trigger_phrases>
|
||||
|
||||
<manual_override> Use /ce:compound [context] to document immediately without waiting for auto-detection. </manual_override> </auto_invoke>
|
||||
<manual_override> Use /ce-compound [context] to document immediately without waiting for auto-detection. </manual_override> </auto_invoke>
|
||||
|
||||
## Output
|
||||
|
||||
@@ -505,26 +505,26 @@ Writes the final learning directly into `docs/solutions/`.
|
||||
Based on problem type, these agents can enhance documentation:
|
||||
|
||||
### Code Quality & Review
|
||||
- **compound-engineering:review:kieran-rails-reviewer**: Reviews code examples for Rails best practices
|
||||
- **compound-engineering:review:kieran-python-reviewer**: Reviews code examples for Python best practices
|
||||
- **compound-engineering:review:kieran-typescript-reviewer**: Reviews code examples for TypeScript best practices
|
||||
- **compound-engineering:review:code-simplicity-reviewer**: Ensures solution code is minimal and clear
|
||||
- **compound-engineering:review:pattern-recognition-specialist**: Identifies anti-patterns or repeating issues
|
||||
- **review:ce-kieran-rails-reviewer**: Reviews code examples for Rails best practices
|
||||
- **review:ce-kieran-python-reviewer**: Reviews code examples for Python best practices
|
||||
- **review:ce-kieran-typescript-reviewer**: Reviews code examples for TypeScript best practices
|
||||
- **review:ce-code-simplicity-reviewer**: Ensures solution code is minimal and clear
|
||||
- **review:ce-pattern-recognition-specialist**: Identifies anti-patterns or repeating issues
|
||||
|
||||
### Specific Domain Experts
|
||||
- **compound-engineering:review:performance-oracle**: Analyzes performance_issue category solutions
|
||||
- **compound-engineering:review:security-sentinel**: Reviews security_issue solutions for vulnerabilities
|
||||
- **compound-engineering:review:data-integrity-guardian**: Reviews database_issue migrations and queries
|
||||
- **review:ce-performance-oracle**: Analyzes performance_issue category solutions
|
||||
- **review:ce-security-sentinel**: Reviews security_issue solutions for vulnerabilities
|
||||
- **review:ce-data-integrity-guardian**: Reviews database_issue migrations and queries
|
||||
|
||||
### Enhancement & Research
|
||||
- **compound-engineering:research:best-practices-researcher**: Enriches solution with industry best practices
|
||||
- **compound-engineering:research:framework-docs-researcher**: Links to framework/library documentation references
|
||||
- **research:ce-best-practices-researcher**: Enriches solution with industry best practices
|
||||
- **research:ce-framework-docs-researcher**: Links to framework/library documentation references
|
||||
|
||||
### When to Invoke
|
||||
- **Auto-triggered** (optional): Agents can run post-documentation for enhancement
|
||||
- **Manual trigger**: User can invoke agents after /ce:compound completes for deeper review
|
||||
- **Manual trigger**: User can invoke agents after /ce-compound completes for deeper review
|
||||
|
||||
## Related Commands
|
||||
|
||||
- `/research [topic]` - Deep investigation (searches docs/solutions/ for patterns)
|
||||
- `/ce:plan` - Planning workflow (references documented solutions)
|
||||
- `/ce-plan` - Planning workflow (references documented solutions)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Documentation schema for learnings written by ce:compound
|
||||
# Documentation schema for learnings written by ce-compound
|
||||
# Treat this as the canonical frontmatter contract for docs/solutions/.
|
||||
#
|
||||
# The schema has two tracks based on problem_type:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# YAML Frontmatter Schema
|
||||
|
||||
`schema.yaml` in this directory is the canonical contract for `docs/solutions/` frontmatter written by `ce:compound`.
|
||||
`schema.yaml` in this directory is the canonical contract for `docs/solutions/` frontmatter written by `ce-compound`.
|
||||
|
||||
Use this file as the quick reference for:
|
||||
- required fields
|
||||
|
||||
Reference in New Issue
Block a user