autoplan

To run an automated plan review without intermediate questions, you need a plan file on disk and execute the single autoplan command. It chains CEO, design, engineering, and DX assessments sequentially, applying decision principles to yield a final approved plan.

An auto-review pipeline orchestrates multi-skill assessments across CEO, design, engineering, and DX domains sequentially. It applies six decision principles to process your plan file and surfaces nuanced taste decisions at a final approval gate.

Yes, you can trigger proactive plan reviews when a file exists on disk. The system detects the plan file and proactively suggests running the full review gauntlet, skipping 15 to 30 intermediate questions to accelerate approval.

Final approval gates handle borderline scope and codex disagreements by surfacing them as taste decisions. The automated pipeline applies six decision principles first, then pauses at the gate for you to resolve nuanced choices.

Yes, the autoplan pipeline integrates with the gstack runtime to automate plan execution. It reads review skills from disk and orchestrates them within the gstack environment to produce a fully reviewed plan.

Automating sequential reviews limits manual intervention during intermediate steps, constraining output to six decision principles. Complex plans with highly subjective design nuances may stall at the final approval gate requiring manual taste decisions.