spec-driven-rcalisted

Unified root cause analysis with 4-layer anti-skip enforcement for both tactical (dev workflow diagnosis) and strategic (5 Whys RCA documents) modes. Tactical mode auto-triggers after 2-3 failed fix attempts during TDD, returning fix prescriptions. Strategic mode invoked via /rca command, producing self-contained RCA documents with 5 Whys analysis, evidence collection, and actionable recommendations. Uses Execute-Verify-Record pattern at every step to prevent token optimization bias. Use this skill whenever root cause analysis is needed — after repeated test failures, integration failures, QA violations, framework breakdowns, workflow violations, or when the user runs /rca. Also use when the diagnosis-before-fix rule triggers after 3+ consecutive fix attempts on the same error.
bankielewicz/DevForgeAI · ★ 4 · AI & Automation · score 66

Install: claude install-skill bankielewicz/DevForgeAI

# Spec-Driven RCA Unified root cause analysis for the DevForgeAI framework. Operates in two modes: - **Tactical:** Fast diagnosis during dev workflow after repeated fix failures. Returns fix prescriptions. (Phases 00-03) - **Strategic:** Full 5 Whys RCA for framework breakdowns. Creates self-contained RCA documents. (Phases 00-02, 04-08) **Core Principle:** Understanding WHY a failure occurred is mandatory before attempting HOW to fix it. **If ambiguous or conflicts detected: HALT and use AskUserQuestion** --- ## Execution Model This skill expands inline. After invocation, execute Phase State Initialization immediately. Enforcement is mechanical (CLI gates, subagents, hooks) — see Anti-Skip Enforcement Contract below. Self-check exhortations are not the mechanism: hooks are. See **`.claude/rules/core/anti-skip-behavior.md`** for the canonical execution contract (Self-Check violation taxonomy; Token-Optimization-Bias prohibition; governed by ADR-076). --- ## Anti-Skip Enforcement Contract Enforced structurally outside LLM control, not by this prose — by the framework's deterministic gates wired for this workflow: the `devforgeai-validate` phase gates, the `settings.json`-registered `.claude/hooks/` scripts, and `.claude/hooks/phase-steps-registry.json` (ADR-076). Behavioral residue: `.claude/rules/core/anti-skip-behavior.md`. --- ## Validation Modes This skill operates in two modes, determined during Phase 00 Initialization. Context-marker extraction and mode-dete