Skill Documentation
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-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.
| Skill |
Description |
/ce-ideate |
Optional first step — discover strong, qualified directions worth exploring with six conceptual frames, warrant requirement, adversarial filtering |
/ce-brainstorm |
Define what something should become — collaborative dialogue, named gap lenses, requirements-only unified plan |
/ce-plan |
Bound execution with guardrails — enrich unified plans with U-IDs, test scenarios, automatic confidence check; WHAT decisions, not HOW code |
/ce-work |
Execute against implementation-ready plan guardrails — figure out the HOW with code in front of you, ship through quality gates |
/ce-compound |
Close the loop by capturing what you learned into docs/solutions/ so the next iteration starts smarter — bug track + knowledge track |
Around the Loop
Skills that anchor, feed, or maintain the loop without being steps inside it.
| Skill |
Description |
/ce-strategy |
Create or maintain STRATEGY.md — the upstream anchor read by ce-ideate, ce-brainstorm, and ce-plan as grounding |
/ce-product-pulse |
Outer feedback loop — single-page time-windowed report on usage, performance, errors, followups; saved to docs/pulse-reports/ as a timeline |
/ce-sweep |
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 |
/ce-compound-refresh |
Maintain docs/solutions/ over time — five outcomes (Keep / Update / Consolidate / Replace / Delete), Interactive + Autofix modes |
On-Demand
Invoked when a specific need arises — not part of any chain.
| Skill |
Description |
/ce-pov |
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 |
/ce-explain |
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 |
/ce-debug |
Find root causes systematically — causal chain gate, predictions, post-fix polish/review, PR handoff |
/ce-code-review |
Structured code review with skill-local reviewer personas, confidence-gated findings, four modes |
/ce-doc-review |
Review requirements or plan documents using skill-local reviewer personas — coherence, feasibility, product-lens, design-lens, security-lens, scope-guardian, adversarial |
/ce-simplify-code |
Refine recently changed code — reuse, quality, and efficiency review; behavior preservation verified |
/ce-optimize |
Metric-driven iterative optimization loops — three-tier evaluation, parallel experiments, persistence discipline |
Research & Context
Git Workflow
| Skill |
Description |
/ce-commit |
Create a single, well-crafted git commit — convention-aware, sensitive-file-safe, file-level logical splitting |
/ce-commit-push-pr |
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 |
/ce-babysit-pr |
Watch an open PR and keep it moving toward merge — react to incoming review comments (via /ce-resolve-pr-feedback) and CI failures (via /ce-debug) as each arrives, comments-first, with a crash-safe resumable tick, continuous or checkpoint mode per harness, and a settle window that avoids premature "ready to merge" |
/ce-worktree |
Ensure work happens in an isolated git worktree — detect existing isolation, prefer the harness's native worktree tool, fall back to plain git |
Autonomous Pipeline
| Skill |
Description |
/lfg |
Run the full hands-off engineering pipeline from planning through a green PR — plan, work, simplify, review, fix, browser-test, ship, and watch CI |
Frontend Design
| Skill |
Description |
/ce-polish |
Conversational UX polish — start dev server, open browser, iterate together; auto-detects 8 frameworks (manual invocation only) |
Collaboration
| Skill |
Description |
/ce-proof |
Publish, view, comment on, and edit markdown via Proof, Every's collaborative editor — Web API and Local Bridge surfaces |
Workflow Utilities
| Skill |
Description |
/ce-promote |
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 |
/ce-resolve-pr-feedback |
Evaluate, fix, and reply to PR review feedback in parallel — including nitpicks |
/ce-dogfood |
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) |
/ce-test-browser |
End-to-end browser tests using a host-native browser with agent-browser fallback |
/ce-test-xcode |
Build and test iOS apps on simulator using XcodeBuildMCP — screenshots, logs, human verification |
/ce-setup |
Diagnose optional tool capabilities and bootstrap safe project-local config |
See also
For the top-level install and usage guide, see README.md. Each skill's authoritative runtime spec is in skills/<skill>/SKILL.md.