autoplan

Execute CEO, design, and engineering review skills from disk with six decision principles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end review process by reading CEO, design, and engineering review skills from disk and executing them in a deterministic sequence using six decision principles. This reduces manual back-and-forth and surfaces the critical tradeoffs at a final approval gate.

Core Features & Use Cases

  • Orchestrates CEO, design, and Eng reviews in a single run to produce a fully reviewed plan.
  • Surfaces taste decisions (close calls, scope boundaries, potential disputes) at the gate to guide faster decisions.
  • Proactively applies the review gauntlet when a plan file exists, minimizing 15–30 intermediate questions.

Quick Start

Run the full auto-review by invoking /autoplan to generate a fully reviewed plan.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I automate code review and design review for a planning session?

Automated code and design review for a planning session is handled by orchestrating CEO, design, and engineering reviews in a single run, applying six decision principles to yield a fully reviewed plan.

What is the best way to run an end-to-end auto-review on a project plan?

The best way to run an end-to-end auto-review is invoking a single command that reads review skill definitions from disk and executes them deterministically, minimizing 15 to 30 intermediate manual questions.

How does auto-review handle close calls and scope boundary disputes?

Auto-review handles close calls and scope boundary disputes by surfacing taste decisions at a final approval gate, guiding faster decisions on critical tradeoffs after the deterministic review sequence completes.

Do I need a plan file to trigger the auto-review gauntlet?

You need a plan file to proactively trigger the auto-review gauntlet, ensuring the orchestration process reads the necessary skill definitions and enforces guardrails for completeness and actionability.

What distinguishes deterministic orchestration from manual review workflows?

Deterministic orchestration distinguishes itself from manual review workflows by reading skill files from disk and applying six decision principles automatically, reducing manual back-and-forth and enforcing completeness guardrails.

Can I apply multiple review skills simultaneously without intermediate questions?

You can apply multiple review skills simultaneously without intermediate questions by proactively running the review gauntlet on an existing plan file, executing CEO, design, and engineering reviews in one command.