10 actions in 10 pieces of software · ranked by words, meaning and measured trust · 614 ms

1. 1ce-proofverified and signedpassport

   skilleveryinc/compound-engineering-pluginrecord

   • ce-proof

     Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.

2. 2ce-povverified and signedpassport

   skilleveryinc/compound-engineering-pluginrecord

   • ce-pov

     Judge a supplied subject against the project's evidence and constraints. Use when assessing an external-adoption question, a holistic take on a document, or a supplied approach set. Use for an oracle panel to consult other models and reconcile their opinions. Use ce-explain for understanding and ce-

3. 3ce-brainstormverified and signedpassport

   skilleveryinc/compound-engineering-pluginrecord

   • ce-brainstorm

     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.

4. 4ce-explainverified and signedpassport

   skilleveryinc/compound-engineering-pluginrecord

   • ce-explain

     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.

5. 5ce-prototypeverified and signedpassport

   skilleveryinc/compound-engineering-pluginrecord

   • ce-prototype

     Build a throwaway prototype to answer how something should work, feel, or read. Use when committing the wrong answer would be expensive to unravel and a cheap sketch cannot settle it. Not a rough visual probe during brainstorming, not for deciding what to build, not polishing a feature that already

6. 6ce-compoundverified and signedpassport

   skilleveryinc/compound-engineering-pluginrecord

   • ce-compound

     Document a solved problem as a durable repo learning. Use when verified work produced non-obvious reasoning absent from its final code, tests, or existing docs; avoid routine fixes whose artifacts already explain the lesson.

7. 7ce-polishverified and signedpassport

   skilleveryinc/compound-engineering-pluginrecord

   • ce-polish

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

8. 8ce-workverified and signedpassport

   skilleveryinc/compound-engineering-pluginrecord

   • ce-work

     Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without the shipping tail.

9. 9ce-code-reviewverified and signedpassport

   skilleveryinc/compound-engineering-pluginrecord

   • ce-code-review

     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.

10. 10ce-work-betaverified and signedpassport

    skilleveryinc/compound-engineering-pluginrecord

    • ce-work-beta

      [BETA] Execute ce-work with external delegate support.