autoplan

Automate gated planning governance for feature development with pass/fail gates.

15|5|Updated May 17, 2026
One-click install
npx skills add https://github.com/cropsgg/skills --skill autoplan-cropsgg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/cropsgg/skills/tree/main/skills/planning/autoplan
Command: npx skills add https://github.com/cropsgg/skills --skill autoplan-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates end-to-end planning governance by chaining executive, design, and engineering reviews into a single, gated pipeline that yields a unified, locked plan.

Core Features & Use Cases

  • Sequentially gates CEO review, design review, and engineering review to ensure scope, architecture, and risk are addressed before proceeding.
  • Outputs a single locked plan document with explicit gates and pass/fail status, plus decomposition into actionable issues.
  • Generates PRD drafts and issue lists to accelerate handoff into product development.

Quick Start

Run autoplan on a feature to produce a locked plan document and decomposed issues ready for PRD.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I automate the feature planning pipeline for multi-discipline reviews?

Automating the feature planning pipeline applies a gated sequence of CEO, design, and engineering reviews to yield a single locked plan and decomposed issues. It sequentially addresses scope, architecture, and risk before proceeding to product development.

What is a locked plan in feature development governance?

A locked plan in feature development governance is a unified document generated after passing executive, design, and engineering gates. It records explicit pass/fail statuses per gate and links directly to PRD drafts and actionable issue decomposition.

Can I use a gated review pipeline for complex scope and high-risk features?

A gated review pipeline is explicitly designed for features with complex scope, medium-to-high risk, or multi-discipline reviews. It ensures architecture and risk are addressed through sequential gates before any development handoff occurs.

How do I decompose a locked plan into actionable issues and PRD drafts?

Decomposing a locked plan into actionable issues and PRD drafts happens automatically after passing all review gates. The pipeline outputs a docs/plans path linking the unified locked plan to the generated issue lists to accelerate product development handoff.

When should I not use an automated planning governance pipeline?

You should not use an automated planning governance pipeline for low-risk or simple features that lack multi-discipline review requirements. The sequential CEO, design, and engineering gates are specifically built to address complex scope and high-risk architectural challenges.