autoplan

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

3|14|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill autoplan-cegit27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/autoplan
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill autoplan-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running multiple review skills manually requires answering dozens of intermediate questions and coordinating several separate commands. This skill automates the entire review gauntlet, from CEO and design reviews to engineering and developer experience checks, delivering a fully reviewed plan with auto-decisions in one step.

Core Features & Use Cases

  • Sequential Review Pipeline: Automatically runs CEO, design, engineering, and DX review skills in the correct order.
  • Auto-Decision Engine: Applies six decision principles to make taste calls on close approaches, borderline scope, and codex disagreements.
  • Final Approval Gate: Surfaces only the decisions that need human judgment, saving you from reviewing everything.
  • Use Case: You have a detailed plan for a new feature and want all reviews completed before presenting to stakeholders. Run autoplan to get a fully vetted plan with clear recommendations and flagged decisions.

Quick Start

Use the autoplan skill to run the complete review pipeline on your current plan file and receive a fully reviewed plan with auto-decisions surfaced for your final approval.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I automate sequential architecture and design reviews for a project plan?

Automate sequential architecture and design reviews by running a pipeline that executes CEO, engineering, and developer experience checks in order, generating a fully reviewed project plan with auto-decisions surfaced for final approval.

What is the best way to run multiple code review workflows on a feature plan at once?

The best way to run multiple code review workflows on a feature plan at once is using an automated sequential pipeline that applies decision principles to make taste calls on borderline scope and auto-approves clear passes.

How does an automated review pipeline handle borderline scope and design disagreements?

An automated review pipeline handles borderline scope and design disagreements by applying an auto-decision engine with six decision principles to make taste calls, surfacing only codex disagreements that require human judgment.

Do I need specific configuration files to automate project plan validation?

Yes, you need access to project plan files, review skill modules, and decision principle configurations to automate project plan validation and generate auto-approved or flagged review outcomes.

When should I not use an automated pipeline for comprehensive plan validation?

You should not use an automated pipeline for comprehensive plan validation when your project lacks detailed plan files or when you need manual control over individual intermediate review questions and separate command coordination.