problem-decomposer

Decompose ambiguous problems into work plans with acceptance criteria.

2|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/AllanYiin/Amon --skill problem-decomposer-allanyiin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-decomposer
Source: https://github.com/AllanYiin/Amon/tree/main/src/amon/resources/skills/problem-decomposer
Command: npx skills add https://github.com/AllanYiin/Amon --skill problem-decomposer-allanyiin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill translates large, ambiguous problems into a structured, actionable plan by clearly framing the gap, identifying root causes, and outlining deliverables and acceptance criteria.

Core Features & Use Cases

  • MECE/Issue Tree framing to isolate root causes and verify assumptions.
  • WBS-style work packages with DoD/AC, dependencies, and delivery criteria.
  • Systemic thinking to map feedback loops, delays, and leverage points.
  • Baseline/PoC planning for uncertain problems and Go/No-Go decision points.
  • Outcome-focused problem statements that align cross-functional teams.

Quick Start

Provide a concise description of the problem, its desired outcome, and any constraints to generate a complete executable problem decomposition.

Frequently Asked Questions about problem-decomposer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a large ambiguous problem into an actionable work plan?

Problem decomposition using a MECE issue tree isolates root causes by ensuring branches are mutually exclusive and collectively exhaustive. It maps feedback loops and leverage points to verify assumptions and frame cross-functional initiatives clearly.

How do I create a WBS with acceptance criteria for a cross-functional project?

Creating a WBS involves dividing the project into delivery-oriented work packages with clear Dependencies and Definition of Done. This ensures outcome-focused problem statements that align cross-functional teams for verifiable execution.

When do I need an issue tree for systemic root cause analysis?

Baseline and PoC planning handles uncertain problems by establishing Go/No-Go decision points. This approach maps dependencies and risk indicators before full execution, ensuring verifiable work packages align with strategic delivery criteria.

What is the best way to frame a strategic problem for cross-functional teams?

The best way to frame a strategic problem is creating an outcome-focused problem statement that aligns cross-functional teams. This translates ambiguous gaps into structured, verifiable work packages with clear dependency mapping and acceptance criteria.