autoplan

You can automate planning reviews by orchestrating sequential CEO, design, engineering, and DX evaluations from disk to surface a final plan for approval. This sequential multi-skill execution applies a six-decision-principle gate to auto-decide and output a reviewed plan.

Running multi-role evaluations sequentially in a single command is the best way to process an existing plan file. It executes CEO review, design critique, engineering plan, and DX readiness checks in order, then auto-decides and surfaces near-misses.

Yes, you can auto-decide and surface near-misses in a planning pipeline without manual prompting. The sequential review process detects when a plan file exists and proactively suggests running the full evaluation gauntlet without asking 15-30 questions.

Planning review automation requires no external dependencies or components to execute the sequential evaluations. It reads the plan directly from disk and runs the sub-skills internally to apply the decision gate and output a single final plan.

You should use a sequential multi-skill review pipeline when a plan file exists and you need to apply a six-decision-principle gate across CEO, design, engineering, and DX perspectives. It provides proactive guidance and outputs a fully reviewed plan for approval.

A limitation of auto-decision gates for plan review pipelines is that they require a pre-existing plan file on disk to function. Without an active plan file, the sequential sub-skills cannot execute the evaluations or surface a final plan.