autoplan

Automate sequential CEO, design, and engineering reviews on project plans.

11|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill autoplan-ajsai47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/ajsai47/holyclaude/tree/main/skills/team/autoplan
Command: npx skills add https://github.com/ajsai47/holyclaude --skill autoplan-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running multiple review cycles on project plans requires manually invoking separate skills for CEO, design, and engineering reviews, then synthesizing their outputs. This Skill automates the entire pipeline, applying six decision principles to resolve intermediate questions and surfacing only the taste decisions that require human judgment.

Core Features & Use Cases

  • Sequential Review Execution: Automatically reads and runs CEO, design, and engineering review skills in the correct order.
  • Auto-Decision Principles: Applies six core principles (completeness, boil lakes, pragmatic, DRY, explicit over clever, bias toward action) to resolve intermediate questions without user input.
  • Taste Decision Gate: Surfaces close approaches, borderline scope, and model disagreements at a final approval gate for human input.
  • Use Case: When you have a rough plan and want a fully reviewed output without answering 15-30 intermediate questions across three separate review sessions.

Quick Start

Use the autoplan skill to run the complete review pipeline on your current plan file and present only the taste decisions that require your approval.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I automate design and engineering plan reviews without answering intermediate questions?

Automated plan review executes sequential CEO, design, and engineering workflows, applying six decision principles to resolve intermediate questions and surfacing only taste-level tradeoffs for final human approval.

What is the best way to run a comprehensive plan validation pipeline for software development?

Comprehensive plan validation pipelines automatically sequence CEO, design, and engineering reviews on project plans, synthesizing outputs while reserving human oversight exclusively for borderline scope and close approach decisions.

How does automated engineering review handle principle-based auto-decisions?

Automated engineering review applies six core principles—completeness, boil lakes, pragmatic, DRY, explicit over clever, and bias toward action—to automatically resolve intermediate questions without requiring manual user input.

Can I use automated review workflows for software plans that need multiple review cycles?

Automated review workflows support software development projects requiring comprehensive plan validation, replacing manual invocation of separate review skills with a single sequential pipeline that synthesizes outputs automatically.

When do I need to provide human input during an automated plan review session?

Human input is required at the final taste decision gate, where the automated review surfaces close approaches, borderline scope decisions, and model disagreements that need human judgment rather than principle-based auto-resolution.