Worked recipe2 min readKeep one real product question in mind as you read.
A recipe you can run again

Follow the recipe once, then keep the parts that help.

Use the situation as your starting point, follow the steps, and save the parts that become a habit.

Try saying

“I am in this situation. Walk me through the recipe and tell me what good looks like.”

Name the situation

Start with the real moment you are in.

Follow the recipe

Do one step, then check the result.

Make it yours

Save the workflow when it works.

From approved PRD to Jira

Turn plans into tickets · 29 s video guideRead the transcript

Situation

You have a PRD the team agreed on. Now you need Jira issues with clear acceptance criteria, without copying the spec by hand or losing the decision behind it.

What you need

  • Jira connected in Connect tools, with a project key set. Issues are created in that project.
  • The PRD in Documents

Steps

1. Link the PRD to an approved decision

Specky sends tickets to Jira only when the PRD is linked to an approved decision. Open the PRD and click Start decision review. Specky opens Draft a decision packet with the PRD attached. Fill in the required fields, such as owner and review date, and approve it. Do this before generating tickets: if the decision changes later, you will need to generate them again.

2. Approve the PRD

Working alone, click Approve for execution. With teammates, click Request review; your reviewer clicks Approve.

3. Send it to execution

Click Send to Execution. Specky opens Build → Generate Tickets with the PRD selected and starts drafting. Keep Destination set to Jira. If a coding agent should pick up the work, choose it under Coding agent handoff.

You get an epic plus a few stories or tasks, each with a type, priority, story-point estimate, labels, and acceptance criteria.

4. Review and adjust

Under Generated Tickets, click a ticket to edit it and untick any you do not want. Every ticket you send needs at least one acceptance criterion.

5. Push to Jira

Click Push to Jira. Specky saves the tickets to Tickets and creates one Jira issue each, with type, priority, labels, and description. With a coding agent selected, the description also carries the acceptance criteria and product context.

6. Plan and track

  • In Tickets, select tickets, type a Sprint name…, and click Assign to group them in Specky. Plan the sprint itself in Jira.
  • Move tickets through Open, In Progress, Blocked, and Done on the Work board.
  • In Sync Watch, click Start outcome review once a ticket is done.

Output

  • Jira issues built from the PRD
  • The same tickets in Specky, each linked to its Jira issue
  • A trail from decision to PRD to tickets

Variations

Linear, GitHub, Trello, Shortcut, or Planner? Same flow: connect the tool and pick it as the Destination. For GitHub, also choose a Target Repository.

Changed a ticket after pushing? Edit it in Tickets and push again. Specky updates the existing issue instead of creating a duplicate.

No PRD yet? Draft one first with Generating Your First PRD or the Gong cookbook.

Ready to apply this?

Start with your own product and keep the first read grounded. You'll create an account before the guided result so it can be saved to your workspace.

Try the guided start