autoplan

Read CEO, design, and engineering review skills from disk to produce a reviewed plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end review pipelines by reading CEO, design, and eng review skills from disk to produce a fully reviewed plan.

Core Features & Use Cases

  • Reads a complete set of reviews from disk and orchestrates them end-to-end.
  • Runs through six decision principles to auto-decide intermediate questions and surfaces a final gate.
  • Emits a plan-ready artifact that can be reviewed or shipped with a single command.

Quick Start

Run /autoplan to execute the full CEO, design, and eng reviews from disk and surface a complete plan.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I automate the engineering review workflow for a feature plan?

Automate the engineering review workflow by running a single command to orchestrate CEO, design, and engineering reviews from disk, producing a fully reviewed plan with telemetry data.

What is an automated end-to-end review pipeline for software engineering?

An automated end-to-end review pipeline reads CEO, design, and engineering skill files from disk, applies six auto-decision principles to intermediate questions, and surfaces taste decisions at a final gate.

Do I need skill documents on disk to run the autoplan review process?

Yes, you need skill documents on disk to run the autoplan review process, as it reads CEO, design, and engineering review skills directly from disk to generate the final plan artifact.

Can I auto-decide intermediate planning questions and only surface final taste decisions?

Yes, the review workflow applies six auto-decision principles to resolve intermediate questions automatically, surfacing only the remaining taste decisions at a final gate for manual review.

What is the best way to generate a plan-ready artifact from feature ideas and changes?

Generate a plan-ready artifact from feature ideas by executing a single command that runs the complete CEO, design, and engineering review pipeline and outputs a reviewed plan with telemetry.

Are there limitations to automating software engineering planning with a single command?

The automation requires existing skill documents on disk and surfaces taste decisions at a final gate rather than fully automating them, meaning human review is still needed for subjective planning choices.