plan

Create executable multi-phase software execution plans with TDD templates and dependency tracking.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mulev/solo-dev --skill plan-mulev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/mulev/solo-dev/tree/main/skills/plan
Command: npx skills add https://github.com/mulev/solo-dev --skill plan-mulev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn vague planning ideas into concrete, executable plans that guide software delivery with built-in testing, phased work, and progress tracking.

Core Features & Use Cases

  • Create single-phase or multi-phase plans with a master plan and phase slices, including TDD templates, dependency tracking, and progress dashboards.
  • Update plans to reflect progress, bug rounds, and completed tasks, with integration to tracker systems.
  • Auto-link to a system plan pointer and store task references for execution.
  • Use references for templates, conventions, and project detection to standardize planning.

Quick Start

Tell me what you want planned, and I'll generate a multi-phase plan with tests, implementation, and documentation.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn vague software ideas into actionable project plans with TDD?

Executable software project plans are generated by decomposing work into discovery, testing, implementation, and delivery phases. This provides TDD-first templates, dependency tracking, and phase slices to guide development.

Does this planning approach support multi-phase decomposition for refactoring and bug fixes?

Multi-phase planning applies to features, fixes, and refactors by creating a master plan with vertical phase slices. Each phase includes dedicated testing, implementation steps, and documentation updates.

Can I integrate task tracking into the generated execution plans?

Task-tracking integration is supported through auto-linking to a system plan pointer. It stores task references and updates plans to reflect progress, bug rounds, and completed tasks.

What is the best way to standardize project planning across different software features?

Standardized software planning uses references for templates, conventions, and project detection. This ensures consistent phase decomposition and executable plan generation across varied features.

How do I update an existing project plan to reflect completed tasks and progress?

Project plan updates capture progress, bug rounds, and completed tasks by modifying the existing phase slices. Integration with tracker systems ensures the task references and progress dashboards stay aligned.

Do I need specific tracker systems to use the automated planning templates?

No specific tracker systems are required as dependencies. Optional task-tracking integration is available if your environment supports it, but single-phase and multi-phase plans generate independently.