autoplan

You can automate end-to-end plan reviews by running a pipeline that executes CEO, design, and engineering reviews sequentially, applying six decision principles to auto-decide intermediate questions and output a fully reviewed plan.

An auto-decision framework for design review pipelines applies six guiding principles to evaluate tradeoffs across CEO, design, and engineering stages, automatically resolving intermediate questions and surfacing taste decisions at a final approval gate.

You enforce completeness and blast-radius safeguards by reading skill files during the review pipeline, validating constraints before auto-deciding steps, and logging all outcomes to ensure reproducibility and track potential impact.

Yes, autoplan handles complex planning workflows with design docs and multi-skill dependencies by reading the required review skills from disk and running them sequentially to produce a fully auto-decided plan.

The best way to run a fully reviewed planning pipeline with one command is executing the auto-review sequence, which generates a ready-to-review plan summary and diagnostics while logging outcomes for reproducibility.

You should not use automated review when taste decisions or subjective design choices require human intuition, as the pipeline auto-decides intermediate steps and only surfaces those specific tradeoffs at a final approval gate.