decompose-tasks

decompose-tasks is a skill for Claude Code, Codex from pilotspace/pilot-space. It costs 16 tokens per session (2,385 once invoked), scanned A, original, Apache-2.0.

A task-planning aid that breaks a complex issue into subtasks, dependencies, and estimates.

In plain words
What is it for?
Use it for large features, complex issues, or requests to decompose work across database, backend, frontend, and testing tasks.
Why use it?
It turns a large request into an ordered work graph, showing which tasks can run in parallel and which must wait.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/pilotspace/pilot-space/decompose-tasks
Any agent
npx skills add pilotspace/pilot-space --skill decompose-tasks
Clone the repo
git clone --depth 1 https://github.com/pilotspace/pilot-space

Made for: Claude Code, Codex.

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 decompose-tasks

README.md
[![agentmods](https://agentmods.dev/badge/skills/pilotspace/pilot-space/decompose-tasks.svg)](https://agentmods.dev/skills/pilotspace/pilot-space/decompose-tasks)
Your own site
<a href="https://agentmods.dev/skills/pilotspace/pilot-space/decompose-tasks"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/decompose-tasks.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,385 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00016 $0.02385
Opus 5 $0.00008 $0.01192
Sonnet 5 $0.00003 $0.00477
Haiku 4.5 $0.00002 $0.00238

Measured 3d ago against content hash 227693d1467e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

decompose-tasks 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 3d 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.

backend/src/pilot_space/ai/templates/skills/decompose-tasks/SKILL.md · 329 lines

How it starts

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

Decompose Tasks Skill

Automatically break down complex issues into actionable subtasks with dependencies and estimates.

Quick Start

Use this skill when:

  • Large feature needs breakdown into subtasks
  • User requests task decomposition (/decompose-tasks)
  • Issue is too complex for single assignee

Example:

Issue: "Implement user authentication system"

AI decomposes into:
1. Design database schema for users/sessions (2 days, no dependencies)
2. Implement JWT token generation (1 day, depends on #1)
3. Create login/logout API endpoints (2 days, depends on #2)
4. Add frontend login form (1 day, depends on #3)
5. Write integration tests (1 day, depends on #3, #4)

Workflow

  1. Analyze Issue Scope

    • Parse description for distinct components
    • Identify technical layers (DB, API, Frontend, Tests)
    • Detect implied tasks from acceptance criteria
  2. Generate Subtask Graph

    • Decomposition Strategy:
      • Backend features: DB schema → API → Tests
      • Frontend features: Component → State → Styling → Tests
      • Full-stack: Backend → Frontend → Integration
    • Identify parallel vs sequential tasks
    • Build dependency graph (DAG)
  3. Estimate Complexity

    • Small (0.5-1 day): Simple implementation, single file
    • Medium (1-3 days): Multiple files, standard patterns
    • Large (3-5 days): Cross-cutting changes, new architecture
  4. Tag Confidence

    • RECOMMENDED: Standard decomposition for known patterns
    • DEFAULT: General breakdown, may need refinement
    • ALTERNATIVE: Multiple valid approaches, team choice

Output Format

{
  "subtasks": [
    {
      "order": 1,
      "name": "Design user database schema",
      "description": "Create users, sessions, and refresh_tokens tables with proper indexes",
      "confidence": "RECOMMENDED",
      "estimated_days": 2,
      "labels": ["backend", "database"],
      "dependencies": [],
      "acceptance_criteria": [
        "Schema supports email and OAuth login",
        "Indexes on email and session_token fields",
        "Migration script tested"
      ],
      "code_references": [
        {
          "file": "backend/src/pilot_space/infrastructure/database/models/user.py",
          "lines": "1-50",
          "description": "Existing User model to extend",
          "badge": "Model"
        },
        {
          "file": "backend/alembic/versions/",
          "description": "Migration directory for new schema",
          "badge": "Migration"
        }
      ],
      "ai_prompt": "Create database schema for user sessions with proper indexes.\n\n## Context\nIssue: AUTH-42 - Implement user authentication system\nAdd support for both email and OAuth login with session management.\n\n## Requirements\n- Create users, sessions, and refresh_tokens tables\n- Add indexes on email and session_token fields\n- Write migration script for schema changes\n\n## Acceptance Criteria\n- [x] Schema supports email and OAuth login\n- [x] Indexes on email and session_token fields\n- [x] Migration script tested\n\n## Files to Reference\n- `backend/src/pilot_space/infrastructure/database/models/user.py` (lines 1-50) - Existing User model to extend\n- `backend/alembic/versions/` - Migration directory for new schema\n\n## Technical Constraints\n- Use SQLAlchemy 2.0 async\n- Follow repository pattern\n- Ensure RLS policies for multi-tenant isolation"
    },
    {
      "order": 2,
      "name": "Implement JWT token service",
      "description": "Create service for generating and validating JWT access/refresh tokens",
      "confidence": "RECOMMENDED",
      "estimated_days": 1,
      "labels": ["backend", "security"],
      "dependencies": [1],
      "acceptance_criteria": [
        "Access tokens expire after 15 minutes",
        "Refresh tokens stored in database",
        "Token validation handles expired tokens"
      ]
    },
    {
      "order": 3,
      "name": "Create login/logout API endpoints",
      "description": "POST /auth/login and POST /auth/logout endpoints with proper error handling",
      "confidence": "RECOMMENDED",
      "estimated_days": 2,
      "labels": ["backend", "api"],
      "dependencies": [2],
      "acceptance_criteria": [
        "Login returns access and refresh tokens",
        "Logout invalidates refresh token",
        "Rate limiting applied (5 attempts/minute)"
      ]
    },
    {
      "order": 4,
      "name": "Build login form component",
      "description": "React login form with email/password validation and error display",
      "confidence": "RECOMMENDED",
      "estimated_days": 1,
      "labels": ["frontend", "react"],
      "dependencies": [3],
      "can_parallel_with": [],
      "acceptance_criteria": [
        "Form validates email format client-side",
        "Displays backend error messages",
        "Redirects to dashboard on success"
      ]
    },
    {
      "order": 5,
      "name": "Write authentication integration tests",
      "description": "End-to-end tests for full login/logout flow",
      "confidence": "RECOMMENDED",
      "estimated_days": 1,
      "labels": ["testing"],
      "dependencies": [3, 4],
      "acceptance_criteria": [
        "Tests cover happy path and error cases",
        "Tests verify token persistence",
        "Tests check session expiration"
      ]
    }
  ],
  "summary": "Decomposed into 5 subtasks, estimated 7 days total",
  "critical_path": [1, 2, 3, 4],
  "parallel_opportunities": ["#4 and #5 can start after #3"]
}

Read the full file on GitHub · 329 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. 3d ago First seen · 329 lines · 16 tokens per session scan A 227693d1467e

Subscribe to this mod's changes

decompose-tasks is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 2,385 once invoked, about $0.0001 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

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens