decompose-task
Task Decomposition
Analyze a task and decompose it into atomic, verifiable sub-tasks when scope exceeds ~100 lines.
When to Use
- Estimated >100 lines of code change
- Multiple unrelated files changing
- Multiple state transitions or new states
- Backend + frontend changes beyond contract sync
- Vague descriptions ("implement pipeline", "add full support")
Process
- Analyze scope: Read relevant files, estimate lines per area
- Identify boundaries: Find natural cut points (interfaces, modules, layers)
- Propose sub-tasks: Create checkbox list with line estimates
- Return proposal for human confirmation
More from b1tank/skills
market-research
Research existing products and competitors for a given product idea. Use when starting a new project, cloning an existing product, or analyzing competitive landscape. Returns feature analysis, gaps, and differentiation opportunities.
15diff-check
Author's cleanup checklist before committing or submitting a PR. Use before any commit or PR to ensure code is clean, focused, and ready for review. Checks for debug code, secrets, redundant changes, and scope creep.
13spec-template
9-section product specification template for defining software projects. Use when drafting a new spec.md, converting an idea into a structured specification, or reviewing spec completeness. Ensures consistent, comprehensive project definitions.
9skill-name
Clear description of what this skill does and when to use it. Include specific triggers and contexts for when Claude should invoke this skill.
5clone-with-hash
Clone a local or remote git repo into a new folder with a short random hash suffix (e.g., -a1b2c3) and immediately create a new branch from a base branch. Use when a user wants a separate workspace to avoid conflicts, especially for parallel feature work or multiple local clones.
2