autoplan

Run CEO, Design, and Engineering reviews on draft product plans.

8|2|Updated Mar 24, 2026

Search Tags:#plan validation #architecture review #product roadmap #UI/UX review #auto-review #decision automation #sequential pipeline

Ready to run

npx skills add https://github.com/MFS-code/gstack --skill autoplan-mfs-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/MFS-code/gstack/tree/main/autoplan
Command: npx skills add https://github.com/MFS-code/gstack --skill autoplan-mfs-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you avoid spending hours manually asking and answering many review questions by turning a rough plan into a fully reviewed, decision-ready plan automatically.

Core Features & Use Cases

Auto-runs the CEO → Design → Engineering review pipeline for a plan, with structured decision-making to produce a coherent approval gate.
Applies completeness-first decision principles to reduce “almost done” gaps and catch taste vs. mechanical issues at the right stage.
Surfaces borderline and disagreement areas as visible “taste decisions” so you know what might need your final call.

Quick Start

Invoke autoplan only when you type /autoplan on the plan you want reviewed.

Frequently Asked Questions about autoplan

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

FAQPage Schema

How do I automatically review a product roadmap for missing UI states and engineering gaps?▼

To automatically review a product roadmap, you can run a sequential review pipeline that evaluates design and engineering completeness. This process applies decision automation to surface scope gaps and missing UI states, outputting a structured failure registry for your plan.

What is sequential plan validation and how does it work for development plans?▼

Sequential plan validation runs CEO, Design, and Engineering reviews in order on a draft plan. It uses deterministic execution and auto-decisions to catch taste versus mechanical issues at the right stage, producing a decision-ready plan with a comprehensive concern registry.

How do I get started with auto-reviewing my plan end-to-end in one go?▼

To auto-review your plan end-to-end, type the designated invocation command on your draft development plan. This triggers the automatic review pipeline, handling premise confirmations through manual gates while applying completeness-first decision principles to finalize approvals.

Does automated architecture review work for plans with weak engineering and testing considerations?▼

Yes, automated architecture review specifically targets plans with weak engineering and testing considerations. It applies completeness-first decision principles to reduce 'almost done' gaps, surfacing borderline areas as visible taste decisions requiring your final manual call.

When should I avoid using an automated decision pipeline for plan validation?▼

You should avoid automated decision pipelines for plan validation if your draft requires extensive subjective debate rather than structured gap analysis. The process handles premise confirmations via manual gates, but heavily relies on deterministic execution to auto-approve mechanical issues.