autoplan

Automating a project plan review pipeline involves sequentially running CEO, design, and eng review skills to generate auto-decisions based on 6 principles, surfacing only taste decisions at a final approval gate. You can trigger this by running an autoplan command on your plan file.

An automated review workflow for project planning sequentially executes CEO, design, and engineering review skills from disk, making auto-decisions using 6 specific principles and isolating subjective taste decisions for final gate approval.

Decision principles in review automation work by providing 6 specific rules that the pipeline uses to automatically resolve standard plan objections, leaving only subjective taste decisions to be surfaced and approved manually at a final gate.

You can use review automation without full manual intervention by applying 6 decision principles to auto-resolve standard objections. However, the pipeline is designed to halt at a final gate to surface subjective taste decisions for manual approval.

The limitation of auto-decision in a review pipeline is that it cannot resolve subjective choices. While 6 principles handle standard auto-decisions, taste decisions must be manually reviewed and approved at a final gate before the plan is fully accepted.