assurance-strategist

Designs end-to-end testing and verification strategies for autonomous agent-built software.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill assurance-strategist-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: assurance-strategist
Source: https://github.com/mistakenot/skills/tree/main/plugins/assurance/skills/assurance-strategist
Command: npx skills add https://github.com/mistakenot/skills --skill assurance-strategist-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Autonomous coding agents build software with no human backstop, so correctness must be proven through evidence rather than trust. This Skill designs complete assurance strategies that let agents self-verify their own work, choosing the right testing techniques at the right rigor level for each subsystem. ## Core Features & Use Cases - Four-axis diagnosis: Evaluates criticality, volatility, longevity, and accountability per subsystem to shape the verification strategy. - Graded technique prescriptions: Selects from unit, property-based, model-based, differential, metamorphic, and React unit testing, choosing the lightest rung that produces useful evidence and stating upgrade triggers. - Technique reference cards: Loads detailed guidance on oracles, prerequisites, harness changes, acceptance criteria, and failure modes before prescribing any technique. - Use Case: When starting a new agent-built service, ask for a testing strategy and receive a plan specifying which techniques apply to each module, what evidence each produces, and how the harness wires into make verify and CI. ## Quick Start Ask the agent to design an assurance strategy for your project, describing its subsystems and how critical each one is.

Frequently Asked Questions about assurance-strategist

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

FAQPage Schema
How do I design a testing strategy for agent-built software?▼

Diagnose four axes per subsystem: criticality, volatility, longevity, and accountability. Then select techniques from the index (unit, property-based, model-based, differential, metamorphic, React unit testing) at the lightest rung that produces useful self-verification evidence, stating the upgrade trigger for each.

What is the difference between differential and metamorphic testing?▼

Differential testing compares the system against a second independent implementation that computes the exact answer, catching wrongness. Metamorphic testing asserts relations between outputs of related inputs when no oracle exists, catching inconsistency but not uniform wrongness.

When should I use model-based testing instead of property-based testing?▼

Use model-based testing when the subsystem is stateful and bugs live in operation ordering, and you need explicit state-machine coverage metrics or online execution. Stateful property-based testing with a reference model is the lighter rung and usually sufficient first.

Does this skill run tests or write test code directly?▼

No. It designs the assurance strategy and generates artifacts such as testing docs and acceptance criteria. Running tests and day-to-day verification are handled by the generated artifacts and harness, not by this skill.

What are the limitations of property-based testing?▼

Property-based testing only checks stated invariants, so it misses bugs where no property is expressed, integration failures, UI issues, and performance regressions. Vacuous or weak properties give false confidence, which mutation testing is used to audit.