What is problem-definition?

A guide for writing a precise problem statement using 5W2H—what, why, where, when, who, how, and how much—and IS/IS NOT comparisons. RCCA and 8D are structured methods for investigating problems and corrective actions.

Use it to define problems for root-cause investigations, 8D reports, nonconformances, failures, and corrective-action work.

It turns scattered failure information into a measurable description without assuming the cause or solution. This keeps an investigation focused on the actual boundaries of the problem.

problem-definition — Plugin by ddunnock

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Claude Code

/plugin marketplace add ddunnock/claude-plugins

agentmods

npx agentmods add plugins/ddunnock/claude-plugins/problem-definition

Clone the repo

git clone --depth 1 https://github.com/ddunnock/claude-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

problem-definition scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/problem-definition/.claude-plugin/plugin.json · 18 lines

What it actually says

{
  "name": "problem-definition",
  "description": "Guide RCCA/8D problem definition using 5W2H and IS/IS NOT analysis. Transforms scattered failure data into precise, measurable problem statements that bound investigation scope without embedding cause or solution. Use when defining problems for root cause analysis, writing D2 sections of 8D reports, analyzing nonconformances, investigating failures, or when user mentions problem definition, problem statement, RCCA, 8D, failure analysis, or corrective action.",
  "version": "1.0.2",
  "author": {
    "name": "dunnock"
  },
  "keywords": [
    "problem-definition",
    "5w2h",
    "is-is-not",
    "rcca",
    "8d",
    "d2",
    "problem-statement"
  ]
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 18 lines scan A 2cd47462e4b6

Subscribe to this mod's changes

problem-definition is a plugin published in the GitHub repository ddunnock/claude-plugins (12 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Data and AI Debugging Writing and docs

problem-definition

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins

ecc

ecc