CtrlK
BlogDocsLog inGet started
Tessl Logo

compound-engineering-plugin

github.com/EveryInc/compound-engineering-plugin

SkillAddedReview
agent-only-skill

tests/fixtures/sample-plugin/skills/agent-only-skill/SKILL.md

An agent-only skill not intended for direct user invocation

26

ce-babysit-pr

skills/ce-babysit-pr/SKILL.md

Babysits an open GitHub PR until merge-ready, first judging whether an old PR still belongs. Use when asked to watch a PR over time or update an old one — not for one-shot comment resolution or one CI failure. GitHub (incl. Enterprise) only.

71

ce-bakeoff

skills/ce-bakeoff/SKILL.md

Develop independent competing solutions to a defined brief, compare them, and synthesize a winning approach. Use when choosing well requires developing alternatives beyond their current form. Use ce-pov to judge developed material and ce-ideate to discover opportunities.

68

ce-brainstorm

skills/ce-brainstorm/SKILL.md

Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.

63

ce-code-review

skills/ce-code-review/SKILL.md

Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.

65

ce-commit

skills/ce-commit/SKILL.md

Create a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.

72

ce-commit-push-pr

skills/ce-commit-push-pr/SKILL.md

Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.

72

ce-compound

skills/ce-compound/SKILL.md

Capture a solved problem's lesson in its cheapest durable form, a test or lint rule, a coding standard, or a repo learning, or refresh existing learnings against the codebase. Use when verified work corrected a wrong belief about how something behaves, such as a failed approach, a real defect a review caught, or a wrong assumption or document, or when auditing stale, overlapping, or drifted learnings. Do not auto-invoke it for work that went as first planned.

64

ce-compound-refresh

skills/ce-compound-refresh/SKILL.md

Old name for refreshing learnings, which now lives in `ce-compound`. Use only when a prompt or standing instruction names `ce-compound-refresh`; use `ce-compound` for every other learnings audit.

73

ce-debug

skills/ce-debug/SKILL.md

Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.

67

ce-doc-review

skills/ce-doc-review/SKILL.md

Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.

69

ce-dogfood

skills/ce-dogfood/SKILL.md

Hands-off, diff-scoped browser QA of the active branch: maps user flows, drives a real browser, autonomously fixes small breakages with regression tests and commits, judges experience against product personas, and writes a durable dogfood report. Manual invocation only.

68

ce-explain

skills/ce-explain/SKILL.md

Explain how and why something has its current shape, or what happened over a window of work, grounded in evidence. Use when the user asks for an explanation. Use ce-pov for a judgment or recommendation.

60

ce-handoff

skills/ce-handoff/SKILL.md

Create a session handoff for another agent, or resume, find, and read any user-selected continuity source. Use when work or conversation must continue without access to the current session history.

65

ce-help

skills/ce-help/SKILL.md

Help and orientation for Compound Engineering: place the user's work on the compounding loop and recommend the next command, without running it. Use when the user invokes ce-help to ask which skill fits, what comes next, how setup, configuration, cost, or upgrades work, or why a skill misbehaved.

70

ce-ideate

skills/ce-ideate/SKILL.md

Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).

65

ce-noslop

skills/ce-noslop/SKILL.md

Rewrite, check, or draft prose so it carries no AI writing tells, reads plainly on the first read, and keeps every source fact. Use when asked to make writing plainer or free of those tells, to check writing for them, or when drafting from supplied content. Use ce-promote for channel-specific marketing copy.

69

ce-optimize

skills/ce-optimize/SKILL.md

Optimize a named target with a measured loop: attribute a workload's cost, or score variants and keep winners. Use when a working system's metric should move and the winning change is not already known. Use ce-debug when the job is diagnosis; use ce-work when the change is already known.

64

ce-plan

skills/ce-plan/SKILL.md

Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

71

ce-polish

skills/ce-polish/SKILL.md

Polish a working feature through user-directed live browser feedback. Use when a functional feature needs focused UX refinement before shipping.

60