autoplan

Automate the end-to-end review workflow to generate a gate-approved plan.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gfires/motion-analysis --skill autoplan-gfires
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/gfires/motion-analysis/tree/main/autoplan
Command: npx skills add https://github.com/gfires/motion-analysis --skill autoplan-gfires

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the end-to-end review workflow by running the CEO, design, engineering, and DX checks from disk to generate a fully reviewed plan.

Core Features & Use Cases

  • Automates the full plan and review pipeline from problem statement to decision gate.
  • Orchestrates multiple sub-skills (office-hours, design doc checks, plan generation, routing) in a single command.
  • Use Case: When asked to "auto review" a feature, Autoplan surfaces final decisions and a complete plan without answering intermediate questions.

Quick Start

Run autoplan to execute the full auto-review pipeline and generate a complete plan.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I automate the full plan and review workflow without answering intermediate prompts?

To automate the review workflow without intermediate prompts, you can run a single command that orchestrates all design, engineering, and DX checks from disk to generate a fully reviewed plan.

What is an automated end-to-end review pipeline for feature planning?

An automated end-to-end review pipeline reads all skill components from disk to execute CEO, design, engineering, and DX checks, surfacing final taste decisions and a gate-approved plan.

Can I generate a ready-to-ship plan from a problem statement without manual intervention?

Yes, you can generate a ready-to-ship plan from a problem statement by orchestrating six decision principles automatically, producing a complete plan with an explicit decision record.

Does the automated review pipeline require any external dependencies or components?

No, the automated review pipeline requires no external dependencies or components, running entirely from disk to orchestrate sub-skills like office-hours and plan generation.

When should I use an automated plan generation tool instead of manual review?

You should use automated plan generation when you need a complete plan for a feature or branch and want to bypass answering intermediate questions during the review process.

What is the best way to surface taste decisions during feature planning?

The best way to surface taste decisions is to run an automated review pipeline that orchestrates multiple sub-skills and outputs a gate-approved plan with an explicit decision record.