Results for “5-whys”

1.

Structured root cause analysis for arriving at a concrete action. Use when something went wrong, a pattern keeps recurring, behavior has drifted, or you catch yourself resolving to "do better" / "remember to X" without a concrete artifact. Five-whys forces behavioral resolutions into file edits, config changes, memory block updates, or scheduled jobs — the action item must produce a diff someone else can verify. Do not use for simple debugging with an obvious cause.

Explain any concept in plain words with one concrete analogy - clear enough for a smart child or a busy outsider, never condescending, never wrong.

A complete tour of the intelli-verse-x 5-layer stack — Leantime/GitHub at the top, Beads/Bernstein/Claude-Squad in the middle, Gas Town as the multi-project fabric, and LiteLLM/Infisical/Langfuse/n8n/GH-Actions underneath. Use whenever the user asks "what does X service do", "where does Y data live", "how do I get to Z", or you need to understand which tool to reach for. This is the architecture map.

Analyzes why a piece of content resonates with audiences using five classic communication theories, identifies the emotional core and effective stance, and outputs discussion directions for a chatroom.

Use this skill when the user asks about driver fitness-for-duty programs — pre-trip readiness assessment, recognizing impairment from drugs/alcohol/medication/fatigue/mental health, refusing assignments when unfit, supervisor training on fitness assessment, FMCSA recommendations on duty status determination, and how to handle a driver who appears unfit. Reference 49 CFR 392.3 + 392.4.

Design reading plans with retention strategies. TRIGGERS - Use when user needs help with reading-plan related tasks.

Translate a vague request or GitHub issue into a concrete, testable spec using five structured elements (problem, scope, acceptance criteria, edge cases, success criterion) before writing any code. Prevents scope creep, PR churn, and mid-implementation pivots.

当需要系统性地提升工作专注度和生产力，实现高质量成果时

Plan gala events with programming and fundraising. TRIGGERS - Use when user needs help with gala-plan related tasks.

Write the executable feature specification — the WHAT and WHY artifact that agents and reviewers treat as source of truth. Owns both /specify and /clarify modes. Load when the user asks to write a feature spec, write a specification, write an executable spec, define functional requirements, capture acceptance criteria as Given/When/Then, or when the spec-driven-development orchestrator routes here. Also triggers on "feature spec", "executable spec", "/specify", "/clarify", "write the spec for this feature", "specification for", "spec-driven", "machine-readable spec". Output: docs/specs/YYYY-MM-DD-<slug>-feature-spec.md. Hard gate: cannot Approve while [NEEDS CLARIFICATION] markers remain.

Applies four disciplined mindsets—audit, debt, help, review—to cut complexity, track deferrals, surface reference, and catch over-engineering in codebases.

Write leave policies covering PTO, sick, and family leave. TRIGGERS - Use when user needs help with leave-policy related tasks.

Challenge decisions, surface counter-arguments, flag assumptions. Trigger: 'should I', 'is this right', 'critique', 'poke holes', 'second opinion', 'devil's advocate'. Auto-fired by ijfw-intent-router.

CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use for CAPA investigations, 5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization.

Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)

Write policy briefs with analysis and recommendations. TRIGGERS - Use when user needs help with policy-brief related tasks.

Create game plans with strategy and tactics. TRIGGERS - Use when user needs help with game-plan related tasks.

Plan gala events with programming and fundraising. TRIGGERS - Use when user needs help with gala-plan related tasks.

Helps find and analyze competitors to imitate using a five-filter method, focusing on profitability and feasibility while eliminating personal bias.

Write leave policies covering PTO, sick, and family leave. TRIGGERS - Use when user needs help with leave-policy related tasks.