Autoplan

What Is This?

Overview

Autoplan is an automated review pipeline skill that reads CEO, design, and engineering review skill definitions from disk and executes them sequentially in a single command. Rather than running each review phase manually and waiting for human input at every decision point, Autoplan applies six core decision principles to handle routine choices automatically, reserving human judgment only for the decisions that genuinely require it.

The pipeline is designed to surface taste decisions at a final approval gate. These include close approaches where two solutions are nearly equivalent, borderline scope questions, and cases where the codex produces conflicting guidance. By batching these edge cases into a single review moment, Autoplan eliminates the interruption-heavy workflow that slows down plan reviews when each phase runs independently.

The result is a fully reviewed plan produced from one command. Engineers and product leads get structured feedback across all three review dimensions without manually coordinating between review types or tracking which phases have completed.

Who Should Use This

• Engineering leads who regularly review technical plans and want consistent, structured output without running each review phase separately
• Product managers coordinating between design, engineering, and executive review cycles on the same plan
• Developers working within the gstack environment who want automated decision handling for routine plan reviews
• Team leads responsible for maintaining review quality across multiple concurrent projects
• Technical program managers who need reproducible review pipelines that apply the same standards across all plans
• Individual contributors preparing plans for review who want to pre-check their work before submitting to stakeholders

Why Use It?

Problems It Solves

• Manual review coordination requires tracking which phases have run, which decisions are pending, and which reviewers have responded, creating overhead that compounds across multiple plans
• Running CEO, design, and engineering reviews separately produces inconsistent output formats and makes it difficult to compare findings across review types
• Routine decisions that have clear answers under established principles still interrupt the review process when they require explicit human confirmation
• Taste decisions and borderline scope questions get buried in review threads rather than surfaced clearly for the person who needs to make the final call
• Review pipelines that depend on manual sequencing are difficult to reproduce consistently, leading to variation in review quality across plans

Core Highlights

• Executes all three review types (CEO, design, engineering) in a single command
• Applies six decision principles automatically to handle non-ambiguous choices
• Surfaces taste decisions, close approaches, and codex disagreements at a single approval gate
• Reads skill definitions from disk, ensuring reviews reflect the current version of each skill
• Reduces review coordination overhead by consolidating output into one structured result
• Designed for use within the gstack development environment
• Triggered by natural language commands including "auto review," "autoplan," and "run all reviews"

How to Use It?

Basic Usage

Invoke Autoplan using any of the recognized trigger phrases within your gstack environment:

autoplan
auto review
run all reviews
review this plan automatically
make the decisions

The pipeline reads the skill definitions for CEO review, design review, and engineering review from disk, then runs each sequentially against the current plan.

Specific Scenarios

Scenario 1: Pre-submission plan check. Before submitting a technical plan to stakeholders, run autoplan to get structured feedback across all three review dimensions. The pipeline completes all phases and presents a consolidated output with any taste decisions flagged for your review.

Scenario 2: Codex disagreement resolution. When the engineering review and design review produce conflicting guidance on an implementation approach, Autoplan surfaces the disagreement at the approval gate rather than silently resolving it, giving you the context needed to make an informed decision.

Real-World Examples

User: autoplan
Pipeline: Reading CEO review skill... complete
Pipeline: Reading design review skill... complete
Pipeline: Reading engineering review skill... complete
Pipeline: Applying decision principles (1-6)...
Pipeline: Surfacing 2 taste decisions for approval gate
Output: Full reviewed plan + approval gate summary

Important Notes

Requirements

• The gstack environment must be configured with CEO, design, and engineering review skill files accessible on disk
• Autoplan version 1.0.0 or later must be installed and active in the skill set
• The plan being reviewed must be available in the current working context before invoking the pipeline