PRD to issues and tests

Hand Zenit, our AI service, a product requirements document and get back a reviewed backlog: epics, stories with acceptance criteria, engineering tasks, and manual test cases with steps. Nothing is created until you accept it.

1. Start from an idea

In a project, open Ideation and post the idea (or pick one the team voted up). Open it and go to its PRD.

2. Write or upload the PRD

Type it in, or use Upload PRD for a .md, .txt, .docx or .pdf file (up to 15 MB). The text is pulled out in your browser and put in the editor so you can check it before saving. Scanned PDFs without a text layer won't work; export a text PDF instead. Headings help: the PRD is read section by section.

3. Generate

Press Generate issues and test cases. It runs in the background, and you can leave the page. The progress card shows each stage and what it has made so far:

Requirements: each section of the PRD becomes a list of distinct requirements.
Epics: all requirements are grouped into epics.
Stories and tasks: one epic at a time, with acceptance criteria a tester can check.
Test cases: one story at a time; happy path first, then the negative and edge cases.

Why it's step by step

Zenit runs on Groq's free tier, which allows only a few thousand tokens a minute. One giant request either fails or comes back thin; many small ones give a complete list. When the per-minute limit is hit, the run waits the few seconds Groq asks for and carries on by itself.

If the daily limit runs out, the run stops as Paused and keeps everything it made. Press Resume later and it continues where it stopped, or Review what's done and accept the partial result.

4. Review and accept

Change any title, type or priority; delete what you don't want. TEST items show their steps.
Save changes keeps your edits. After editing, a paused run can't be resumed any more (its place in the list no longer matches), so finish or accept first.
Accept & create issues creates everything in the project, nested the same way: epics → stories → tasks and test cases. Test cases become TEST issues with their steps, ready for a QA test run.

PRDs with a schedule or work types

If the PRD plans work by week (or sprint or phase), and/or separates it by type (frontend, backend, design, QA...), Zenit keeps both. In review, each story, task and test shows a Week N badge and its work types.

Accepting creates one sprint per week, named Week 1, Week 2... (or reuses ones with those names), and puts every story, task and test in its week. Epics stay out of sprints, since they span weeks.
Set Week 1's date next to the accept button to date the sprints a week each; leave it empty to date them later.
Each work type becomes a label (an existing label with the same name is reused). A story is labelled with the types of the requirements it covers; each task with its own type.

Smaller AI helpers

New issue: possible duplicates appear while you type the title, with the person who handled similar issues as a suggested assignee. Suggest fills in type, priority and labels.
Issue drawer: a summary of a long thread, with decisions, open questions and next steps.
Search: type a request in plain English ("my high-priority bugs in review") and it becomes filters.