Test Strategy

Use when the primary problem is test design, explicit TDD, test-first or red-green-refactor work, test seams, regression coverage, mocks, assertions, fixtures, or timing and wait strategy, or when a requested change needs a non-obvious test level, seam, regression signal, or acceptance proof. Do not use for generic testing explanations, ordinary implementation, unresolved root-cause diagnosis, unresolved architecture or ownership/interface/dependency-boundary decisions, explicit review or feedback handling, or completed-work readiness review.

Chrike Updated 1 repo stars

File contents

Chrike/coding-agent-skills commit 7d9985181a

Frequently asked questions

npx get-skill add chrike/test-strategy