Testing & Debugging Skills

Use when the user wants a comprehensive multi-issue health pass — fix all bugs, resolve broken tests, clear CI failures, fix lint and type errors, restore green builds — not for a single targeted bug fix. Diagnoses and resolves every outstanding open bug ticket plus all validation failures (test, lint, type, format, infrastructure) using orchestrated sub-agents with TDD discipline, in tier order. Trigger phrases include 'debug everything', 'fix all bugs', 'fix the failing tests', 'CI is failing', 'build is broken', 'clean up the codebase', 'restore green', 'project health pass'.

Use when debugging a visual bug, layout issue, CSS problem, rendering issue, broken UI, page-looks-wrong report, or any browser-visible defect. Enforces a 3-tier hypothesis-first process that minimizes @playwright/cli token usage — generates hypotheses from static code analysis (Tier 1), confirms them with targeted in-browser JS evidence (Tier 2, ≤3 run-code calls), and only escalates to full browser interaction (Tier 3) when prior tiers are exhausted. Trigger phrases include 'visual bug', 'layout issue', 'CSS problem', 'rendering issue', 'broken UI', 'the page looks wrong', 'screenshot regression', 'browser bug', 'frontend bug', 'why is this element off-screen'.

Use when breaking down an epic into user stories, story splitting, backlog grooming, defining acceptance criteria, or auditing and reconciling existing epic children before implementation. Dispatches an opus dso:story-decomposer sub-agent to draft prioritized vertical-slice user stories with measurable done definitions tied to epic Success Criteria (never inline), identifies dependencies, runs an adversarial red-team review pass, dispatches a UI designer for UI stories, and writes the story tickets to the tracker. Trigger phrases include 'break down this epic', 'split into stories', 'story splitting', 'backlog grooming', 'write user stories', 'define acceptance criteria', 'plan the epic', 'decompose the epic', 'reconcile epic children'.

Use when the user wants to see what DSO skills and scripts are available, list installed plugin commands, or look up the description of a skill they don't recognize. Auto-discovers and displays every script under the plugin scripts directory and every skill under the plugin skills directory, with each entry's description extracted from script comments or skill YAML frontmatter. No hardcoded lists — everything resolves dynamically at invocation time. Trigger phrases include 'list available skills', 'what skills are available', 'show plugins', 'what tools are installed', 'what can DSO do', 'list dso commands', 'show plugin scripts'.

Use when a calling skill (e.g., /dso:implementation-plan, /dso:design-review, /dso:preplanning architectural-pattern check) needs to run a multi-perspective review of an artifact (plan, design, pattern). The caller passes subject, artifact, a perspectives list (each is a reviewer file), passthreshold, startstage, maxrevisioncycles, and callerid; this skill dispatches one sub-agent per perspective, scores on configured dimensions, detects conflicts between reviewers, runs a revision cycle up to maxrevisioncycles, and returns JSON per the standardized REVIEW-SCHEMA. Not user-invocable directly — it is the shared review engine that calling skills delegate to instead of writing ad-hoc review logic.

Use when the user asks about review metrics, review analytics, reviewer performance, the review dashboard, review trends, resolution rates, or how /dso:review has been performing over time. Runs review-stats.sh and displays its output as-is — reviewer tier distribution (light/standard/deep), autonomous resolution rates, severity-distribution trends, and time-bucketed counts. Trigger phrases include 'review stats', 'review metrics', 'review analytics', 'reviewer performance', 'review dashboard', 'how is review going', 'tier distribution'.

Use when checking ticket health, cleaning up stale tickets, fixing dependency cycles, or validating that tickets are ready for sprint execution. Runs validate-issues.sh against the DSO ticket tracker to score health 1–5, surfaces common issues (orphan epics, missing acceptance criteria, dependency cycles, blocked-everywhere tasks, stale inprogress, broken interface tasks), and provides per-issue fix commands. Trigger phrases include 'ticket health', 'validate tickets', 'stale tickets', 'issue cleanup', 'check ticket dependencies', 'fix dependency cycle', 'are the tickets clean', 'audit the tracker'.

Use when starting an epic's wireframe designs, scanning a frontend for UI components, cataloguing existing routes, or inventorying frontend state. Generates or refreshes the UI Discovery Cache: inventories components via Glob/Grep, crawls routes via Playwright, and writes structured results to .ui-discovery-cache/. Produces a deterministic validation script for git-based cache invalidation. Trigger phrases include 'scan UI components', 'discover routes', 'catalog UI elements', 'inventory frontend components', 'refresh ui-discovery-cache', 'before designing wireframes'.

Use when running a smoke test, sanity check, health check, or status check before closing work — also when the user asks 'is everything working', 'verify the deployment', or 'check the build'. Dispatches read-only sub-agents that run local validate.sh, check CI pipeline status, probe staging deployment health, and ping live-environment endpoints in parallel; gates Batch 2 (live env) on Batch 1 passing; reports PASS/WARN/FAIL per domain with recommended actions. Detects and reports — never fixes. Trigger phrases include 'smoke test', 'sanity check', 'health check', 'status check', 'is everything working', 'verify deployment', 'run the checks', 'is the build green', 'validate before close'.