Define “done”
Name the finished artifact, inputs, boundaries, acceptance checks, and evidence before prompting.
For freelancers and solo operators, turn one vague request or recurring task into a bounded deliverable with a human review gate—before you buy a large stack or automate an unsafe step.
Name the finished artifact, inputs, boundaries, acceptance checks, and evidence before prompting.
Separate scout, maker, skeptic, finisher, and human checks by the failure each prevents.
Pass verified facts, limits, decisions, and open work without forwarding private conversation debris.
Check claims, links, scope, privacy, usability, and delivery before anything leaves the draft.
Redact sensitive context and match each statement to the evidence actually available.
Use the same bound–route–handoff–check–prove loop for research, content, products, and launches.
A self-serve text kit you can copy into your own local notes or Markdown files. It is deliberately tool-agnostic and useful without a subscription.
Want to test the task before buying anything? Run the free first-task check. If the small pilot earns a place in your routine, inspect the complete 44-file system next.
This is the kind of copy-ready page the kit supplies. Adapt the labels to one recurring task.
For a freelancer or solo operator, turn a vague request into a bounded deliverable, review check, and completion receipt before promising implementation. This is a positioning lens, not a client-result guarantee.
Try the free problem brief →