# Compound Engineering v3
**作者**: Trevin Chow
**日期**: 2026-04-22T21:32:47.000Z
**来源**: [https://x.com/trevin/status/2047066108763770998](https://x.com/trevin/status/2047066108763770998)
---
v3 is here! The naming cleanup we've been teasing for 3 weeks finally lands, our brainstorm and plan created artifacts now give requirements a paper trail from idea to commit, every harness outside Claude Code gets first-class install and runtime support, and our review loops stop letting you rubber-stamp your way through findings — all in Compound Engineering 3.0.0.
## One consistent namespace, no more collisions
Every skill and agent now lives under a single ce- hyphen prefix. ce:work becomes ce-work, git-commit becomes ce-commit, setup becomes ce-setup, and so on.
The old mix of prefixed, unprefixed, and colon-prefixed names collided with similarly named skills from other plugins across harnesses — a persistent source of ambiguity any time you ran more than one plugin side by side. The colon in ce:work also required filesystem sanitization on Windows. After v3, everything CE ships sits under its own unambiguous namespace, so our skills don't fight with anyone else's. 2 small renames went along for the ride to help clarity and simplification: ce-review became ce-code-review, and ce-document-review became ce-doc-review.
This is a breaking change. Existing chains, references, and muscle memory need to move to the new names... but it's worth it! 😀
## A paper trail from brainstorm to commit, for you and your agents
Before v3, a requirement you wrote during ce-brainstorm didn't have a stable identity. By the time it reached ce-plan it was prose; by the time it was implemented it was vibes. When a test failed or a reviewer asked "what was this covering?", the answer lived in somebody's head — and the agents running ce-work or ce-code-review had no better way to recover intent than you did.
v3 rewrites the ce-brainstorm and ce-plan product docs to carry much better structure rather than just prose. The brainstorm requirements doc now has 1st class sections for Actors, Key Flows, Acceptance Examples, and Requirements, each with stable IDs. ce-plan pulls those IDs forward into a Requirements Trace section and assigns plan-local implementation unit IDs that survive plan deepening and reorders. Test scenarios reference the acceptance examples they cover. ce-work recognizes those unit IDs in blockers, verification, and task labels.
The obvious payoff is provenance for you and your agents. Trace a failing test back to the acceptance example it was supposed to cover, a plan unit back to the flow that motivated it, and a commit back to the brainstorm entry that started it all. The less obvious and arguably bigger payoff is that the agents can follow those same threads. A reviewer can check whether an implementation actually satisfies the acceptance example it claims to cover. A debugger can see which flow a failing test was exercising. A work agent hitting a blocker on U3 can go read the origin criteria instead of guessing at intent.
The biggest change this also support is improved greenfield product-tier brainstorms. They also get structural support they didn't have before prior to v3. The template used to optimize for incremental changes inside an existing product, so deep-scope work on something new had thin guidance and forced the agent to improvise a shape.
Better structure upstream produces better outcomes downstream...and not just for the human in the loop.
## First-class across every harness
Claude Code was where CE started, and for a long time everything else felt like a second-class port. v3 changes that across the board.
- Codex users can install the native way: codex plugin marketplace add plus the /plugins TUI. Skills and MCP servers register directly with no Bun converter step. Codex's plugin spec doesn't cover custom agents yet, so a small converter fills the gap by writing CE's agents as Codex TOML under ~/.codex/agents/.
- Pi gets an even bigger shift: we stopped shipping our own compatibility layer which collided with the most popular community subagent extension and serialized parallel dispatch. We now delegate to 2 community extensions, @nicopreme's pi-subagents for native parallel sessions and @edlzsh's pi-ask-user, for a blocking-question UX. Pi users get real parallelism and proper question overlays without us competing with community maintainers on infrastructure they already do better.
- Copilot on the CLI and in VSCode both get first class support with the native plugin install too!
Cross-harness cleanup landed alongside the big lifts:
- question-tool no longer silently skips blocking questions on Codex (where request_user_input is only exposed in Plan mode) or on Claude Code (where the tool is deferred and its schema isn't loaded at session start), fixed with a unified instruction applied across 37 SKILL.md files.
- Skill descriptions are now capped at the harness limit with a frontmatter test enforcing it.
## Reviews that make you decide, not rubber-stamp
Our review skills all used to ask bucket-level policy questions which results in one decision covering many findings. In practice that degraded into rubber-stamping or wholesale deferral, and reviewers ended up re-litigating the same premise in different wordings across a dozen findings.
v3 reshapes the whole review family around per-finding engagement:
- ce-code-review Interactive mode walks you through findings one at a time with Apply/Defer/Skip/"LFG the rest" options and a plain-English framing of each proposed fix. Finally, easier way to understand review feedback so you can make better and faster decisions. If you choose to defer the findins, we now route to your real issue tracker instead of a deprecated internal todo store that CE managed.
- ce-doc-review adds three-tier autofix classification and premise-dependency chain grouping — collapse findings that all hinge on one root into a single decision with cascading dependents. Typical engagement dropped from 14+ findings per run to roughly 4-6 real decisions.
- ce-resolve-pr-feedback got tightened clustering (cross-round evidence is required before it activates, so unrelated single-round feedback no longer triggers holistic refactors) with bot-wrapper noise filtered out.
- A new ce-swift-ios-reviewer persona joins the reviewer cohort for Swift/iOS stacks, catching SwiftUI state-wrapper misuse, Combine retain cycles, and Core Data context threading. Thanks to @jcjvm for contribution.
## Debugging that diagnoses, not guesses
ce-debug already had a 4-phase methodology, but in practice it defaulted to print-debugging, skipped environment sanity before deep tracing, and sometimes declared heisenbugs "fixed" when instrumentation perturbed them out of sight. v3 tightens all of that:
- An early environment sanity check before deep tracing: branch, deps, runtime, env vars, stale artifacts.
- An assumption audit at hypothesis time to help agent steering. Many wrong hypotheses are correct hypotheses tested against a wrong assumption.
- A parallel read-only subagent dispatch option for broad searches.
- A new technique reference covering boundary instrumentation, test-order pollution, repro minimization, stepping debuggers versus instrumentation, heisenbugs, and a bug-class checklist (timezone, encoding, float, overflow, cache, auth).
## Less friction, fewer sharp edges
Small quality-of-life upgrades to existing skills:
- ce-proof now triggers on direct user requests to share or iterate on a markdown file. "Share this to Proof so we can iterate" works without needing an upstream caller like ce-brainstorm or ce-plan. You can try it with any markdown down in your repo for example with something like "/ce-proof iterate with me on <doc>"
- ce-demo-reel adds local save as an alternative to catbox upload, so you can keep demo assets on disk without manually fishing them out of temp directories. Thanks to Lucas Henn for this contribution.
- ce-setup checks for ast-grep and the corresponding agent skill, with a new Skills section in the health-check output matching the existing Tools section.
And a round of correctness and safety fixes:
- ce-plan no longer misclassifies non-software research as only factual lookup, silently substitutes generic web search for user-named resources, or skips the blocking post-plan handoff menu. You can get real thoughtful agent assisted planning for your non-software problems whether it's your kids math lessons, that roadtrip to Portland or the home improvement project you've been trying to pin down.
- ce-work stopped inventing human-time estimates and multi-day session breakdowns — framings that don't apply to agent execution.
- ce-update derives its cache directory from the plugin root parent with a shape check, so malformed env values can't collapse into a dangerous rm -rf target. Thanks to @andrewlook for raising this issue.
- ce-compound YAML frontmatter now survives strict parsers and Cowork's plugin validator.
What's next: more work on product and strategy skills, sharper verification and shipping support, and configurable preferences so things like the compounded-docs output path don't have to live hardcoded as docs/solutions. That last one was close to ready for v3 but needed more time to bake.
v3 is as much a foundation as a release....more landing soon!
## 相关链接
- [Trevin Chow](https://x.com/trevin)
- [@trevin](https://x.com/trevin)
- [82K](https://x.com/trevin/status/2047066108763770998/analytics)
- [Compound Engineering 3.0.0](https://github.com/everyinc/compound-engineering-plugin)
- [@nicopreme](https://x.com/@nicopreme)
- [pi-subagents](https://github.com/nicobailon/pi-subagents)
- [@edlzsh](https://x.com/@edlzsh)
- [pi-ask-user](https://github.com/edlsh/pi-ask-user)
- [@jcjvm](https://x.com/jcjvm)
- [Lucas Henn](https://github.com/Isaccseven)
- [ast-grep](https://github.com/ast-grep/ast-grep)
- [@andrewlook](https://x.com/andrewlook)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [5:32 AM · Apr 23, 2026](https://x.com/trevin/status/2047066108763770998)
- [82.9K Views](https://x.com/trevin/status/2047066108763770998/analytics)
- [View quotes](https://x.com/trevin/status/2047066108763770998/quotes)
---
*导出时间: 2026/4/23 15:05:24*