auto-plan

Generates structured multi-phase task plans with acceptance criteria and progress tracking.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/lov-b/Skills --skill auto-plan-lov-b
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-plan
Source: https://github.com/lov-b/Skills/tree/main/skills/auto-plan
Command: npx skills add https://github.com/lov-b/Skills --skill auto-plan-lov-b

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague task or requirement into an actionable development plan is error-prone: scope is misjudged, phases lack clear acceptance criteria, and progress gets lost across conversations. This Skill analyzes the project context, classifies task size (small/medium/large), and produces a structured plan document that both the user and the Agent can follow and resume. ## Core Features & Use Cases - Structured Four-Part Plans: Outputs requirement overview (goal, current state, done criteria), phased breakdown with dependencies, per-phase acceptance criteria plus test cases for large tasks, and a progress tracking table. - Task Size Classification: Judges small/medium/large tasks based on project and module scope, adjusting phase granularity accordingly. - Document Update Mode: Updates an existing plan file in place via patch preview instead of regenerating the full plan, preserving structure and annotating new content. - Progress Persistence & Resume: Maintains a status board in the saved Markdown file so a new conversation can resume execution by reading the progress table; supports optional Git commit+push to a configured docs repository. - Use Case: You describe a cross-project feature request; the Skill scans the workspace, classifies it as a large task, and saves a plan file with 6 phases, test cases, and a progress board you can resume from days later. ## Quick Start Ask the Agent to create a structured development plan for your task by saying "auto-plan: help me plan the user permission refactor across the backend and admin frontend".

Frequently Asked Questions about auto-plan

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

FAQPage Schema
How do I create a structured development plan from a requirement?▼

Describe your task or requirement and trigger the plan workflow with a phrase like "make a plan" or "/auto-plan". The Skill analyzes your project context, classifies the task size, and outputs a phased plan with acceptance criteria you can confirm and save.

How does task size classification work for project planning?▼

Tasks are classified as small (single module, one-shot), medium (multiple projects or modules, single requirement), or large (multiple requirements across projects). The classification determines phase granularity: 1-2 phases for small tasks, 3-5 for medium, and 5+ with test cases for large ones.

Can I update an existing plan document instead of regenerating it?▼

Yes. Point the Agent at an existing plan file and ask to update, supplement, or adjust it. The Skill enters document update mode, shows a patch preview of the changes, and writes back to the original file while preserving its structure.

How do I resume a saved plan in a new conversation?▼

Each saved plan contains a progress tracking table with per-phase status. When you ask to continue execution, the Agent reads that table to locate the current phase directly, without re-analyzing the entire plan or requiring you to restate the requirement.

Where are plan documents saved and can they be committed to Git?▼

Plans are saved to a user-configured directory, defaulting to the system Downloads folder, with filenames like plan-{slug}-{timestamp}.md. If a Git repository is detected, the Skill offers to commit and push only the new plan file, never bundling unrelated changes.