autoplan

Execute CEO, design, and Eng plan reviews sequentially with automatic decisions.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill autoplan-caltexbevo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak/autoplan
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill autoplan-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-review pipeline reads CEO, design, and Eng review skills from disk and runs them sequentially with auto-decisions using six principles. It surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out.

Core Features & Use Cases

  • Sequentially executes CEO, design, and Eng reviews from disk.
  • Auto-decisions with six principles to surface taste decisions at the final gate.
  • Single command to generate a fully reviewed plan ready for approval.

Quick Start

Run /autoplan to execute the full auto-review pipeline on the current 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 plan reviews for engineering governance?

Automating end-to-end plan reviews requires sequentially executing CEO, design, and engineering review skills from disk. The autoplan pipeline runs these stages with automatic decisions, surfacing only borderline taste decisions at a final approval gate.

What is an auto-review pipeline for product plans?

An auto-review pipeline for product plans is a sequential execution of CEO, design, and engineering reviews that applies six decision principles. It automatically processes plan-driven reviews and surfaces final taste decisions at an approval gate.

How do I run a full plan review with a single command?

Running a full plan review with a single command executes the autoplan pipeline on the current plan. It reads required review skills from disk and sequentially applies them to generate a fully reviewed plan ready for final approval.

Can I automate governance decisions for borderline engineering scope?

Automating governance decisions for borderline engineering scope is handled using six decision principles. The pipeline auto-decides standard cases and specifically surfaces close approaches, borderline scope, and codex disagreements at the final approval gate.

Does the plan review pipeline require external dependencies or components?

The plan review pipeline requires no external dependencies or components. It reads the necessary CEO, design, and engineering review skills directly from local disk storage to execute the sequential auto-decisions.

When should I not use an automated sequential review pipeline?

You should not use an automated sequential review pipeline when your plan requires subjective taste decisions outside the six decision principles. The pipeline explicitly defers close approaches, borderline scope, and codex disagreements to a manual final approval gate.