ln-41-test-strategy-planner

Designs risk-based test portfolio decisions and prioritized test scenarios without modifying code.

556|83|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-41-test-strategy-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-41-test-strategy-planner
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/plugins/testing-suite/skills/ln-41-test-strategy-planner
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-41-test-strategy-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often accumulate tests without a clear rationale, leaving critical risks unproved while low-value tests multiply. This Skill produces a read-only, risk-based test strategy that maps requirements to existing evidence and decides which tests to keep, add, update, merge, delete, or deliberately omit.

Core Features & Use Cases

  • Risk Mapping: Traces critical flows and enumerates plausible defect classes tied to protected outcomes like money, authorization, and data integrity.
  • Portfolio Decisions: Assigns every material risk an explicit action (KEEP, ADD, UPDATE, MERGE, DELETE, NO_TEST) with level, oracle, environment, and gate.
  • Prioritized Test Matrix: Orders scenarios so safety-critical checks run first, separates release gates from diagnostics, and states exclusions and residual risks.
  • Use Case: Before implementing a payment retry feature, run this Skill to identify which behaviors lack proof, decide the right test level for each risk, and produce a READY verdict with a prioritized scenario matrix.

Quick Start

Ask the agent to design a risk-based test strategy for the new checkout retry feature without writing or changing any tests.

Frequently Asked Questions about ln-41-test-strategy-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a risk-based test strategy for a new feature?

Provide the feature requirements and acceptance criteria, then the Skill maps existing test evidence, enumerates plausible defect classes, and assigns each material risk a portfolio action with level, oracle, and priority. It returns a READY, INCONCLUSIVE, or BLOCKED verdict with a prioritized scenario matrix.

How to decide which tests to keep, update, or delete?

Each affected test gets exactly one action: KEEP when trusted unique proof remains valid, UPDATE when intent survives but basis or oracle changed, MERGE for consolidatable proof, and DELETE for obsolete or duplicate tests. DELETE and MERGE require proof that replacement evidence preserves every required behavior and failure mode.

Does this test planning skill write or modify any tests?

No, the run is strictly read-only. It never creates tests, fixtures, snapshots, tasks, or documentation, and never updates the reviewed implementation. It only produces a strategy document with decisions, priorities, and evidence gaps.

When should I choose unit vs integration vs end-to-end tests?

Choose unit tests for isolated local rules, contract tests for producer-consumer agreement, integration tests for owned boundaries, and end-to-end tests for production-shaped journeys whose terminal outcome cannot be proved lower. Avoid duplicating the same behavior at multiple levels unless each detects a distinct failure class.

What happens when requirements are too vague to plan tests?

The Skill returns a BLOCKED verdict when there is no concrete behavior to plan for, or INCONCLUSIVE when partial planning is possible but material evidence is missing. It states the smallest next evidence-gathering action for every unresolved area.