Skip to main content
affpapa.org
RU EN
skill CX Codex

analyse-problem — Claude Code skill: A3 problem analysis

This skill turns a problem into a one-page A3 document: background, current condition, goal, root cause and an action plan.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add NeoLabHQ/context-engineering-kit --skill analyse-problem -a claude-code
Open on GitHub

What analyse-problem does

The skill walks the agent through seven sections: background and impact, current condition with facts and metrics, a measurable goal, root cause analysis via 5 Whys or a fishbone diagram, countermeasures, an implementation plan with owners and dates, and follow-up. Output is a single-page document in markdown or plain text, named after the A3 paper format.

Invoke it with /analyse-problem [problem_description]. Leave the description out and the skill asks for it. OUTPUT_FORMAT controls the output, markdown by default.

It earns its place when an incident keeps coming back and you want the cause, not another patch on the symptom. The catch: the skill needs data. The current condition section is built on facts and metrics, so without logs, measurements or examples the agent fills it with platitudes.

What it helps with

  • trace a recurring incident back to its root cause
  • write up a problem on one page for the team
  • separate facts and metrics from opinions when describing a failure
  • build an implementation plan with owners and dates
  • check that countermeasures target the cause, not the symptom

Example prompts for the agent

  • /analyse-problem API goes down 2-3 times a week during peak hours
  • /analyse-problem figure out why the build fails at the test stage
  • /analyse-problem response times keep growing, OUTPUT_FORMAT: text

How to install analyse-problem

1Skills CLI (Vercel)

npx skills add NeoLabHQ/context-engineering-kit --skill analyse-problem -a claude-code

2Manually: put the files in place

~/.claude/skills/analyse-problem/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/analyse-problem/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about analyse-problem

How do I install analyse-problem in Claude?

Run npx skills add NeoLabHQ/context-engineering-kit --skill analyse-problem -a claude-code. The skill lands in ~/.claude/skills/analyse-problem/SKILL.md.

What does analyse-problem do?

It runs an A3 problem analysis: background, current condition, goal, root cause, countermeasures, implementation plan and follow-up. Everything fits on one page.

What input does the analysis need?

Facts and metrics about the problem: logs, measurements, examples. Without them the current condition section stays empty and the analysis turns generic.

Similar skills

All skills for Agent setup: memory, context, orchestration →
problem-solving mrgoonie A collection of structured creative thinking techniques to unblock agent reasoning. Helps find clean abstractions when conventional coding solutions hit a dead end. CX Codex +1 570installs scientific-problem-selection official anthropics A skill that helps scientists structure research problem selection, from idea generation to navigating obstacles. Works through three entry points: pitch a new idea, troubleshoot a stuck project, or answer a strategic question. CX Codex +1 2,400installs systematic-debugging Hermes Agent (adapted from obra/superpowers) A four-phase skill that moves from a reproducible symptom to its root cause. Use it for test failures, build errors, integration issues, and unexpected behavior. CX Codex +1 471installs groove-utilities-task-analyse andreadellacorte Pulls tasks from your project backend and groups them by status, so you have something to write into daily memory. CX Codex +1 588installs sequential-thinking mrgoonie Breaks complex problems into iterative reasoning steps with dynamic scope and hypothesis branching. Built for architecture planning and deep debugging. CX Codex +1 1,800installs define-problem-statement product-on-purpose Builds a problem framing document: who feels the pain, what it costs the business, and which metrics will show success. CX Codex +1 816installs

From the same set55

analyse Selects a Kaizen technique for your target, running code exploration via Gemba Walk, workflow reviews with VSM, or waste audits using Muda. CX Codex +1 1,200installs judge The skill runs a two-stage review of work from the current conversation: one sub-agent sets the criteria, another scores the result with evidence. CX Codex +1 1,200installs add-task Turns your request into a task file under .specs/tasks/draft/, with a verb-first title, a type and your original wording. The first step of a spec-driven workflow. CX Codex +1 1,200installs do-in-parallel Runs isolated tasks across separate files concurrently via sub-agents and validates work with automated judges. Fits batch refactoring and doc generation. CX Codex +1 1,200installs setup-serena-mcp Step-by-step assistant workflow to configure the Serena MCP server for semantic code exploration and symbol editing. CX Codex +1 1,200installs write-tests The skill reads your uncommitted and untracked git changes and writes tests for them. Useful when the logic is done but coverage is not. CX Codex +1 1,200installs why Conducts iterative Five Whys root cause analysis for technical bugs and incidents. Helps uncover process and system gaps instead of settling for superficial patches. CX Codex +1 1,200installs review-local-changes Reviews uncommitted working-tree changes and returns a list of issues with improvement suggestions. Handy right before you commit. CX Codex +1 1,200installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor