agentsclimarketplace

Testing strategy

Skill nledford/engineering-review-board/skills/testing-strategy

A collection of AI agent skills I have written

Install
npx -y skills add nledford/engineering-review-board --skill testing-strategy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review test strategy, confidence gaps, TDD and BDD fit, flaky tests, boundary coverage, and suite maintainability. Use for a risk-focused audit of tests or test plans; do not use to write a single test, debug an active failure, or run a routine TDD loop.

SKILL.md

1.6 KB, as published. Nobody here has run it

Testing Strategy Skill

Use this skill when the primary task is assessing whether a test suite or test plan provides the right confidence. Always load review-verification-protocol before reporting findings. For repository change reviews, also load code-review.

Use test-driven-development for Red-Green-Refactor implementation, and systematic-debugging for an active unexplained test failure.

Workflow

  1. Identify the behaviors, contracts, invariants, risks, and failure modes the tests need to protect.
  2. Map existing unit, integration, contract, end-to-end, property, and manual checks to those risks.
  3. Find confidence gaps, redundant coverage, brittle implementation coupling, over-mocking, flakiness, unclear fixtures, and slow feedback paths.
  4. Recommend the narrowest test level that proves each missing behavior, including boundary tests for architecture-critical constraints.
  5. Validate claims with test code and runner evidence. Record skipped checks, environmental limitations, and residual quality risk.

Output

Return prioritized findings and a risk-focused improvement plan with evidence, recommended test levels, skipped validation, and residual risk.

Gives 0 of the 12 instructions most roadmap strategy skills give

Counted across 591 of the 672 authors here whose files we hold, read 2026-08-06

  • read product marketing context before asking questionsin 21 of 591, across 10 files
  • base price on perceived value, not costin 15 of 591, across 4 files
  • compact after finalizing a planin 14 of 591, across 9 files
  • differentiate tiers using features, limits, or supportin 14 of 591, across 3 files
  • use Van Westendorp to find acceptable price rangein 13 of 591, across 2 files
  • use MaxDiff to identify highly valued featuresin 13 of 591, across 2 files
  • map topics to buyer journey stagesin 12 of 591, across 6 files
  • Extract domain capabilities and classify subdomainsin 11 of 591, across 1 file
  • Define bounded contexts around consistency and ownershipin 11 of 591, across 1 file
  • Establish a ubiquitous language glossary and anti-termsin 11 of 591, across 1 file
  • Capture context boundaries in ADRs before implementationin 11 of 591, across 1 file
  • Open the strategic design template if neededin 11 of 591, across 1 file

Said here and by no other author read

  • load the review-verification protocol before reporting
  • load the code-review skill for repository change reviews
  • identify behaviors, contracts, invariants, and risks
  • map existing checks to those risks
  • find confidence gaps and slow feedback paths
  • recommend the narrowest test level per missing behavior

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.