From taches-principled
A3-format problem analysis with root cause investigation and action plan. Use when user says 'analyze this problem', 'root cause', 'why is this happening', or 'figure out what's wrong'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/taches-principled:analyse-problem [problem description]When to use
Use when the user says "analyze this problem", "root cause", "why is this happening", or "figure out what's wrong". IMMEDIATELY when debugging incidents, recurring issues, or systemic failures that need structured investigation. Do NOT use for general code quality (use analyse), for ongoing issues without a specific incident (use root-cause-analysis), or when the problem is already well-understood.
[problem description]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
IF investigating a recurring issue, incident, or major improvement opportunity → produce a complete A3 analysis
IF investigating a recurring issue, incident, or major improvement opportunity → produce a complete A3 analysis IF the problem is a trivial one-line fix or minor bug → skip (A3 is designed for significant, recurring, or systemic issues) IF deeper root cause work is needed → use Five Whys or Fishbone analysis within section 4 of the template IF the situation evolves during investigation → update the A3 as a living document until closure
Structured one-page problem documentation and resolution planning using the A3 format — named after the paper size that constrains analysis to concise, complete thinking.
Force complete, concise root-cause-to-resolution thinking onto a single page. If it doesn't fit, the problem isn't well enough understood yet.
An A3 document covering the full problem lifecycle: background, current state, goal, root cause, countermeasures, implementation plan, and follow-up. Written to conversation. Can be used as a historical record for organizational learning.
TITLE: [Concise problem statement]
1. BACKGROUND — Why this matters
2. CURRENT CONDITION — What's happening (data, not opinions)
3. GOAL/TARGET — Specific, measurable targets
4. ROOT CAUSE ANALYSIS — Five Whys or Fishbone
5. COUNTERMEASURES — Actions tied to root causes
6. IMPLEMENTATION PLAN — Who, what, when, dependencies
7. FOLLOW-UP — Success metrics, monitoring, review dates
The A3 paper size is the forcing function. If the analysis genuinely requires more space, the problem scope is too broad — decompose into sub-problems and produce multiple A3s.
Section 5 must reference section 4 explicitly. Every countermeasure must trace to a specific root cause. This prevents treating symptoms.
The A3 should be updated as understanding grows or the situation changes. Only close it when the follow-up metrics confirm success and prevention measures are in place.
npx claudepluginhub git-fg/taches-principledProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.