Resources Prompt pack
Prompt packThe SOP-to-system prompt set
7 prompts that turn a written procedure into a workflow spec, a tool list, and a build order.
What the prompt does.
A procedure written for people leaves out what a system needs: the trigger, the records it touches, the rule behind each decision. These 7 prompts ask for those parts in order, so the thing you hand to a builder is complete.
Run them in sequence. Each one takes the output of the last.
Everything in the file.
Nothing here is held back for a paid tier. The community adds the walkthrough, not extra parts.
- 01 · SOP to system spec
- 02 · Trigger and input audit
- 03 · Decision rules, written as conditions
- 04 · Tool shortlist against the spec
- 05 · Build order, cheapest step first
- 06 · Failure cases and what happens on each
- 07 · Handover note for whoever runs it
In order.
Read all of them first. The order matters more than any single step.
- Paste prompt 01 into Claude, ChatGPT, or a Claude Code session.
- Give it one procedure. One, not a department.
- Answer the [unclear] flags before moving to 02.
- Stop after 04 if you only need the tool decision.
Take it now.
One click copies the whole block. Paste it into Claude, ChatGPT, or a Claude Code session.
Below is a written procedure from my business.
Rewrite it as a system spec with these sections:
- Trigger: the event that starts it
- Inputs: every document, message, or record it needs
- Steps: one action per line, in order
- Decisions: each point where a person chooses, and the rule they use
- Outputs: what exists at the end that didn't before
- Failure points: where it breaks today, from the text or implied
Keep my wording where it's specific. Flag anything vague with [unclear].
Don't recommend tools. Don't add steps I didn't describe.
Procedure:
[paste the SOP here]Build it with other founders.
The community opens soon. Weekly builds, the full library, and answers when this file does not match your business.