Back to the Playbook
BuildBU-02
Prepare standup
Summarise what actually moved in Jira, branches and pull requests since yesterday, with blockers and the gap between plan and code, so the standup is about problems, not status.
Product statusAvailable now
Context in3 required inputsCurrent sprint · Branches and pull requests · Yesterday's blockers
TransformationEngineer + Engineering Agent + Product AgentAtlassian · Code Analysis
OutcomeStandup summary with blockers, risk flags and plan-versus-code deviations.Artifact: Jira story
Why it matters
Jira says 80 percent. The code says 45. This Activity puts both next to each other every morning, with the ticket, branch and pull request behind every flag.
Owner
Engineer
Agent-led
Participants · Agents
Product ManagerEngineering AgentProduct Agent
Trigger
Every morning before the standup, or on demand.
Required context
JiraCurrent sprintCodeBranches and pull requestsJiraYesterday's blockers
Optional context
FilesChat threads added as filesCodeTest resultsJiraIncidents
Skills
AtlassianCode Analysis
Activity steps
- 1Collect overnight activity from Jira and Git.
- 2Compare planned status with actual code progress.
- 3Flag blockers, scope drift and blocked work.
- 4Write the standup summary with proposed actions.
Output
Standup summary with blockers, risk flags and plan-versus-code deviations.
Artifacts
Updates: Jira story
What good looks like
- Every flag links to a ticket, branch or pull request.
- The plan-versus-code gap is stated in numbers.
- Blocked work has a proposed next action.
- Fits on one screen.
Quality gate
No human gate before the result is promoted. It stays an Activity result in Teklens until a person decides to use it.
Destination
Teklens onlyJira
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.