What problem does it solve? Teams often jump straight into coding when handling feature requests or bug fixes, skipping root cause analysis and planning, which leads to recurring bugs, scope creep, and untested changes. This Skill enforces a mandatory, non-skippable gate sequence so every change is triaged, understood, planned, tested, and validated before it ships. ## Core Features & Use Cases - Six Mandatory Gates: Triage (classify the request), RCA/Research (find root cause), Brainstorm (compare 2-3 approaches), Plan (bite-sized tasks), TDD (failing test first), and E2E (validate against real systems). - Skip Rules with Guardrails: A clear table defines which gates can be skipped for trivial changes, while Triage and E2E can never be skipped. - Pitfall Prevention: Built-in guidance against common failure modes like fixing symptoms instead of root causes and relying on mocks that hide integration bugs. - Use Case: When a user reports "price sync failing on Lazada", the agent classifies it as a bug, traces the HTTP 429 rate limit root cause, compares retry vs. throttling approaches, writes a plan, implements via TDD, and verifies with a full sandbox sync. ## Quick Start Ask the agent to fix a bug or build a feature, and it will walk the request through triage, root cause analysis, brainstorming, planning, TDD, and end-to-end validation before writing any implementation code.
