design-strategy
Design a verification strategy for specific components to unlock more autonomy. Trigger phrases: "design verification strategy", "what verification do I need", "verification plan", "how to verify this component", "unlock autonomy for this module", "what tests should I add" Optional argument: [component-name-or-path] (defaults to full codebase)
Pinned to revision d3f3870d68c8, so it is the text this page describes rather than whatever the author pushed since.
Pre-approved tools experimental
Experimental field. Support varies between clients, so this list is what the author declared, not what your client will enforce.
- Read
- Bash
- Glob
- Grep
Files
- skills/design-strategy/SKILL.md
- skills/design-strategy/references/eval-framework-operations.md
- skills/design-strategy/references/eval-framework.md
- skills/design-strategy/references/fitness-functions-implementation.md
- skills/design-strategy/references/fitness-functions.md
- skills/design-strategy/references/gate-design-patterns.md
- skills/design-strategy/references/generator-evaluator.md
- skills/design-strategy/references/harness-architecture.md
- skills/design-strategy/references/hybrid-strategies.md
- skills/design-strategy/references/oracle-patterns.md
- skills/design-strategy/references/safe-evolution.md
- skills/design-strategy/references/strategy-report-template.md
- skills/design-strategy/references/toolchain-catalog-ecosystems.md
- skills/design-strategy/references/toolchain-catalog.md
- skills/design-strategy/references/traceability-design.md
- skills/design-strategy/references/verification-cost-tiers.md
Every link opens the file at its source, pinned to the revision this page describes.