Back to the Playbook
Define & DesignDD-07
How to write a good ticket
Make the item understandable and testable while respecting the engineers’ agreed working format.
Product statusAvailable now
Input3 required inputsUser need and related brief or PRD · Designs and expected failure cases · Initiative focus and approved Product Brain guidance
SkillsDraft a Jira story · Prepare task context · Review an artifact against agreed criteriaProduct Manager + Product Manager Agent
OutcomeBuild-ready Jira story: title, why, observable behaviour, testable acceptance criteria, error copy and evidence links.Artifact: Jira story
Owner
Product Manager
Human + Agent
Participants · Agents
EngineerQAProduct Manager Agent
Trigger
One bounded story or work item is ready to be written.
Required context
ConfluenceUser need and related brief or PRDDesign systemDesigns and expected failure casesProduct BrainInitiative focus and approved Product Brain guidance
Optional context
JiraExisting item in JiraCodeAffected code paths
Skills
Draft a Jira storyPrepare task contextReview an artifact against agreed criteria
Suggested conversation arc
- 1Agree story scopeClarify the user outcome and smallest coherent unit of work. Agree the useful ticket format with engineering and identify oversized scope.Skills: Prepare task context
- 2Draft behaviour and acceptanceWrite a clear title, why, observable behaviour, testable acceptance criteria, actual error copy and evidence links. Leave implementation choices open unless constrained by an accepted decision.Skills: Draft a Jira story
- 3Check engineering readinessRead as the receiving engineer; identify ambiguous behaviour, missing links or decisions and compare with relevant product-brain guidance.Skills: Review an artifact against agreed criteria
- 4Discuss and confirm the storyResolve each blocking question, compare the final draft with the existing item if any and confirm the intended version. Source application follows normal explicit confirmation.
Output
Build-ready Jira story: title, why, observable behaviour, testable acceptance criteria, error copy and evidence links.
Artifacts
Creates: Jira story
What good looks like
- Acceptance criteria are testable and behaviour is observable.
- The receiving engineer finds no ambiguous behaviour or missing decision.
- Implementation choices stay open unless an accepted decision constrains them.
Quality gate
The Product Manager confirms the intended version before it is applied to Jira.
Destination
Jira
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Deep dives from the AI PM Lab
Articles that explain the thinking behind this Activity.
Choose the path that matches your role.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.