Skip to content

Spec to tickets

Free

Turn 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.

Tickets appear here

Paste a spec, then make the tickets.

Your agent can call this as spec_to_tickets or convert_board.How an agent uses this

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

Paste your spec

Markdown works best: one heading per ticket, with a list of what must work under it.

Check the tickets

Read the criteria and the test cases. The notes say which tickets still miss something.

Export or import

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 writeYou get
## A headingA ticket
A list item under itAn acceptance criterion
Given …, when …, then …An acceptance criterion and a test case
Test: step; step -> resultA test case
Test area: FiltersThe test area of the ticket's test cases
Files: src/list.tsxLikely touched files
Needs: <ticket title>A dependency
Type: bug, Priority: highThe ticket's type and priority, one line each

Questions

It says what to build, how to tell it is done, how to test it and what must come first. An agent can then work on it without asking. The notes name the tickets that still miss criteria or test cases.