overwhelm-breakdown
SolidBreak an overwhelming project — or any large, vague task someone can't find an entry point into — down to a single concrete next step. Use whenever someone faces something big and signals they're stuck or overwhelmed: "I need to build a whole reporting system but I don't know where to start", "this feels like too much", "where do I even begin with X", "I'm drowning in this project", "can you break this down", "chunk it for me", "I'm paralyzed by the size of this". The goal is momentum, not a master plan: decompose into a few major parts, then collapse all the way down to one doable step sized by time AND energy, with a clear definition of done for today. Trigger on the combination of a large or ambiguous task PLUS stuck-ness, overwhelm, or an explicit request to break the work down — even if the person never uses the words "overwhelm" or "breakdown". Do NOT use this to produce a full project plan — that's the opposite of what an overwhelmed person needs.
Install
Quality Score: 78/100
Skill Content
Details
- Author
- scoobydrew83
- Repository
- scoobydrew83/skills
- Created
- 1 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
task-decomposition
DEPRECATED — this skill was merged into `overwhelm-breakdown` on 2026-06-16 because the two were competing for the same triggers. Do NOT trigger this skill. If you see this description matching a user request, use `overwhelm-breakdown` instead — it now covers "I'm overwhelmed, where do I start?" alongside "break this big thing down for me", with the worked reporting-system example, the size-by-time-AND-energy guidance, and the "use real tools only" caution that used to live here. This tombstone exists only because the source file could not be deleted in the build environment; treat it as a no-op redirect.
breaking-driven
Demolish bloated code and re-derive it clean, cutting every surface the rebuilt contract does not name. Use for a repo-wide bloat sweep, when patching a subsystem has stopped paying, or when the user says "this whole module is bloated", "rewrite this properly", or "break it and rebuild".
task-decomposer
USE WHEN the user describes a vague goal ('build X', 'plan Y', 'figure out how to Z') that needs to be broken into concrete steps before any work can start. Produces an ordered task list with rough estimates, dependencies, and unknowns flagged.