autoplan

Automate sequential CEO, design, engineering, and DX review workflows on project plans.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/a29paul/hexlens --skill autoplan-a29paul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/a29paul/hexlens/tree/main/.claude/skills/gstack/autoplan
Command: npx skills add https://github.com/a29paul/hexlens --skill autoplan-a29paul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the tedious manual work of running multiple review cycles on project plans. Instead of answering 15-30 intermediate questions across separate CEO, design, engineering, and DX review sessions, you get a fully reviewed plan with automated decisions in one command.

Core Features & Use Cases

  • Sequential Review Pipeline: Automatically runs CEO, design, engineering, and DX review skills in sequence.
  • Automated Decision-Making: Applies 6 decision principles to make auto-decisions on review findings.
  • Taste Decision Gate: Surfaces subjective decisions like close approaches, borderline scope, and codex disagreements at a final approval gate for human input.
  • Use Case: Perfect for builders who have a plan file and want the full review gauntlet without answering dozens of intermediate questions.

Quick Start

Use the autoplan skill to automatically run all review gauntlets on your current plan and present the final approved result with any taste decisions flagged for your input.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I automate cross-functional plan validation for a project file?

Automated plan validation runs sequential CEO, design, engineering, and DX review workflows on your project file, applying decision principles to auto-approve findings and flag subjective items for final review.

What is the best way to run multiple review workflows on a project plan without manual input?

Sequential review pipelines automate the gauntlet of architecture, design, and DX critiques, eliminating 15-30 intermediate manual questions by applying auto-decisions and surfacing only borderline scope items at a final gate.

Do I need the gstack framework to run automated project plan reviews?

Yes, automated plan validation requires the gstack skill framework and existing project plan files to sequentially invoke review modules, apply decision principles, and process findings for final approval.

Can I use automated review pipelines for architecture and design critique before implementation?

Yes, automated review pipelines are designed for product development scenarios requiring comprehensive architecture review, design critique, and plan validation to evaluate decisions before implementation begins.

How does the taste decision gate handle subjective findings in plan validation?

The taste decision gate surfaces subjective findings like close approaches, borderline scope, and codex disagreements at a final approval gate, requiring human input only for items that automated decision principles cannot resolve.

What are the limitations of automated decision-making in cross-functional review workflows?

Automated decision-making applies six principles to resolve objective findings but cannot finalize subjective decisions, requiring human input at a final gate for close approaches, borderline scope, and codex disagreements.