autoplan

Run sequential CEO, design, and engineering reviews on a plan file.

1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/shhubbh/flowstate --skill autoplan-shhubbh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/shhubbh/flowstate/tree/main/.claude/skills/gstack/autoplan
Command: npx skills add https://github.com/shhubbh/flowstate --skill autoplan-shhubbh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end review of strategic plans by reading CEO, design, and engineering review skills from disk and executing them with deterministic auto-decisions.

Core Features & Use Cases

  • Auto-run full CEO, design, and Eng reviews using six decision principles.
  • Surface taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate.
  • One command to generate a fully reviewed plan, with proactive suggestions when a plan file exists.

Quick Start

Run /autoplan to execute the full review pipeline and generate a completed plan.

Frequently Asked Questions about autoplan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end plan review across product, design, and engineering domains?▼

Automated plan review runs full CEO, design, and engineering evaluations sequentially using six decision principles. This pipeline reads review skills from disk and executes them with deterministic auto-decisions to produce a fully evaluated plan.

What is an auto-review pipeline for strategic plans and how does it work?▼

An auto-review pipeline orchestrates product, design, and engineering evaluations sequentially with deterministic auto-decisions. It reads CEO, design, and engineering review skills from disk, evaluates plans, and surfaces taste decisions at a final approval gate.

Can I run a full design and engineering plan review with a single command?▼

Yes, running a single command executes the full review pipeline. The orchestrator reads CEO, design, and engineering review skills from disk sequentially, applying six decision principles to generate a fully reviewed plan with proactive suggestions.

How does the pipeline handle borderline scope and taste decisions during plan evaluation?▼

The pipeline surfaces taste decisions like close approaches, borderline scope, and disagreements at a final approval gate. It uses six decision principles to auto-decide clear cases and only escalates subjective taste decisions for manual review.

Do I need an existing plan file to generate proactive suggestions during the review?▼

Yes, a plan file must be present to generate proactive suggestions. The auto-review pipeline requires an existing plan file to read, evaluate across product and engineering domains, and produce a fully reviewed output with actionable recommendations.

What are the limitations of using automated auto-decision principles for plan evaluation?▼

Automated plan evaluation relies on six deterministic decision principles to auto-decide clear cases. It cannot resolve subjective taste decisions automatically, instead surfacing close approaches, borderline scope, and disagreements at a final approval gate for manual review.