autoplan

Execute CEO, design, and Eng plan reviews sequentially with six decision principles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual review of multi-discipline project plans is slow and error-prone; Autoplan automates the end-to-end review by reading the full CEO, design, and Eng skill definitions from disk and executing them sequentially with auto-decisions using six principles.

Core Features & Use Cases

  • Sequential CEO → Design → Eng review with auto-decisions guided by six principles
  • One-command plan output: from an initial plan to a fully reviewed plan ready for release
  • Telemetry and auditability: logs decisions and outcomes for traceability and governance
  • Proactive orchestration: coordinates multiple skill layers to reduce manual questions and handoffs

Quick Start

Run autoplan in your project to generate a fully reviewed plan from existing skill files with a single command.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I automate multi-discipline plan reviews for software projects?

Automated plan review is achieved by sequentially executing CEO, design, and engineering skill definitions from disk. This orchestrates multiple review layers in one command to produce a fully reviewed plan.

What is sequential CEO, design, and engineering review workflow automation?

Sequential review automation reads full skill definitions from disk and executes CEO, design, and engineering phases in order. It applies six decision principles to auto-review project plans and surfaces final decisions.

How do I run an end-to-end auto-review pipeline with one command?

Run autoplan in your project directory to read existing skill files and execute the end-to-end auto-review pipeline. It processes CEO, design, and engineering phases sequentially to output a release-ready plan.

Do I need existing skill files on disk to run an automated plan review?

Yes, automated plan review requires the full CEO, design, and engineering skill definitions to be present on disk. The pipeline reads these files sequentially to orchestrate the auto-review workflow.

What's the best way to ensure traceability in automated engineering plan reviews?

Automated plan reviews ensure traceability by logging telemetry and auto-decisions throughout the sequential execution. This auditability provides governance by recording outcomes from the CEO, design, and engineering phases.

Why use a sequential auto-review pipeline instead of manual plan reviews?

Sequential auto-review pipelines reduce manual questions and handoffs by proactively coordinating multiple skill layers. This approach mitigates the slow and error-prone nature of manual multi-discipline project plan reviews.