autoplan

Automate end-to-end auto-review across CEO, design, and engineering files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/effiraid/reflix-nextjs --skill autoplan-effiraid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/effiraid/reflix-nextjs/tree/main/.claude/skills/gstack/autoplan
Command: npx skills add https://github.com/effiraid/reflix-nextjs --skill autoplan-effiraid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-review pipelines solve the tedious, multi-skill coordination problem by running CEO, design, and eng reviews from disk and making auto-decisions using predefined principles, producing a unified, ready-to-ship plan.

Core Features & Use Cases

  • End-to-end auto-review across CEO, design, and eng reviews, surfacing clear decisions at the gate.
  • Single-command execution that reads structured skill files and outputs a complete plan for release.
  • Proactive governance via six decision principles to resolve intermediate questions and surface tradeoffs.

Quick Start

Run /autoplan to generate a fully reviewed plan from the skill files on disk.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I automate code review and design review workflows together?

Automated review workflows coordinate multi-skill reviews by reading structured design and engineering files from disk to produce a unified, ready-to-ship plan. This eliminates manual coordination by applying predefined decision principles to resolve intermediate questions automatically.

What is an auto-review pipeline for engineering plans?

An auto-review pipeline is an automated process that runs CEO, design, and engineering reviews sequentially from disk files. It uses six decision principles to evaluate tradeoffs and surface clear decisions at the gate, outputting a complete plan for release.

How do I generate a fully reviewed release plan from structured documentation?

Generating a fully reviewed release plan requires reading structured skill files from disk and executing a single command. The pipeline applies governance principles across design and engineering documentation, producing a deliverable plan and review output.

Does automated plan generation work with existing design and engineering documentation on disk?

Automated plan generation works specifically with projects that have structured design and engineering documentation stored as files on disk. It reads the relevant skill files directly, applies six decision principles, and outputs a complete plan without requiring external integrations.

What's the best way to resolve intermediate questions during an automated code review workflow?

The best way to resolve intermediate questions during automated code review is using predefined decision principles applied proactively. The pipeline surfaces tradeoffs and makes auto-decisions at the review gate, ensuring a unified plan output without manual intervention.

When should I not use a single-command auto-review pipeline?

A single-command auto-review pipeline should not be used when a project lacks structured design and engineering documentation files on disk. It requires predefined skill files to read and evaluate, so unstructured or ad-hoc projects without governance documentation will not produce usable plan outputs.