autoplan

You can automate an end-to-end plan review by running a single command that sequentially executes CEO, design, eng, and DX review skills, returning a consolidated verdict with auto-decisions.

The best way to run sequential reviews is using an automated pipeline that reads review skills from disk and executes them in sequence, enforcing decision principles and surfacing taste decisions at a final gate.

Yes, you can trigger a full gate workflow with a single command that proactively prompts when a plan file exists, executing the review gauntlet and surfacing contextual taste notes for approval.

Decision principles work by enforcing six specific rules during the automated review process, enabling auto-decisions for standard plan elements while surfacing borderline scope and disagreements at the final approval gate.

Auto-review works without manual intervention by using auto-decisions to process standard plan elements, only halting at a final approval gate to surface taste decisions like close approaches or codex disagreements.

The limitation is that while standard elements receive auto-decisions, taste decisions such as close approaches, borderline scope, and codex disagreements must be manually reviewed at the final approval gate.