Back to the Playbook
OperateOP-08
Answer a product question
Answer a customer, support or internal question about how the product behaves from the Product Brain and the code, with sources and the owner who confirms.
Product statusAvailable now
Context in4 required inputsThe question and its context · Relevant code · Related tickets and decisions
TransformationProduct Manager + Product Agent + Architecture AgentCode Analysis · Atlassian · Local Files · Find Code Owners
OutcomeSourced answer with classification and the owner to confirm.Artifact: Documentation
Why it matters
The expensive people get pulled into support questions that repeat. The answer usually exists in the code, a decision or a ticket; this Activity finds it and names who should confirm it.
Owner
Product Manager
Agent-led
Participants · Agents
EngineerProduct AgentArchitecture Agent
Trigger
A support ticket, a customer question or an internal question about product behaviour.
Required context
Customer evidenceThe question and its contextCodeRelevant codeJiraRelated tickets and decisionsConfluenceProduct documentation
Optional context
Product BrainPrevious answersFilesAccount contextConfluenceRelease notes
Skills
Code AnalysisAtlassianLocal FilesFind Code Owners
Activity steps
- 1Locate the behaviour in the code and the decisions behind it.
- 2Draft the answer with sources: code, ticket, decision, documentation.
- 3Classify: expected behaviour, defect or feature request.
- 4Name the owner to confirm and, if needed, create the bug or opportunity.
Output
Sourced answer with classification and the owner to confirm.
Artifacts
Updates: Documentation
What good looks like
- Every claim links to code, a ticket or a decision.
- Expected behaviour is separated from defect and wish.
- The answer says what the customer can do now.
- Repeated questions become documentation.
Quality gate
The named owner confirms answers that go to customers.
Destination
Teklens onlyJiraConfluence
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.