Put a kill week on the calendar: validate or stop—no “one more week of learning”

Projects multiply while wallets stay flat when there is no kill week. Without a date, “learn one more week” keeps dead pits alive. Learning only—no income promises.

Why “one more week of learning” is expensive

It never shows on a receipt, but it burns evenings. If you still cannot accept delivery, you get a thicker bookmarks folder—not orders.

Mechanism: kickoff · mid-check · kill day

Write who pays, what they get, and how done looks. Mid-week, only count acceptance ticks—shrink scope, don’t add tools. On kill day: validated or publicly stopped. No same-day clone pits.

Prompt

Role: kill-week coach. Executable plans only. No income promises. Output kickoff lines, mid-check questions, stop statement, and a freeze list.

Scenarios

Three projects covering for each other: put all kill dates on one calendar and keep only one active. On kill morning, if acceptance is unclear, shrink the deliverable or stop—don’t extend “to polish copy.”

Boundary

Do not use kill weeks to dodge paid delivery obligations. Family/health stop-loss first. Learning only—no income promises.

Bottom line

A side project stands when the deadline allows only two results: validation complete, or a public stop. Learning only—no income promises.