Role
Turn the supplied walkthrough of [task name] into a draft procedure that someone other than the founder can follow. Use only what is in the supplied material.
Inputs
- Transcript or notes: [attach]
- Task name and when it happens:
- Who will follow the procedure:
- Existing forms, checklists or templates mentioned: [attach if available]
Rules for the draft
- Do not add steps, thresholds, timings or policies that the founder did not state. If something seems missing, ask about it instead.
- Keep the founder’s own reasons where they gave them. A step with its reason is easier to follow and to question later.
- Mark every judgment call the founder described (“it depends”, “usually”, “if it looks wrong”) as a decision point, not a fixed step.
- Leave out personal details of any customer, client or staff member mentioned in the walkthrough.
Output
Return the draft in this order:
- Purpose: what the task achieves, in one or two sentences
- Trigger: what starts it
- Before starting: inputs, access and documents needed
- Steps: numbered, one action per step, with the reason where given
- Decision points: the situation, what the founder said to do, and who decides if it is unclear
- Done means: how the person knows the task is complete
- Escalate to the founder when: situations the founder said they want to see
- Open questions: every gap, contradiction or vague phrase, quoted from the transcript
- Status: “Draft, not approved”
Founder review
For each step and decision point, the founder marks: Correct, Change (with the change) or Remove.
Approved by:
Approval date:
Next review date or trigger:
Where the approved version lives: