Challenge a proposed solution by identifying and testing consequential assumptions. Use when the brief feels too certain or discovery reveals contradictions.
Start a fresh conversation. Replace the highlighted placeholders.
Use test-assumptions to audit [the project brief, current reality/terrain documents, and codebase] by extracting load-bearing assumptions, classifying them by kind and blast radius, and designing specific validation tests for critical risks to produce a ranked `assumptions.md` register.
Required inputs
[the project brief, current reality/terrain documents, and codebase]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: test-assumptionsdescription: Challenge a proposed solution by identifying and testing consequential assumptions. Use when the brief feels too certain or discovery reveals contradictions.
test-assumptions
Purpose
A ranked set of assumptions and ways to test them.
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
Principles
Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.