solo-plan

Generate a file-level spec and phased implementation plan from a task description.

18|2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/fortunto2/solo-factory --skill solo-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solo-plan
Source: https://github.com/fortunto2/solo-factory/tree/main/skills/plan
Command: npx skills add https://github.com/fortunto2/solo-factory --skill solo-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning takes vague ideas and translates them into concrete specifications and actionable tasks, preventing scope creep and adoption delay.

Core Features & Use Cases

  • Auto-classifies the task type (feature, bug, refactor, or chore) from the description.
  • Generates a track ID and creates spec.md and plan.md with verifiable acceptance criteria.
  • Produces a phased, atomic task breakdown that maps to code changes, docs, and deployment steps when relevant.

Quick Start

Describe the feature or bug you want planned and let this skill generate a spec and actionable plan.

Frequently Asked Questions about solo-plan

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

FAQPage Schema
How do I turn a short task description into executable file-level plans?

To turn a short task description into executable file-level plans, use automation to auto-classify the task as a feature, bug, refactor, or chore, then generate a track ID, a spec with verifiable acceptance criteria, and a multi-phase plan with atomic tasks.

What is the best way to automate creating a spec and implementation roadmap from an idea?

Automating the creation of a spec and implementation roadmap involves converting ideas into structured specifications and actionable tasks, which prevents scope creep and generates a phased plan that maps directly to atomic code changes and documentation updates.

Can I generate deployment considerations and documentation steps for a code refactor plan?

Yes, you can generate deployment considerations and documentation steps for a code refactor plan. The automation optionally includes deployment steps when infrastructure exists, mapping atomic tasks across phases to necessary code changes, docs, and deployment workflows.

How do I break down a software feature into verifiable acceptance criteria and atomic tasks?

To break down a software feature into verifiable acceptance criteria and atomic tasks, load the project context and generate structured plan artifacts, producing a spec.md for acceptance criteria and a plan.md for the phased implementation roadmap.

Does the generated plan from task planning automation integrate with build execution workflows?

Yes, the generated plan integrates with build execution workflows. The structured plan artifacts, including the spec and multi-phase task breakdown, are specifically designed to be consumed by build processes for direct implementation execution.