t4-p3-04authored2–4h
Stakeholder writeup
requires: t4-p3-03
Spec
One page as if presenting to a non-technical manager - what problem this solves, what it cost to build, what the data shows, and your recommendation to kill it, keep it as is, or invest further - with reasoning.
Why this matters
A recommendation, not a status update. Being willing to recommend killing your own week's work is the professional skill here, and it is rarer than the engineering.
Verify
No result yet. Run `learn verify t4-p3-04` locally, or push to trigger CI.
artifact
unrun
judge
unrun
Rubric
# t4-p3-04 — Stakeholder writeup
**Task:** One page as if presenting to a non-technical manager - what problem this solves, what it cost to build, what the data shows, and your recommendation to kill it, keep it as is, or invest further - with reasoning.
**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 it readable by someone non-technical?
- Is the recommendation actually decided, or hedged into meaninglessness?
**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.