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 sprint
Situation
You have an approved PRD. Now you need to break it into Jira tickets, assign story points, and get it into the current sprint — without losing the context that went into the PRD.
What you need
- Jira integration connected (Settings → Integrations → Jira)
- An approved PRD in Specky Documents
- 5 minutes
Steps
1. Open the PRD in Documents
Go to Documents and open the approved PRD.
2. Generate tickets
Click Generate tickets in the top toolbar. Specky reads the PRD and generates:
- One epic (if the feature is large enough)
- User stories with acceptance criteria
- Technical tasks (if the PRD includes implementation notes)
- A QA/test task
Each ticket inherits the PRD's evidence links — so the engineer can always trace a ticket back to the customer signal that motivated it.
3. Review and adjust
The ticket preview shows all generated tickets in a list. You can:
- Edit acceptance criteria inline
- Add or remove tickets
- Adjust story point estimates
- Reassign ticket types (story vs. task vs. bug)
4. Push to Jira
Click Push to Jira. Choose:
- Project — which Jira project to push to
- Sprint — the current sprint or the backlog
- Epic — link to an existing Jira epic or create a new one
All tickets are pushed with:
- A link back to the Specky PRD
- The acceptance criteria from Specky
- The original customer evidence linked in the description
5. Track progress
Specky monitors the Jira tickets and updates their status in your Product Graph. When all tickets in a PRD are marked Done, Specky flags the PRD as "shipped" and prompts you to link an outcome experiment.
Output
- Structured Jira tickets with acceptance criteria
- Context preserved: every ticket links back to its PRD and customer evidence
- Automatic "shipped" status when all tickets are done
Variations
Linear instead of Jira? Same flow — Settings → Integrations → Linear. Push targets Linear issues instead of Jira tickets.
Large feature? For PRDs with more than 10 stories, push the epic first and push stories in batches by sprint.
No PRD yet? Ask AI Chat to draft the PRD first (see the Gong cookbook), then come back to this flow.
Ready to apply this?
Start with your own product and keep the first read grounded. You can create an account after you see the result.