autoplan

Automating review pipelines is done by sequentially running CEO, design, and engineering reviews from disk with auto-decisions, surfacing only taste-based decisions at a final approval gate to produce a single approved plan.

An auto-review workflow reads on-disk review skills and executes them sequentially, applying six decision principles to auto-approve standard cases while flagging borderline scope and codex disagreements for manual review.

Running an end-to-end review with one command requires executing /autoplan, which reads on-disk review files, applies auto-decisions, and outputs a fully reviewed plan ready for shipping.

Taste decisions surfaced during an automated review pipeline include close approaches, borderline scope, and codex disagreements, which are held back from auto-approval and presented at a final gate for manual judgment.

Yes, automating the CEO, design, and engineering workflow requires access to on-disk review files, as the pipeline reads these skills sequentially to apply auto-decisions and generate an approved plan.

You should not use a fully automated review pipeline when your plan involves subjective taste decisions like close approaches or borderline scope, as these require manual judgment at the final approval gate rather than auto-decisions.