Skip to content
DecisionNerd Skills

Check Readiness

Is the issue done enough to PR or close — against the quality trace?

What it is

Section titled “What it is”

Compare current state to issue requirements, acceptance criteria, and BDD completion scenarios (plus DocSlime REQUIREMENTS/TESTING when present). Report gaps with evidence, not vibes.

Why it works

Section titled “Why it works”

Definition of Done prevents “looks finished” merges — and done is the scenario→evidence map (Quality trace), regime-specific (Quality regimes). DORA high performers keep trunk releasable via automated checks; GitHub protected branches encode the gate; lightweight Given/When/Then (Dan North) makes acceptance falsifiable without mandating Cucumber. Unsatisfied scenarios or missing DocSlime contracts are gaps — often bugs or debt.

When to use it

Section titled “When to use it”

Before opening/merging a PR or closing an issue/milestone gate — when scenarios or docs claim done.

Do

Section titled “Do”
  • Extract BDD scenarios and evidence maps from issue/plan/DocSlime
  • Verify each scenario’s named proof exists or was run (or justified non-automated)
  • One write owner for follow-up fixes; hand off to test-it / document-it / docslime-fill / merge-it

Don’t

Section titled “Don’t”
  • Ignore DocSlime TESTING maps when they exist
  • Treat missing automation as a gap when manual evidence is appropriate and recorded
  • Skip orientation when you’re lost
  • Spawn overlapping agents to “go faster”
Section titled “Related concepts”

13-quality-trace, 04-evidence-over-vibes, 03-smallest-next-step, 11-quality-regimes, 12-bugs-and-debt

Further reading

Section titled “Further reading”

See also the handbook Sources & grounding bibliography.

Agent skill

Section titled “Agent skill”

check-readiness