Trevin Chow details the updates to Compound Engineering culminating in v2.60.0 of March 31, 2026. The throughline is the tightening of the end-to-end pipeline: code reviews are less noisy and now mandatory, plans detect more gaps before implementation, and day-to-day usage friction continues to decrease.
The most significant change concerns ce:review. A headless mode enables programmatic invocation by other skills, which unlocked the next step: making code review mandatory across the entire pipeline (ce:work, ce:brainstorm, ce:plan). Full review is the default level, with limited review requiring explicit justification. To avoid "mandating noise," a 6-level confidence rubric (0.00–1.00) with a 0.60 suppression threshold was added simultaneously. Six false-positive categories are targeted: pre-existing issues, style nitpicks, intentional patterns, cases handled elsewhere, code restatement, and generic advice. Result: a 49% reduction in false positives with no loss of real detection. Findings are checked against the PR context, and multi-persona consensus boosts confidence by 0.10.
ce:work now accepts raw prompts without a prior plan, with automatic complexity assessment. Universal test discovery before implementation ensures code/test synchronization. A new check detects behavioral changes without corresponding tests.
ce:brainstorm fixes a subtle bug where Phase 1.1 prevented agents from reading technical files, producing unverified claims such as "this table doesn't exist" without checking the schema. Now, verification of the current state is allowed while implementation decisions remain deferred to planning.
ce:plan gains an interactive deepening mode allowing each agent's findings to be accepted, rejected, or discussed before integration. Document review is made mandatory after enrichment.
A cross-cutting feature automatically generates diagrams (mermaid/ASCII) when complexity exceeds certain thresholds. resolve-pr-feedback now detects "whack-a-mole" by clustering similar comments. document-review moves from 3 to 2 tiers and suggests the next step based on document type. Finally, ce:compound adopts a track-based schema (bug vs knowledge) with a discoverability check.