Help us improve
Share bugs, ideas, or general feedback.
From oac
Breaks complex features into atomic JSON subtasks with dependencies, acceptance criteria, deliverables, and agent assignments. Use for multi-file changes or parallelizable work.
npx claudepluginhub darrenhinde/openagentscontrol --plugin oacHow this skill is triggered — by the user, by Claude, or both
Slash command
/oac:task-breakdownThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Break down complex features into atomic, verifiable subtasks with dependency tracking. Each subtask gets its own JSON file with clear acceptance criteria and deliverables.
Decomposes specs into ordered, verifiable tasks with acceptance criteria using vertical slicing and dependency graphs. Use for large tasks, scope estimation, or parallel agent work.
Breaks down implementation plans into detailed task lists with agent contexts, acceptance criteria, dependencies, priorities, complexity levels, and status tracking.
Decomposes feature requests into phased task boards with dependency mapping, parallelization flags, risk flags, edge cases, and test matrices.
Share bugs, ideas, or general feedback.
Break down complex features into atomic, verifiable subtasks with dependency tracking. Each subtask gets its own JSON file with clear acceptance criteria and deliverables.
Announce at start: "I'm using the task-breakdown skill to create an execution plan for [feature]."
Identify these elements:
Write .tmp/tasks/{feature}/task.json:
{
"id": "jwt-auth",
"name": "JWT Authentication System",
"status": "active",
"objective": "Implement JWT-based authentication with refresh tokens",
"context_files": [
".opencode/context/core/standards/code-quality.md",
".opencode/context/core/standards/security-patterns.md"
],
"reference_files": [
"src/middleware/auth.middleware.ts"
],
"exit_criteria": [
"All tests passing",
"JWT tokens signed with RS256"
],
"subtask_count": 3,
"completed_count": 0,
"created_at": "2026-02-16T02:00:00Z"
}
Rules:
context_files: standards/conventions ONLYreference_files: project source files ONLYWrite .tmp/tasks/{feature}/subtask_01.json, subtask_02.json, etc:
{
"id": "jwt-auth-01",
"seq": "01",
"title": "Create JWT service with token generation",
"status": "pending",
"depends_on": [],
"parallel": true,
"suggested_agent": "CoderAgent",
"context_files": [
".opencode/context/core/standards/security-patterns.md"
],
"reference_files": [],
"acceptance_criteria": [
"JWT tokens signed with RS256 algorithm",
"Access tokens expire in 15 minutes"
],
"deliverables": [
"src/auth/jwt.service.ts",
"src/auth/jwt.service.test.ts"
]
}
Rules:
depends_on arrayparallel: true for isolated workVerify:
## Tasks Created
Location: .tmp/tasks/jwt-auth/
Files: task.json + 3 subtasks
Subtasks:
- 01: Create JWT service (parallel: true, agent: CoderAgent)
- 02: Create password hashing util (parallel: true, agent: CoderAgent)
- 03: Integrate middleware (parallel: false, agent: CoderAgent)
Next Steps:
- Execute subtasks in dependency order
- Tasks 01 and 02 can run in parallel
- Task 03 depends on completion of 01 and 02
If you think any of these, STOP and re-read this skill:
| Excuse | Reality |
|---|---|
| "It's only 3-4 files, I don't need a breakdown" | 3-4 files = multiple subtasks with dependencies. Skipping tracking means losing progress on failure. |
| "I'll track it in my head" | Subagents don't share memory. JSON files are the only reliable state. |
| "The tasks are obvious, no need to document them" | Obvious tasks still need acceptance criteria. "Done" without binary criteria is not done. |
| "Parallel execution isn't worth it for this" | Parallel tasks cut execution time in half. The JSON overhead is 2 minutes. The time saving is 20+. |
context_files = standards ONLY, reference_files = source code ONLYparallel: trueTask: Break down this feature into atomic subtasks: $ARGUMENTS