specflow-bugslisted

Diagnose bugs in a Specflow-managed project by walking the spec-model diagnostic tree to find the root cause layer, classify the bug type, file it in the bug ledger (.cortex/compass/bugs/), and produce a concrete change plan for the change-router to execute. Use this skill whenever the user reports a bug, describes unexpected behavior, says something is broken or wrong, or when a test failure needs triage. PROACTIVELY use this skill when you encounter: "X doesn't work", "X returns wrong result", "X crashes", "this test is failing", "the behavior should be Y but it's Z", "why does X happen", error messages, 500s, wrong data, missing responses, or any report where implemented behavior diverges from expected behavior. Also trigger when test runs produce failures that need classification — the skill handles both human-reported bugs and automated test failure triage. If a .specflow/specs/ directory exists and the user reports something broken, this skill runs first — it diagnoses before anyone touches code.
pedropacheco95/cortex · ★ 1 · Testing & QA · score 74

Install: claude install-skill pedropacheco95/cortex

# Specflow: Bug Diagnosis ## Core Principle In a spec-managed project, a bug is never just "wrong code." Every bug is a signal that something upstream in the spec model is incomplete or incorrect. Code is a derived artifact — if it's wrong, the specification that generated it was wrong or missing. **This skill diagnoses. It does not fix.** The output is a classified bug file in the ledger — `.cortex/compass/bugs/B-NNN-<slug>.md` — with a concrete change plan. The change-router executes the plan. **"Just fix the code" never happens.** Every fix starts at the spec layer, flows through acceptance criteria, through tests, and only then touches code. The code change is always the last step. ## When This Skill Activates Two entry points: 1. **Human-reported bug.** The user says something is broken, wrong, or unexpected. The skill walks the diagnostic tree, classifies, documents, and produces the change plan. 2. **Test failure triage.** A test run produced failures. The skill reads the failure output, identifies which spec and criterion each failure maps to, classifies the root cause, and produces the change plan for each failure. ## The Seven Bug Types Every bug in a Specflow project traces to exactly one of these root causes: | Type | Root Cause | What's Missing/Wrong | |------|-----------|---------------------| | 1 | Missing acceptance criterion | Spec and rule exist, but no Given/When/Then covers this case | | 2 | Incomplete rule | Spec exists, but a rule is