test-strategy

Classifies task specification sources to determine optimal implementation test strategy.

Updated Feb 20, 2026

Search Tags:#testing #tdd #bdd #acceptance-criteria #red-green #test-planning

Ready to run

npx skills add https://github.com/supertyrelle/pelley --skill test-strategy-supertyrelle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-strategy
Source: https://github.com/supertyrelle/pelley/tree/main/skills/test-strategy
Command: npx skills add https://github.com/supertyrelle/pelley --skill test-strategy-supertyrelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you choose the right testing strategy before implementation so you can avoid writing the wrong tests, wasting time on brittle coverage, or skipping validation entirely.

Core Features & Use Cases

Spec-aware classification: Distinguishes codified, articulated, and tacit tasks so the workflow matches the evidence available.
Red-green discipline: Guides you to write failing tests first when a specification exists, then implement against frozen assertions.
Fallback coverage: Switches to test-after boundaries when the work is exploratory or when implementation constraints force an escape valve.
Use case: A developer receives a bug report with repro steps and uses this Skill to turn the report into focused tests before touching the code.

Quick Start

Ask the test-strategy skill to analyze your task, classify the available specification, and produce the next testing steps for implementation.

Frequently Asked Questions about test-strategy

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

FAQPage Schema

How do I decide whether to write tests before or after implementation?▼

Test strategy is determined by classifying the task's specification source, using formal specs or acceptance criteria for red-green test-first flows and switching to test-after coverage for exploratory work lacking formal specs.

What's the best way to turn a bug report with repro steps into focused tests?▼

Turn bug reports into focused tests by classifying the repro steps as articulated specifications, then writing failing tests first to validate the issue before touching the implementation code.

What is red-green gating in TDD and when should I use it?▼

Red-green gating is a test-first discipline where you write failing tests against frozen assertions before implementation. Use it when a codified specification or formal acceptance criteria exists for the feature task.

How do I handle test planning for exploratory work with no formal specification?▼

Test planning for exploratory work uses fallback test-after coverage boundaries when no spec exists, allowing implementation constraints to dictate validation rather than forcing premature test-first assertions.

Can I apply test planning workflows to refactoring tasks?▼

Test planning workflows apply to refactoring tasks by classifying the refactor's specification source, using existing frozen assertions to gate implementation attempts within a three-attempt loop before falling back to test-after coverage.

What are the limitations of test-first development for agent dispatch workflows?▼

Test-first development for agent dispatch workflows is limited when implementation constraints force escape valves, requiring fallback test-after boundaries instead of strict red-green gating against provenance-traced assertions.