t4-p2-05draft2–4h
Missing-response nudge
requires: t4-p2-04
Spec
Direct-message anyone who has not responded by a cutoff, once, without being annoying. Tie this feature back to a specific pain point from your Phase 1 interviews.
Why this matters
Once, and only once. The nudge is where a helpful bot becomes an annoying one, and the constraint forces you to trace a feature to an interview rather than to your own preference.
Verify
No result yet. Run `learn verify t4-p2-05` locally, or push to trigger CI.
contract
unrun
judge
unrun
Rubric
# t4-p2-05 — Missing-response nudge
**Task:** Direct-message anyone who has not responded by a cutoff, once, without being annoying. Tie this feature back to a specific pain point from your Phase 1 interviews.
**Strong:** Directly answers every one of the review questions below in the affirmative, with specific evidence from the actual work, not a restatement of the task.
- Is the nudge traceable to a quoted pain point, or justified after the fact?
**Passing but weak:** The deliverable exists and technically satisfies the spec, but is generic, restates the task instructions instead of engaging with them, or only partially addresses the review questions below.
**Fails:** The deliverable is missing, or engages with none of the review questions below - e.g. it describes what was built without explaining the reasoning the task actually asks for.