Skill Detail
problem-decomposition
Breaking complex, ambiguous work into smaller executable parts with clear dependencies, sequencing, and ownership.
What problem it solves
Large ambiguous problems create paralysis because they hide the actual work inside a fog of uncertainty. problem-decomposition solves this by turning a vague objective into smaller parts that can be reasoned about, prioritized, and executed.
How it works
- •Clarify the real objective before splitting the problem apart.
- •Separate the work into subproblems with clean boundaries.
- •Identify dependencies, order of operations, and blocking unknowns.
- •Turn each subproblem into something actionable or researchable.
- •Use the decomposition to reduce ambiguity, not to create bureaucratic overhead.
Use case from logs
Breaking a production auth system into executable work
Context: A complete authentication build spanning OAuth2, JWT, RBAC, and production security is too large to execute well as one undifferentiated task.
What happened: The work was handled as a structured system build rather than a single request: security concerns, auth flows, implementation details, and review/refinement loops were separated into smaller pieces that could be iterated on together.
Outcome: That decomposition made it possible to move fast on a large surface area without losing architectural coherence.
Source
Pause in Collaboration — content/blog/pause-in-collaboration.md
A complete authentication system — 60+ files covering OAuth2, JWT, RBAC, production-ready security. The kind of system that takes most teams months. We did it in days, iterating together, arguing about implementation details, refining the architecture until it felt right.
GitHub
Code examples for this skill will link out to GitHub once the public repo is ready.