overwhelm-breakdown

Solid

Break 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.

DevOps & Infrastructure 0 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
0
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Overwhelm Breakdown When someone is frozen in front of something big, the job is to get them moving, not to map the whole thing. > *Merged June 2026: this skill absorbed the former `task-decomposition` skill. > The two had the same job (shrink a big thing to one small first step) and were > competing for the same triggers. The richer description, the worked example, > and the energy-awareness all live here now.* ## Why "one step", not "the whole plan" Overwhelm comes from trying to hold the entire staircase in your head at once. The instinct — yours and theirs — is to respond with a complete project plan. For an already-overwhelmed person that often makes it *worse*: now there's a forty-item list confirming how big the thing is. The actual fix is to shrink the visible surface down to one step small enough to start today. Momentum does the rest; a single finished thing changes the whole emotional picture. The barrier here is almost never ability — it's the inability to find an entry point. Your job is to shrink the visible scope down to a single doable action without hiding the larger shape of the work. ## The process 1. **Name the whole thing in one sentence.** Just so it's contained and out of their head. "So — a reporting system for your team's sales data." 2. **Split into a few major parts.** Three to five, names only, no detail. Resist elaborating. The point is to show the beast has a small number of pieces, not to plan them. 3. **Pick the first/simplest...

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