expectations-checklist

What problem does it solve?

This Skill prevents inconsistent results by preserving the operator’s acceptance criteria as a checklist that can be verified later, instead of relying on agents’ interpretations that may drift over time.

Core Features & Use Cases

• Operator-controlled acceptance test: Captures each human-readable “wish” as a verifiable checklist item tied to PRD acceptance criteria when available.
• Evidence-typed verification: Enforces per-item evidence requirements (empirical, static, measurement) so QA checks are specific and testable.
• Fail-block routing with overrides: Marks items as met/partial/missed and blocks the pipeline when partial/missed items lack an operator-provided override.
• Append-only evolution: Supports canonical-first creation and later append-merge amendments without rewriting or losing history.

Quick Start

Create a task-specific expectations checklist file and then run /dr-qa or /dr-compliance to verify each wish and either pass, conditionally pass with override, or block and route back to /dr-do with the focused wish-ids.