Back to the Playbook
DefineDE-07
Draft Jira story
Create a build-ready story grounded in product intent and the actual code, with testable acceptance criteria and edge cases.
Product statusAvailable now
Context in4 required inputsParent epic or initiative · Problem and expected behaviour · Relevant PRD
TransformationProduct Manager + Product Agent + Architecture AgentStory Drafting · Code Analysis · Atlassian
OutcomeDraft Jira story with acceptance criteria and linked evidence.Artifact: Jira story
Owner
Product Manager
Human + Agent
Participants · Agents
EngineerProduct AgentArchitecture Agent
Trigger
A defined slice of work is ready to enter the backlog.
Required context
JiraParent epic or initiativeConfluenceProblem and expected behaviourConfluenceRelevant PRDCodeAffected code
Optional context
Design systemUI draftCustomer evidenceCustomer evidenceArchitectureDependenciesJiraEstimate
Skills
Story DraftingCode AnalysisAtlassian
Activity steps
- 1Retrieve the parent intent and the decision behind it.
- 2Inspect the affected code paths and data shapes.
- 3Draft the user-visible outcome and acceptance criteria with edge cases.
- 4Add dependencies, risks and links to the evidence.
Output
Draft Jira story with acceptance criteria and linked evidence.
Artifacts
Creates: Jira story
What good looks like
- Clear user-visible outcome.
- Acceptance criteria are testable.
- Enough code grounding to avoid hidden scope.
- Linked to parent intent and evidence.
Quality gate
Product and engineering approve before Ready for Build.
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.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.