autoplan

Automating an engineering review workflow involves running sequential design and governance reviews with auto-decisions. This skill orchestrates the end-to-end pipeline, applying six decision principles to produce a fully formed plan with a final approval gate.

An auto-review pipeline is a deterministic execution flow that reads multiple skill specifications from disk and runs them sequentially. It surfaces taste decisions, like borderline scope and codex disagreements, at a final approval gate for a ready-to-merge plan.

You run a fully automated decision flow by executing a single command (/autoplan) that orchestrates multiple review skills from disk. It applies strict adherence to six decision principles and requires provenance in the final output plan.

Yes, you can orchestrate multiple review skills sequentially for governance tasks. The pipeline loads CEO, design, and engineering skill specifications from disk, automating the decision flow while surfacing subjective taste decisions at a final approval gate.

Deterministic execution in an automated review pipeline handles standard decisions via six principles but cannot resolve subjective taste decisions automatically. Close approaches, borderline scope, and codex disagreements must be surfaced for manual review at a final approval gate.