Spec to tickets
FreeTurn a spec into tickets an agent can finish. Each ticket comes with acceptance criteria, test cases, its dependencies and the files it likely touches.
Up to 100 KB. One heading per ticket, with a list of what must work.
Paste a spec, then make the tickets.
A Trello JSON or a CSV file, up to 2 MB
Only moving from Trello? Use the Trello converter
Drop an export, then choose where it should go.
What each ticket has
Enough for a person or a coding agent to start without asking.
- What and why. A title, a type, a priority and a short description in the spec's words.
- Acceptance criteria. Points a test can check, written as Given/When/Then or a checklist.
- Test cases. Steps and the expected result, filed under a test area.
- Dependencies. Tickets come in the order to build them, and each one says what must come first.
- Likely touched files. Only paths and areas your spec names. It is a guess, and every export marks it as one.
How it works
Markdown works best: one heading per ticket, with a list of what must work under it.
Read the criteria and the test cases. The notes say which tickets still miss something.
Download a GitHub script or CSV, a Jira CSV or Markdown, or import the tickets into BugBoard.
Write the spec so it splits well
Plain Markdown is enough. These lines give each ticket more.
| You write | You get |
|---|---|
| ## A heading | A ticket |
| A list item under it | An acceptance criterion |
| Given …, when …, then … | An acceptance criterion and a test case |
| Test: step; step -> result | A test case |
| Test area: Filters | The test area of the ticket's test cases |
| Files: src/list.tsx | Likely touched files |
| Needs: <ticket title> | A dependency |
| Type: bug, Priority: high | The ticket's type and priority, one line each |