Back to the Playbook
DefineDE-12
Run refinement
Resolve ambiguity and bring the selected stories to a shared Ready-for-Build understanding, with the decisions recorded.
Product statusAssisted workflowThe session itself is human. Teklens prepares the pack and records the decisions; the Meeting bot for live capture is in beta.
Context in4 required inputsRefinement pack · Selected stories · Open questions
TransformationProduct Manager + Product AgentAtlassian · Estimate Feature · Code Analysis
OutcomeRefinement decisions and updated stories.Artifact: Jira story
Owner
Product Manager
Human-led
Participants · Agents
EngineerArchitectDesignerProduct Agent
Trigger
A scheduled refinement session.
Required context
FilesRefinement packJiraSelected storiesFilesOpen questionsProduct BrainProduct and code context
Optional context
JiraEstimatesDesign systemUI draftsCustomer evidenceCustomer evidence
Skills
AtlassianEstimate FeatureCode Analysis
Activity steps
- 1Review the intent of each story.
- 2Resolve open questions and challenge the scope.
- 3Estimate and decide readiness.
- 4Record the decisions and update the stories.
Output
Refinement decisions and updated stories.
Artifacts
Updates: Jira story, Decision record
What good looks like
- Decisions are explicit and recorded.
- Acceptance criteria are understood the same way.
- Unresolved blockers have an owner.
- No silent assumptions.
Quality gate
The team confirms Ready for Build.
Destination
JiraProduct Brain
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.
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.