planning-and-task-breakdown SKILL.md skillA

planning-and-task-breakdown from skillmds/skillmd is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add skillmds/skillmd/planning-and-task-breakdown@git:20260919.fecc0d5

Pins git:20260919.fecc0d5 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

skillmds/skillmd

Path

plugins/create-agent-skills/skills/planning-and-task-breakdown/SKILL.md

Versions recorded

1

Latest version

git:20260919.fecc0d5, committed Sep 19, 2026

Size

7,631 bytes

Repository stars

250

License

MIT

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Planning and Task Breakdown

## Overview

Decompose work into small, verifiable tasks with explicit acceptance criteria. Good task breakdown is the difference between an agent that completes work reliably and one that produces a tangled mess. Every task should be small enough to implement, test, and verify in a single focused session.

## When to Use

- You have a spec and need to break it into implementable units
- A task feels too large or vague to start
- Work needs to be parallelized across multiple agents or sessions
- You need to communicate scope to a human
- The implementation order isn't obvious

**When NOT to use:** Single-file changes with obvious scope, or when the spec already contains well-defined tasks.

## The Planning Process

### Step 1: Enter Plan Mode

Before writing any code, operate in read-only mode:

- Read the spec and relevant codebase sections
- Identify existing patterns and conventions
- Map dependencies between components
- Note risks and unknowns

**Do NOT write code during planning.** The output is a plan document saved to `tasks/plan.md` and a task list saved to `tasks/todo.md`, not implementation.

### Step 2: Identify the Dependency Graph
…

Read the whole file at its exact version.

How to install

mdr add skillmds/skillmd/planning-and-task-breakdown@sha256:e79417132a267e09

[![mdr](https://markdownregistry.com/badge/art_rdgfly4yg23qdbrd.svg)](https://markdownregistry.com/a/art_rdgfly4yg23qdbrd)

Versions

The registry has recorded 1 version of this file, committed on Sep 19, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_rdgfly4yg23qdbrd
GET https://markdownregistry.com/api/v1/resolve?ref=skillmds/skillmd/planning-and-task-breakdown
GET https://markdownregistry.com/api/v1/blob/e79417132a267e09f21f991be6453699a4db65bce8c74b69c8202299b742470d

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from skillmds/skillmd

Every file in skillmds/skillmd

Other files named planning-and-task-breakdown

Browse by kind, by grade A, or by owner.