analyse-problem

Name: analyse-problem
Author: NeoLabHQ

865installs132forks

How to install analyse-problem?

neolabhq/context-engineering-kit/analyse-problem

$npx -y skills add NeoLabHQ/context-engineering-kit --skill analyse-problem

Installs into the current project.

Summary

Comprehensive A3 one-page problem analysis with root cause and action plan

Files · 1

View on GitHub

SKILL.md

1	# A3 Problem Analysis
2
3	Apply A3 problem-solving format for comprehensive, single-page problem documentation and resolution planning.
4
5	## Description
6	Structured one-page analysis format covering: Background, Current Condition, Goal, Root Cause Analysis, Countermeasures, Implementation Plan, and Follow-up. Named after A3 paper size; emphasizes concise, complete documentation.
7
8	## Usage
9	`/analyse-problem [problem_description]`
10
11	## Variables
12	- PROBLEM: Issue to analyze (default: prompt for input)
13	- OUTPUT_FORMAT: markdown or text (default: markdown)
14
15	## Steps
16	1. Background: Why this problem matters (context, business impact)
17	2. Current Condition: What's happening now (data, metrics, examples)
18	3. Goal/Target: What success looks like (specific, measurable)
19	4. Root Cause Analysis: Why problem exists (use 5 Whys or Fishbone)
20	5. Countermeasures: Proposed solutions addressing root causes
21	6. Implementation Plan: Who, what, when, how
22	7. Follow-up: How to verify success and prevent recurrence
23
24	## A3 Template
25
26	```
27	═══════════════════════════════════════════════════════════════
28	A3 PROBLEM ANALYSIS
29	═══════════════════════════════════════════════════════════════
30
31	TITLE: [Concise problem statement]
32	OWNER: [Person responsible]
33	DATE: [YYYY-MM-DD]
34
35	┌─────────────────────────────────────────────────────────────┐
36	│ 1. BACKGROUND (Why this matters) │
37	├─────────────────────────────────────────────────────────────┤
38	│ [Context, impact, urgency, who's affected] │
39	└─────────────────────────────────────────────────────────────┘
40
41	┌─────────────────────────────────────────────────────────────┐
42	│ 2. CURRENT CONDITION (What's happening) │
43	├─────────────────────────────────────────────────────────────┤
44	│ [Facts, data, metrics, examples - no opinions] │
45	└─────────────────────────────────────────────────────────────┘
46
47	┌─────────────────────────────────────────────────────────────┐
48	│ 3. GOAL/TARGET (What success looks like) │
49	├─────────────────────────────────────────────────────────────┤
50	│ [Specific, measurable, time-bound targets] │
51	└─────────────────────────────────────────────────────────────┘
52
53	┌─────────────────────────────────────────────────────────────┐
54	│ 4. ROOT CAUSE ANALYSIS (Why problem exists) │
55	├─────────────────────────────────────────────────────────────┤
56	│ [5 Whys, Fishbone, data analysis] │
57	└─────────────────────────────────────────────────────────────┘
58
59	┌─────────────────────────────────────────────────────────────┐
60	│ 5. COUNTERMEASURES (Solutions addressing root causes) │
61	├─────────────────────────────────────────────────────────────┤
62	│ [Specific actions, not vague intentions] │
63	└─────────────────────────────────────────────────────────────┘
64
65	┌─────────────────────────────────────────────────────────────┐
66	│ 6. IMPLEMENTATION PLAN (Who, What, When) │
67	├─────────────────────────────────────────────────────────────┤
68	│ [Timeline, responsibilities, dependencies, milestones] │
69	└─────────────────────────────────────────────────────────────┘
70
71	┌─────────────────────────────────────────────────────────────┐
72	│ 7. FOLLOW-UP (Verification & Prevention) │
73	├─────────────────────────────────────────────────────────────┤
74	│ [Success metrics, monitoring plan, review dates] │
75	└─────────────────────────────────────────────────────────────┘
76
77	═══════════════════════════════════════════════════════════════
78	```
79
80	## Examples
81
82	### Example 1: Database Connection Pool Exhaustion
83
84	```
85	═══════════════════════════════════════════════════════════════
86	A3 PROBLEM ANALYSIS
87	═══════════════════════════════════════════════════════════════
88
89	TITLE: API Downtime Due to Connection Pool Exhaustion
90	OWNER: Backend Team Lead
91	DATE: 2024-11-14
92
93	┌─────────────────────────────────────────────────────────────┐
94	│ 1. BACKGROUND │
95	├─────────────────────────────────────────────────────────────┤
96	│ • API goes down 2-3x per week during peak hours │
97	│ • Affects 10,000+ users, average 15min downtime │
98	│ • Revenue impact: ~$5K per incident │
99	│ • Customer satisfaction score dropped from 4.5 to 3.8 │
100	│ • Started 3 weeks ago after traffic increased 40% │
101	└─────────────────────────────────────────────────────────────┘
102
103	┌─────────────────────────────────────────────────────────────┐
104	│ 2. CURRENT CONDITION │
105	├─────────────────────────────────────────────────────────────┤
106	│ Observations: │
107	│ • Connection pool size: 10 (unchanged si

People who liked this also viewed

6 picks

Type

azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026472k1.3k
systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026197k259k
safe-debugRigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training SkillsMay 2026161k507
explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026161k507
minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026161k507
insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 202618k31

analyse-problem

865installs132forks

View on GitHub

How to install analyse-problem?

neolabhq/context-engineering-kit/analyse-problem

$npx -y skills add NeoLabHQ/context-engineering-kit --skill analyse-problem

Installs into the current project.

Summary

Comprehensive A3 one-page problem analysis with root cause and action plan

Files · 1

View on GitHub

SKILL.md

1	# A3 Problem Analysis
2
3	Apply A3 problem-solving format for comprehensive, single-page problem documentation and resolution planning.
4
5	## Description
6	Structured one-page analysis format covering: Background, Current Condition, Goal, Root Cause Analysis, Countermeasures, Implementation Plan, and Follow-up. Named after A3 paper size; emphasizes concise, complete documentation.
7
8	## Usage
9	`/analyse-problem [problem_description]`
10
11	## Variables
12	- PROBLEM: Issue to analyze (default: prompt for input)
13	- OUTPUT_FORMAT: markdown or text (default: markdown)
14
15	## Steps
16	1. Background: Why this problem matters (context, business impact)
17	2. Current Condition: What's happening now (data, metrics, examples)
18	3. Goal/Target: What success looks like (specific, measurable)
19	4. Root Cause Analysis: Why problem exists (use 5 Whys or Fishbone)
20	5. Countermeasures: Proposed solutions addressing root causes
21	6. Implementation Plan: Who, what, when, how
22	7. Follow-up: How to verify success and prevent recurrence
23
24	## A3 Template
25
26	```
27	═══════════════════════════════════════════════════════════════
28	A3 PROBLEM ANALYSIS
29	═══════════════════════════════════════════════════════════════
30
31	TITLE: [Concise problem statement]
32	OWNER: [Person responsible]
33	DATE: [YYYY-MM-DD]
34
35	┌─────────────────────────────────────────────────────────────┐
36	│ 1. BACKGROUND (Why this matters) │
37	├─────────────────────────────────────────────────────────────┤
38	│ [Context, impact, urgency, who's affected] │
39	└─────────────────────────────────────────────────────────────┘
40
41	┌─────────────────────────────────────────────────────────────┐
42	│ 2. CURRENT CONDITION (What's happening) │
43	├─────────────────────────────────────────────────────────────┤
44	│ [Facts, data, metrics, examples - no opinions] │
45	└─────────────────────────────────────────────────────────────┘
46
47	┌─────────────────────────────────────────────────────────────┐
48	│ 3. GOAL/TARGET (What success looks like) │
49	├─────────────────────────────────────────────────────────────┤
50	│ [Specific, measurable, time-bound targets] │
51	└─────────────────────────────────────────────────────────────┘
52
53	┌─────────────────────────────────────────────────────────────┐
54	│ 4. ROOT CAUSE ANALYSIS (Why problem exists) │
55	├─────────────────────────────────────────────────────────────┤
56	│ [5 Whys, Fishbone, data analysis] │
57	└─────────────────────────────────────────────────────────────┘
58
59	┌─────────────────────────────────────────────────────────────┐
60	│ 5. COUNTERMEASURES (Solutions addressing root causes) │
61	├─────────────────────────────────────────────────────────────┤
62	│ [Specific actions, not vague intentions] │
63	└─────────────────────────────────────────────────────────────┘
64
65	┌─────────────────────────────────────────────────────────────┐
66	│ 6. IMPLEMENTATION PLAN (Who, What, When) │
67	├─────────────────────────────────────────────────────────────┤
68	│ [Timeline, responsibilities, dependencies, milestones] │
69	└─────────────────────────────────────────────────────────────┘
70
71	┌─────────────────────────────────────────────────────────────┐
72	│ 7. FOLLOW-UP (Verification & Prevention) │
73	├─────────────────────────────────────────────────────────────┤
74	│ [Success metrics, monitoring plan, review dates] │
75	└─────────────────────────────────────────────────────────────┘
76
77	═══════════════════════════════════════════════════════════════
78	```
79
80	## Examples
81
82	### Example 1: Database Connection Pool Exhaustion
83
84	```
85	═══════════════════════════════════════════════════════════════
86	A3 PROBLEM ANALYSIS
87	═══════════════════════════════════════════════════════════════
88
89	TITLE: API Downtime Due to Connection Pool Exhaustion
90	OWNER: Backend Team Lead
91	DATE: 2024-11-14
92
93	┌─────────────────────────────────────────────────────────────┐
94	│ 1. BACKGROUND │
95	├─────────────────────────────────────────────────────────────┤
96	│ • API goes down 2-3x per week during peak hours │
97	│ • Affects 10,000+ users, average 15min downtime │
98	│ • Revenue impact: ~$5K per incident │
99	│ • Customer satisfaction score dropped from 4.5 to 3.8 │
100	│ • Started 3 weeks ago after traffic increased 40% │
101	└─────────────────────────────────────────────────────────────┘
102
103	┌─────────────────────────────────────────────────────────────┐
104	│ 2. CURRENT CONDITION │
105	├─────────────────────────────────────────────────────────────┤
106	│ Observations: │
107	│ • Connection pool size: 10 (unchanged si

People who liked this also viewed

6 picks

Type