[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDB33J1MBWX27WAJ6R402P":3,"skill-same:01M6MDB33J1MBWX27WAJ6R402P":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6MDB33J1MBWX27WAJ6R402P","five-whys",null,"Root cause analysis using the Five Whys technique. Use when a bug persists despite surface fixes, a failure recurs, or a process keeps breaking. Ensures the fix targets the root, not the symptom.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Ffive-whys\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"five whys","root cause analysis","analysis","fix","process","use","bug","targets","root","fixes","root cause","when","2026-11-10 10:12:30",false,"---\nname: five-whys\ndescription: Root cause analysis using the Five Whys technique. Use when a bug persists despite surface fixes, a failure recurs, or a process keeps breaking. Ensures the fix targets the root, not the symptom.\n---\n\n# Five Whys — Root Cause Analysis\n\n## The Rule\n\n```\nDO NOT FIX THE SYMPTOM. FIND THE CAUSE.\n```\n\nA fix that doesn't address the root cause is temporary. The cause returns.\n\n## Protocol\n\n### Step 1 — Define the problem precisely\n\nOne concrete sentence. Not vague.\n\n| Wrong | Correct |\n|-------|---------|\n| \"The system is slow\" | \"GET \u002Forders exceeds 3s for 90% of requests in prod since Friday\" |\n| \"Tests fail sometimes\" | \"test_payment_flow fails in CI roughly 1 in 20 runs with no clear error message\" |\n\n### Step 2 — Five Whys cascade\n\nFor each answer, ask: **\"Why does that happen?\"**\n\nDon't stop until you reach something you control — a decision, a process, a line of code, a missing configuration.\n\n```\nProblem: Users see another user's data\n  Why 1: Cache returns the wrong entry\n  Why 2: Cache key does not include user_id\n  Why 3: Developer assumed the endpoint was public\n  Why 4: No isolation test existed for this endpoint\n  Why 5: Code review had no data isolation checklist\n  → Root cause: review process missing a security checklist\n```\n\n### Step 3 — Validate in reverse\n\nRead the chain bottom-up: \"No review checklist → cache key missing user_id → data leak.\" If the chain holds, the root cause is valid.\n\n### Step 4 — Fix at the root, not the symptom\n\nFix at the deepest level that is practical to change.\n\n| Fix level | Example | Durability |\n|-----------|---------|------------|\n| Symptom | Manually flush cache | Hours |\n| Proximate cause | Add user_id to cache key | Days |\n| Root cause | Add isolation checklist to review | Permanent |\n\nIf you can only fix an intermediate level, document the root cause as tracked technical debt with a concrete TODO.\n\n## Branching\n\nA root cause can have multiple branches — explore all before choosing where to fix.\n\n```\nProblem: Deploy fails in prod but not in staging\n  Branch A: different configuration (env vars, secrets)\n  Branch B: prod data has different volume or format\n  Branch C: network dependencies only reachable in prod\n```\n\nTest each branch independently. Do not assume.\n\n## When to Stop\n\nStop before the 5th why if you reach a clear, actionable root cause. Stop after the 5th if the chain hasn't converged — there may be multiple independent root causes.\n\n## Output\n\nDocument the analysis:\n\n```markdown\n**Problem:** [concrete one-liner]\n**Root cause:** [deepest level found]\n**Fix:** [concrete action with file\u002Fcomponent]\n**Temporary fix (if needed):** [what you apply now while the real fix is in progress]\n**Technical debt:** [what remains unresolved and why]\n```\n\n## Integration with A Team\n\n- Run this skill **before** launching the `systematic-debugging` agent — Five Whys defines the investigation scope\n- After finding the root cause, use the `tdd-guide` agent to write the test that would have caught it\n- If the root cause implies a process change, document the analysis in `DAILY.md`\n","# Five Whys — Root Cause Analysis\n\n## The Rule\n\n```\nDO NOT FIX THE SYMPTOM. FIND THE CAUSE.\n```\n\nA fix that doesn't address the root cause is temporary. The cause returns.\n\n## Protocol\n\n### Step 1 — Define the problem precisely\n\nOne concrete sentence. Not vague.\n\n| Wrong | Correct |\n|-------|---------|\n| \"The system is slow\" | \"GET \u002Forders exceeds 3s for 90% of requests in prod since Friday\" |\n| \"Tests fail sometimes\" | \"test_payment_flow fails in CI roughly 1 in 20 runs with no clear error message\" |\n\n### Step 2 — Five Whys cascade\n\nFor each answer, ask: **\"Why does that happen?\"**\n\nDon't stop until you reach something you control — a decision, a process, a line of code, a missing configuration.\n\n```\nProblem: Users see another user's data\n  Why 1: Cache returns the wrong entry\n  Why 2: Cache key does not include user_id\n  Why 3: Developer assumed the endpoint was public\n  Why 4: No isolation test existed for this endpoint\n  Why 5: Code review had no data isolation checklist\n  → Root cause: review process missing a security checklist\n```\n\n### Step 3 — Validate in reverse\n\nRead the chain bottom-up: \"No review checklist → cache key missing user_id → data leak.\" If the chain holds, the root cause is valid.\n\n### Step 4 — Fix at the root, not the symptom\n\nFix at the deepest level that is practical to change.\n\n| Fix level | Example | Durability |\n|-----------|---------|------------|\n| Symptom | Manually flush cache | Hours |\n| Proximate cause | Add user_id to cache key | Days |\n| Root cause | Add isolation checklist to review | Permanent |\n\nIf you can only fix an intermediate level, document the root cause as tracked technical debt with a concrete TODO.\n\n## Branching\n\nA root cause can have multiple branches — explore all before choosing where to fix.\n\n```\nProblem: Deploy fails in prod but not in staging\n  Branch A: different configuration (env vars, secrets)\n  Branch B: prod data has different volume or format\n  Branch C: network dependencies only reachable in prod\n```\n\nTest each branch independently. Do not assume.\n\n## When to Stop\n\nStop before the 5th why if you reach a clear, actionable root cause. Stop after the 5th if the chain hasn't converged — there may be multiple independent root causes.\n\n## Output\n\nDocument the analysis:\n\n```markdown\n**Problem:** [concrete one-liner]\n**Root cause:** [deepest level found]\n**Fix:** [concrete action with file\u002Fcomponent]\n**Temporary fix (if needed):** [what you apply now while the real fix is in progress]\n**Technical debt:** [what remains unresolved and why]\n```\n\n## Integration with A Team\n\n- Run this skill **before** launching the `systematic-debugging` agent — Five Whys defines the investigation scope\n- After finding the root cause, use the `tdd-guide` agent to write the test that would have caught it\n- If the root cause implies a process change, document the analysis in `DAILY.md`\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Ffive-whys",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill five-whys",{"tool":52,"command":53},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill five-whys",{"tool":55,"command":56},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill five-whys","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Ffive-whys\u002FSKILL.md",true,[],[61,71,79,87,95,103],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":70},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":70},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":70},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":70},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":70},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":70},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]