plan

Decompose a problem spec into testable work chunks with dependencies and a progress dashboard.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/rolopez23/agent-harness --skill plan-rolopez23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/rolopez23/agent-harness/tree/main/skills/plan
Command: npx skills add https://github.com/rolopez23/agent-harness --skill plan-rolopez23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates a problem spec into an actionable, testable implementation plan by breaking work into clearly delineated chunks with explicit dependencies and a live progress dashboard.

Core Features & Use Cases

  • Decomposes a spec into named, independently testable chunks to enable parallel work and measurable milestones.
  • Produces per-chunk sub-plans with embedded tests-first steps, supporting TDD-style development and traceable commits.
  • Provides guidance on branching strategy and plan maintenance as work progresses.

Quick Start

Provide a problem spec at docs/<feature-name>/spec.md and run /plan to generate a plan with a status dashboard and per-chunk details.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a software feature spec into an actionable implementation plan?

A spec is decomposed into named, independently testable chunks by applying a tests-first planning workflow that maps dependencies, provides branching guidance, and generates per-chunk sub-plans for measurable milestones.

How do I plan feature development using test-driven development steps?

Feature planning with TDD steps works by decomposing a spec into independent work chunks, mapping dependencies, and producing per-chunk sub-plans that embed tests-first steps to support traceable commits.

What is the best way to break down a project spec into parallel work chunks?

Breaking down a spec into parallel work chunks involves decomposing the specification into named, independently testable segments with explicit dependencies, enabling parallel work and measurable milestones.

Do I need a specific file format to generate a feature implementation plan?

You need a problem specification placed at docs/<feature-name>/spec.md to generate an actionable, testable implementation plan with a status dashboard and per-chunk details.

Can I track feature planning progress using a living dashboard?

You can track feature planning progress using a living dashboard generated alongside the implementation plan, which provides status updates as work progresses through the decomposed, testable work chunks.