autoplan

Orchestrate CEO, design, eng, and DX reviews into a finalized plan.

4|1|Updated Sep 13, 2023
One-click install
npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill autoplan-louisfghbvc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/louisfghbvc/mcp-leetcode-crawler/tree/main/.agent/skills/autoplan
Command: npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill autoplan-louisfghbvc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates an end-to-end review pipeline by reading CEO, design, eng, and DX review inputs from disk and running them with auto-decisions to produce a finalized plan.

Core Features & Use Cases

  • Orchestrates multiple review skills (CEO, design, engineering, DX) in a single pipeline.
  • Automatically decides using a defined set of principles and surfaces decision points.
  • Produces a single, ready-to-ship plan and surfaces actionable edges, including recommendations when the plan exists on disk.

Quick Start

Run autoplan to auto-run all reviews and produce a final, ready-to-ship plan.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I automate a design review pipeline for multiple stakeholders?

An end-to-end review pipeline reads CEO, design, engineering, and DX inputs from disk, applies six decision principles for auto-decisions, and surfaces only taste decisions at a final gate to produce a ready-to-ship plan.

How do I consolidate engineering and design review inputs into a single plan?

Consolidate review inputs by reading stakeholder files from disk and running them through an automated pipeline that applies six decision principles to auto-decide conflicts and output a single ready-to-ship plan file.

What is an auto-decision gate in a software review pipeline?

An auto-decision gate applies six defined principles to automatically resolve standard review conflicts across stakeholders, surfacing only subjective taste decisions at a final gate for manual approval.

Do I need existing review files on disk to run an automated plan pipeline?

Yes, the automated plan pipeline requires existing CEO, design, engineering, and DX review input files on disk to read, orchestrate, and process into a finalized, ready-to-ship plan.

What is the best way to generate a governance-ready plan from multiple stakeholder reviews?

The best way to generate a governance-ready plan is running an automated review pipeline that reads stakeholder inputs, applies six decision principles, and surfaces taste decisions at a final gate to produce a finalized plan file.

When should I use an automated review pipeline instead of manual plan approval?

Use an automated review pipeline when multiple stakeholders must be satisfied and you need fast decision gates, comprehensive governance-ready reviews, and a finalized plan generated efficiently in a single run.