agentsclimarketplace

Testing regression strategy

Skill planifest/planifest-framework/planifest-framework/external-skills/testing-regression-strategy

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill testing-regression-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

Risk-based regression suite curation for release gating under time and budget limits. Use when teams must decide what runs always versus conditionally by impact and risk; do not use for implementing a single test type in isolation.

SKILL.md

2.1 KB, as published. Nobody here has run it

Testing Regression Strategy

Overview

Use this skill to select regression coverage that maximizes risk reduction within execution constraints.

Scope Boundaries

  • Use when not all tests can run every change and selection policy is required.
  • Typical requests:
    • Optimize regression coverage under CI time budget.
    • Define mandatory versus conditional suites by risk.
    • Map change impact to regression gates.
  • Do not use when:
    • The task is implementing one specific test case only.
    • The task is observability/alert policy design (observability-*).

Inputs

  • Release risk profile and CI budget
  • Test inventory with cost, flakiness, and detection value
  • Change-impact and component criticality model

Outputs

  • Tiered regression policy (always-run, conditional, periodic)
  • Decision record for suite selection logic and trade-offs
  • Verification checklist and gap register

Workflow

  1. Classify system areas by business and technical risk.
  2. Quantify each suite by execution cost and detection value in assets/regression-tiering-template.csv.
  3. Compare selection policies and choose one with rationale.
  4. Define trigger rules for conditional suites.
  5. Publish policy, residual risk, and review cadence.

Quality Gates

  • High-risk areas are always covered by mandatory gates.
  • Selection policy is explainable and auditable.
  • Budget trade-offs are explicit, not implicit.
  • Policy includes periodic recalibration triggers.

Failure Handling

  • Stop when high-risk areas are uncovered by mandatory tests.
  • Escalate when budget and required risk coverage conflict.

Bundled Resources

  • references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.
  • assets/regression-tiering-template.csv: quick-start matrix for always/conditional/nightly suite selection.

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.