autoplan

Automating the engineering plan review process is done by running a single command that sequentially applies the CEO, design, and engineering skills to your draft on disk. It auto-resolves intermediate questions using a six-principle decision framework to produce a fully reviewed plan.

A six-principle decision framework is an internal logic mechanism used to auto-resolve intermediate questions during sequential plan reviews. It evaluates conflicts between the CEO, design, and engineering skill files to enforce completeness and automatically decide standard intermediate questions.

Handling taste decisions and scope disagreements is managed by surfacing borderline cases and codex conflicts at a final approval gate. The auto-review pipeline delays these specific subjective decisions for manual resolution instead of auto-deciding them.

Running the full CEO, design, and engineering reviews with a single command is supported by reading your plan files directly from disk. It executes the sequential pipeline and outputs auditable structured artifacts ready for the final approval gate.

You should not use an automated plan review pipeline when your draft requires continuous manual interventions for subjective taste decisions. The workflow is designed for teams wanting to auto-decide standard intermediate questions while only surfacing borderline scope or disagreements at the end.

The autoplan workflow requires no external dependencies, operating entirely by reading CEO, design, and engineering skill files from local disk. It produces auditable outputs and structured artifacts for downstream processes without needing additional components.