autoplan

Execute CEO, design, and Eng review workflows from local skill definitions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Reads the CEO, design, and Eng review skill definitions from disk and executes them in strict sequence with auto-decisions, producing a fully reviewed plan.

Core Features & Use Cases

  • End-to-end CEO, design, and Eng review pipeline run from local skill definitions.
  • Auto-decision gate surfaces final decisions and highlights taste decisions when conflicts exist.
  • Use when you want a single command to generate a fully reviewed plan without intermediate prompts.

Quick Start

Run /autoplan to execute the full review pipeline and produce 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 end-to-end engineering and design review workflows?

You can automate the full review pipeline by running a single command that reads local skill definitions and executes CEO, design, and engineering phases in strict order with auto-decisions. This generates a complete, fully reviewed plan without intermediate prompts.

Can I run a full review pipeline without intermediate prompts for approval?

Yes, you can run a full review pipeline without intermediate prompts by using auto-decision gates. The system reads local skill definitions, executes CEO, design, and engineering phases sequentially, and surfaces final decisions automatically, highlighting taste decisions only when conflicts exist.

What is an auto-decision gate in a design and engineering review process?

An auto-decision gate in a review process is a final checkpoint that automatically surfaces decisions after executing sequential CEO, design, and engineering reviews. It specifically highlights taste decisions when conflicts exist between phases to ensure traceable outcomes.

How do I generate a fully reviewed plan from local skill definitions?

You generate a fully reviewed plan by reading local skill definitions from disk and executing CEO, design, and engineering review workflows in strict sequence. The process implements six guiding principles, applies auto-decisions, and logs all outcomes for traceability.

Does the automated review pipeline enforce a strict phase order for CEO, design, and engineering?

Yes, the automated review pipeline enforces a strict phase order across CEO, design, and engineering reviews. It reads skill definitions from disk, executes them sequentially without intermediate prompts, and implements six guiding principles to produce a fully reviewed plan.

When should I use a single-command automated review pipeline instead of manual reviews?

You should use a single-command automated review pipeline when you need a complete review across CEO, design, and engineering phases without intermediate prompts. It is ideal for generating fully reviewed plans with auto-decisions, strict phase order, and traceable outcome logs.