unmatched-workflow
Installation
SKILL.md
Unmatched workflow
Leading words: falsifiable done-predicate, hypothesis loop, VERIFIED NOT VERIFIED INCONCLUSIVE.
When no playbook fits, the deliverable before any code is the workflow: phases that scale rigor to the task. Inconclusive is not a pass.
Copy these steps into the todo list verbatim. Skip with skip: <reason>.
- Frame: falsifiable done-predicate, scope, rigor level (one-way doors get more). Present before a long run.
- Design the workflow: atomic units, riskiest-unknown first, verification harness before features. The first unit that writes code is the harness, not a product edit. Deleting the old API is out of scope unless the Phase 1 predicate names it. Write the phase list down.
- Run the loop: each unit is an experiment — hypothesis, smallest change, measure on the real artifact, keep or revert.
- Verify the whole against the Phase 1 predicate on the real product.
Verdicts
Each unit: VERIFIED, NOT VERIFIED, or INCONCLUSIVE. Do not hide a negative.