1. Add the requirement
In Pyloq, click New Requirement. Paste anything that describes the work: a written spec, an analysis, or a messy conversation with its decisions and side notes. You can also drop in a .docx, .txt or .md file.
You don't have to start in Pyloq. From Claude, ChatGPT or another connected AI tool, ask Pyloq to send an idea over and the requirement lands here as a draft.
2. Choose the breakdown
| Option | Best for |
|---|---|
| Stories | Features. Stories become epics, with tickets nested under them. |
| Tickets | Bug batches and small tasks. A flat list with no epic. |
| Single ticket | One well-scoped fix. No breakdown. |
3. Pyloq reads it first
Before drafting, Pyloq works out what kind of input it is:
- A written requirement or spec goes straight to drafting. Turn on Review with Pyloq first if you want to tidy it up, with an instruction such as "make the acceptance criteria testable".
- A bug report always becomes a single ticket.
- A rough idea or conversation gets a card first, so you can let Pyloq shape it into a proper requirement before drafting. Tick Allow Suggestions to let it propose what's missing.
4. Review stories and tickets
Pyloq drafts the stories (for the Stories option) and then the tickets, each with a description and acceptance criteria. On each step you can edit any field, ask Pyloq to refine a story or ticket with an instruction, check a ticket for gaps, or regenerate the breakdown.
You can leave and come back: unfinished drafts wait under Workflows.
5. Publish
On the last step, click Publish to Jira (or ClickUp). Pyloq creates the epics and tickets in your tracker and shows the new ticket keys, such as PYL-406.
Your workspace needs a connected ticket tracker to publish. See Jira or ClickUp.
Make tickets match your team's style
Under Settings → Ticket Styles, paste up to three of your team's existing tickets. Pyloq learns their structure, tone, formatting and acceptance criteria, and writes future tickets to match.