PRD Generator
helio / prd-writerGive it a problem and a goal. It asks the questions a spec needs before it writes, then hands back a PRD with acceptance criteria engineering can plan a sprint from.
Write a PRD for prescription withdrawal. Doctors need to withdraw a mis-issued prescription without phoning the patient. Success is the patient notified within 3 seconds. Ask me whatever you need before you start writing.
Swap in your own problem and success metric. The last sentence is the part that matters — it's what stops it drafting on assumptions.
What is PRD Generator?
A teammate that turns a problem into a spec: background, features, flow, testable acceptance criteria, edge cases, and the questions still open. Drafts land in Notion, so revisions are a diff. It won't decide scope, feasibility, or priority — it flags the conflict and leaves the call to you.
What it does
Any chatbot writes a PRD once. Helio runs it as a standing job — from your context, kept current, delivered to you.
| Owns the job, not just the draft | It routes the feasibility read to an engineer and only calls the PRD done once the open questions close. |
| Runs again without starting over | Once it works, it's saved. The next idea runs the same vetted process on a trigger — not a blank prompt. |
| Writes from your context | It pulls your Notion, past PRDs, and acceptance-criteria style, so a new spec matches how your team writes. |
| Keeps itself current | When your direction or conventions change, it updates the workflow. You don't re-teach it your standards. |
| Lands where you work | The PRD and its open questions arrive in Slack, Lark, or email. You don't open Helio to read it. |
Three things it gets right
It refuses to guess
A PRD built on assumptions costs more than no PRD, so it asks first. A design choice, not a setting.
Criteria you can test
"Paid prescription: system rejects with a message." A check QA can run, so the sprint has something to close against.
Open questions stay open
Unresolved calls get their own section. What it doesn't know is visible, not hidden in confident prose.
What PRD Generator connects to.
Questions
- How many questions will it ask before it writes?
- Usually three to five. It stops once the success metric, the edge cases, and the out-of-scope list are settled. Tell it to draft anyway and it writes the document with the gaps listed as open questions.
- Who checks it before it's final?
- You route it. It asks for a feasibility read from engineering and won't call a draft final on its own, because whether something is buildable is not a judgement it should be making.
- Can it update a PRD as requirements change?
- Point it at the Notion doc and the change. It rewrites the affected sections and leaves the rest alone, so a reviewer reads a diff instead of the whole document again.
- Does it work outside software?
- Yes. It adapts the structure to the domain, and in regulated ones like healthcare it flags where a compliance or clinical review is required rather than writing around it.
From an idea to a build-ready PRD.
Run the prompt above. The first thing back is the list of questions it needs answered before it will write a word.
Ask about this automation