npx claudepluginhub levifig/loaf --plugin loafWant just this skill?
Then install: npx claudepluginhub u/[userId]/[slug]
Decomposes specs into atomic tasks with dependencies and priorities. Use when the user asks "break this down" or "create tasks for this spec."
This skill uses the workspace's default tool permissions.
templates/task.mdBreakdown
Decompose specifications into atomic, implementable tasks.
Contents
- Task Breakdown Philosophy
- Task Backend Detection
- Process
- Priority Levels
- Guardrails
- Related Skills
Input: $ARGUMENTS
Task Breakdown Philosophy
Primary principle: separation of concerns.
Right-Sizing Rules
| Rule | Guideline |
|---|---|
| One agent type | Completable by ONE agent (backend-dev, frontend-dev, dba, qa, devops) |
| One concern | Touches one layer, service, or component |
| Context-appropriate | Fits in model context with room for exploration |
| Not over-fragmented | Don't split what naturally belongs together |
The Right Size Test
- Can a single specialized agent complete this? If no, split by agent type
- Does it touch multiple unrelated concerns? If yes, split by concern
- Will the agent need too much context? If yes, split into phases
- Am I splitting just to have more tasks? If yes, merge back
Anti-Patterns
| Don't | Do Instead |
|---|---|
| Split backend + tests into separate tasks | Keep tests with the code they test |
| Create a task per file | Group files by concern |
| Separate "implement" and "verify" tasks | Every task includes its own verification |
Task Backend Detection
Check .agents/loaf.yaml:
task_management:
backend: linear # or "local"
If no config exists, ask user.
Process
Step 1: Parse Input
$ARGUMENTS should reference a spec (e.g., "SPEC-001"). If unclear, list available specs.
Step 2: Read the Spec
Extract: test conditions, scope, implementation notes, appetite.
Step 3: Identify Task Boundaries
Break down by concern (DBA, Backend, Frontend, QA, DevOps). One concern per task. Explicit dependencies for sequential tasks.
Step 4: Interview for Priorities
Ask about highest priority parts, required ordering, preferred implementation sequence.
Step 5: Draft Task List
Create tasks following task template. Each task needs: clear title, priority, file hints, verification command, observable done condition.
Step 6: Present for Approval
Show tasks with priorities, dependencies, and dependency graph. Do NOT create tasks without explicit approval. User may adjust priorities, combine/split, add tasks, or change dependencies.
Step 7: Create Tasks
Linear backend: Create issues with title, description, labels, priority.
Local backend: Use loaf task create --spec SPEC-XXX --title "Task title" --priority P1 for each task. The CLI creates the TASKS.json entry and .md skeleton file. Then edit the .md body content (description, acceptance criteria) directly.
Step 8: Update Spec and Announce
Set spec status to implementing. Announce created tasks with next steps.
Priority Levels
| Priority | Meaning |
|---|---|
| P0 | Urgent/blocking -- drop everything |
| P1 | High -- work next |
| P2 | Normal -- scheduled work (default) |
| P3 | Low -- when time permits |
Guardrails
- One concern per task -- don't mix backend + frontend
- Clear verification -- how to prove it works
- Observable done condition -- not subjective
- File hints -- help session know where to look
- Get approval -- don't create without confirmation
- Update spec status -- mark as implementing
Related Skills
- shape -- Create specs that get broken down
- implement -- Start session for a task or coordinate multiple tasks
Similar Skills
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.