You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
End-user-facing documentation for compound-engineering plugin skills. Each page covers the skill's high-level purpose, novel mechanics, use cases, and chain position relative to other skills.
For runtime behavior and contributor reference, the SKILL.md in each skill's source folder under skills/ is authoritative.
The compound-engineering core loop
[/ce-ideate] (optional) "What's worth exploring?"
│
▼
┌─→ /ce-brainstorm "What does this need to be?"
│ │
│ ▼
│ /ce-plan "What's needed to accomplish this?"
│ │
│ ▼
│ /ce-work "Build it."
│ │
│ ▼
└── /ce-compound "Capture what we learned."
/ce-compound is the closer that makes the loop compound: it writes learnings into docs/solutions/, which the next iteration's /ce-brainstorm and /ce-plan read as grounding — that return arrow is the whole point. /ce-ideate is an optional prelude for when you don't yet know what to work on. Everything else in this catalog is either an anchor around the loop or an on-demand tool used when a specific need arises — not a step you walk through every time.
The Core Loop
The steps of every engineering iteration. /ce-ideate runs only when you need to find a direction first; the other four run in order per piece of work.
Recurring feedback sweep — ingest Slack/GitHub items (email experimental) since per-source cursors, acknowledge at source, analyze recordings, verify fixes merged, and reconcile an /lfg-ready rolling plan
Form a decisive, project-grounded verdict on an external input (framework, library, CVE, pattern) — dual-grounding floors, cold or warm (mid-session) invocation, graded Adopt/Trial/Hold/Reject/Not-our-problem with a reasoned handoff
Turn a concept, a diff, an idea, or a window of your own recent work into a dense, visual explainer written for you personally — optional check-in (predict-then-reveal for diffs, corrected exercises), capability-detected destination ask
Review requirements or plan documents using skill-local reviewer personas — coherence, feasibility, product-lens, design-lens, security-lens, scope-guardian, adversarial
Go from working changes to an open PR with adaptive descriptions, related-reference handling, three modes (full workflow / description update / description-only generation), and a concept-teaching section for anything the change newly introduces
Draft user-facing announcement copy for a shipped feature (X, changelog, LinkedIn, email) — voice-matched via the optional Spiral CLI, a lite layer of editorial & social expertise without it, drafts only
Hands-off diff-scoped browser QA of the active branch — maps flows, autonomously fixes small breakages with regression tests and commits, writes a durable report (manual invocation only)