autoplan

Orchestrate CEO, design, eng, and DX reviews into a single plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-review pipelines are needed to coordinate multiple specialized review skills. This skill orchestrates CEO, design, engineering, and DX reviews from disk, applies six decision principles, and produces a single, fully reviewed plan. It surfaces taste decisions at a final gate so you can ship with confidence.

Core Features & Use Cases

  • Orchestrates CEO, design, eng, and DX reviews from disk and runs them in sequence.
  • Applies six decision principles to auto-decide intermediate steps and surface taste decisions at the final gate.
  • Produces a single, ready-to-ship plan; supports auto-run when asked or plan files exist.

Quick Start

Run /skill:autoplan to generate a fully reviewed plan from your existing CEO, design, eng, and DX reviews.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I automate code and design review workflows into a single pipeline?

To automate code and design review workflows, you can run an auto-review pipeline that sequentially orchestrates CEO, design, engineering, and DX reviews from disk. It applies six decision principles to auto-decide intermediate steps and produces a single, fully reviewed plan.

What is an auto-review pipeline for planning and how does it work?

An auto-review pipeline for planning coordinates multiple specialized review skills by reading CEO, design, eng, and DX reviews from disk. It runs them sequentially using six principles to auto-decide intermediate steps and surfaces taste decisions at a final approval gate.

Do I need existing review skills on disk to run the autoplan workflow?

Yes, the autoplan workflow reads full CEO, design, eng, and DX review skills directly from disk to orchestrate them. It proactively suggests auto-running when a plan file exists and integrates with gstack.

What's the best way to handle taste decisions like close approaches or codex disagreements during plan reviews?

The best way to handle taste decisions during plan reviews is to use an auto-review pipeline that surfaces close approaches or codex disagreements at a final approval gate. This ensures you can manually review nuanced taste decisions before shipping.

Why does my automated plan review stop at a final approval gate instead of finishing automatically?

An automated plan review stops at a final approval gate to deliberately surface taste decisions, such as close approaches or codex disagreements. The pipeline auto-decides intermediate steps but pauses for final human approval on subjective matters.