Prompt Almanac

Create advanced Works with: Any AI

Create Jira Stories From a PRD or Requirements Document

Structured brief Has example

Break a product requirements document into ordered, linked stories.

Open in ChatGPTOpen in Claude

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Rate this prompt

Loading ratings…

Create Jira stories from this requirements document: [PRD_TEXT]. Product and release goal: [RELEASE_GOAL]. Team roles available (frontend, backend, design, QA): [TEAM_ROLES]. Maximum story size we accept: [MAX_STORY_SIZE].

Work in this order. First, write a one-paragraph summary of the goal so I can confirm you understood it. Second, list every requirement as a numbered line, using the document's numbering where it exists, and mark each as a user need, a business rule, a non-functional constraint or background. Third, draw epics from the user needs only; business rules become acceptance criteria, and non-functional constraints become criteria on several stories or a team agreement. If the document and the release goal disagree, stop and tell me which statement you followed.

Under each epic list stories in build order with a unique summary, an 'As a... I want... so that...' line, three to five Given/When/Then criteria, dependencies by number, and a size guess of small, medium or large. Flag requirements that are vague, contradictory or ownerless and do not turn them into stories. If the document names a deadline or owner, carry it into the description, not into a field I cannot confirm.

Output a CSV with the columns Summary, Issue Type, Description, Epic Name, Priority, Labels for the Jira CSV importer: quote any field containing a comma, avoid line breaks in cells, and use a semicolon between labels if allowed; check the column mapping and matching rules in the import screen [VERIFY]. Finish with a traceability list of each requirement number and its stories, and a list of requirements that map to no story and why.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

See an example result (fictional data)
Invented extract. Epic: Invoice download. Story 1 'Download a PDF invoice' (Given a completed order, when I select Download, then a PDF with number, date, items, tax and total opens). Story 2 'Prevent access to other customers' invoices'. Story 3 'Bulk download by date range' (Could). CSV row: Summary,Issue Type,Description,Epic Name,Priority,Labels. Traceability: requirements R-01 to Story 1; R-02 to Story 2; R-03 to Story 3. Not converted: R-04 'fast' needs a measurable target; question raised. Coverage check: 4 requirements, 3 converted, 1 flagged; 100 percent accounted for. Stories are created in Jira only after the product owner answers the flagged question.

Illustrative only, made-up data. Your results will differ and must be reviewed.

Related prompts