Frame stakeholder requests with 5 Whys analysis and solution options.
npx skills add https://github.com/pelletencate/iron-horse --skill frame-problem
Please help me install this Agent Skill. Skill: frame-problem Source: https://github.com/pelletencate/iron-horse/tree/main/skills/frame-problem Command: npx skills add https://github.com/pelletencate/iron-horse --skill frame-problem
Frame problems and guide solution discovery to avoid XY problems before coding. It helps teams translate vague stakeholder requests into clearly defined problems and actionable plans, surfacing root needs and potential misdirections early in the process.
Describe the stakeholder request and run the framing process before starting any implementation.
High-intent search queries and answers about installing and using this skill.
Use problem framing before coding to translate vague stakeholder requests into clearly defined objectives. Document the raw request, perform 5 Whys root-cause analysis, and generate multiple solution options with trade-offs to surface true needs early.
The 5 Whys analysis is a root-cause identification technique used during problem framing to iteratively ask why a stakeholder request exists, revealing the true underlying need and preventing misdirected solution implementation.
Translate vague feature requests by documenting the raw request, analyzing the existing codebase for gaps, classifying the problem type, and delivering a recommended approach alongside a draft specification for implementation.
The best way to evaluate solution options is through option-driven planning, which generates multiple solution paths with explicit trade-offs and recommends an approach, mitigating risks and improving feature scoping before development starts.
You need problem framing and codebase analysis before coding, during feature requests, or when stakeholder needs are unclear, ensuring the discovery and analysis phases align the proposed solution with the actual root cause.
reckerswartzFrame ambiguous stakeholder requests into problem statements and architectural options.
einargudnigCreates non-code design plans with options, tradeoffs, and validation.
ComputerConnectionDesign feature-driven system architectures with trade-offs and implementation plans.
ilandahanGuide Tech Lead teams through architecture decisions and code review criteria.
