planning-and-task-breakdown

planning-and-task-breakdown is a skill for Claude Code from 233i/agent-skills. It costs 59 tokens per session (1,894 once invoked), scanned A, original, MIT.

A planning guide that turns a clear specification or requirement into small, ordered tasks with clear acceptance checks. It also maps dependencies so work can be done in a sensible order.

In plain words
What is it for?
Use it to plan multi-part features, estimate their scope, explain the work to people, and prepare tasks for one or more coding agents or sessions.
Why use it?
Large or vague work is hard to start and easy to tangle. Breaking it into small, verifiable pieces makes the scope, risks, and possible parallel work clearer.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the agent-skills plugin — 20 skills, 7 commands, 3 agents, 1 hook shipped together

Good fit Use it to plan multi-part features, estimate their scope, explain the work to people, and prepare tasks for one or more coding agents or sessions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/233i/agent-skills/planning-and-task-breakdown
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add 233i/agent-skills --skill planning-and-task-breakdown
Clone the repo
git clone --depth 1 https://github.com/233i/agent-skills

Made for: Claude Code.

Or install agent-skills, the plugin that ships this one along with the rest of its 20 skills, 7 commands, 3 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for planning-and-task-breakdown

README.md
[![agentmods](https://agentmods.dev/badge/skills/233i/agent-skills/planning-and-task-breakdown/github.svg)](https://agentmods.dev/skills/233i/agent-skills/planning-and-task-breakdown)
Your own site
<a href="https://agentmods.dev/skills/233i/agent-skills/planning-and-task-breakdown"><img src="https://agentmods.dev/badge/skills/233i/agent-skills/planning-and-task-breakdown/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for planning-and-task-breakdown

Your own site · 80×15
<a href="https://agentmods.dev/skills/233i/agent-skills/planning-and-task-breakdown"><img src="https://agentmods.dev/badge/skills/233i/agent-skills/planning-and-task-breakdown.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,894 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.01894
Opus 5 $0.00030 $0.00947
Sonnet 5 $0.00012 $0.00379
Haiku 4.5 $0.00006 $0.00189

Measured 10d ago against content hash 52c748ceb643, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

planning-and-task-breakdown scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/planning-and-task-breakdown/SKILL.md · 224 lines

How it starts

The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.

规划与任务拆解

概览

把工作拆成小而可验证的任务,并给每个任务明确的验收标准。好的任务拆解,是 agent 能稳定完成工作与把事情做成一团乱麻之间的区别。每个任务都应该小到可以在一次专注会话中完成实现、测试和验证。

何时使用

  • 你已经有 spec,需要把它拆成可执行单元
  • 任务太大或太模糊,难以下手
  • 工作需要在多个 agent 或多个会话之间并行展开
  • 你需要向人类说明工作范围
  • 实现顺序并不明显

不适用的场景: 单文件且范围显而易见的改动,或 spec 中已经包含了定义清晰的任务。

规划流程

步骤 1:进入规划模式(Plan Mode)

在写任何代码之前,先以只读模式工作:

  • 阅读 spec 和相关代码区域
  • 识别现有模式和约定
  • 绘制组件间依赖
  • 记录风险与未知项

规划阶段不要写代码。 产出应该是一份计划文档,而不是实现。

步骤 2:识别依赖图

先画清楚谁依赖谁:

Database schema
    │
    ├── API models/types
    │       │
    │       ├── API endpoints
    │       │       │
    │       │       └── Frontend API client
    │       │               │
    │       │               └── UI components
    │       │
    │       └── Validation logic
    │
    └── Seed data / migrations

实现顺序应该沿依赖图自底向上推进,先打基础。

步骤 3:做纵向切片

不要先做完整数据库、再做完整 API、再做完整 UI。应该一次打通一条完整功能路径:

坏例子(水平切片):

Task 1: Build entire database schema
Task 2: Build all API endpoints
Task 3: Build all UI components
Task 4: Connect everything

好例子(纵向切片):

Task 1: User can create an account (schema + API + UI for registration)
Task 2: User can log in (auth schema + API + UI for login)
Task 3: User can create a task (task schema + API + UI for creation)
Task 4: User can view task list (query + API + UI for list view)

每个纵向切片都能交付可工作的、可测试的功能。

步骤 4:编写任务

每个任务都遵循如下结构:

## Task [N]: [简短描述性标题]

**Description:** 一段话说明这个任务完成什么。

**Acceptance criteria:**
- [ ] [具体且可测试的条件]
- [ ] [具体且可测试的条件]

**Verification:**
- [ ] Tests pass: `npm test -- --grep "feature-name"`
- [ ] Build succeeds: `npm run build`
- [ ] Manual check: [需要检查什么]

**Dependencies:** [依赖哪些任务编号,或写 "None"]

**Files likely touched:**
- `src/path/to/file.ts`
- `tests/path/to/test.ts`

**Estimated scope:** [Small: 1-2 files | Medium: 3-5 files | Large: 5+ files]

步骤 5:排序并设置检查点

排列任务时确保:

  1. 依赖先满足,基础优先
  2. 每个任务完成后系统仍处于可工作状态
  3. 每做完 2 到 3 个任务就设置一次验证检查点
  4. 高风险任务尽量提前,尽早失败

加入显式检查点:

## Checkpoint: After Tasks 1-3
- [ ] All tests pass
- [ ] Application builds without errors
- [ ] Core user flow works end-to-end
- [ ] Review with human before proceeding

Read the full file on GitHub · 224 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 224 lines · 59 tokens per session scan A 52c748ceb643

Subscribe to this mod's changes

planning-and-task-breakdown is a skill published in the GitHub repository 233i/agent-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 1,894 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens