Back to the Playbook
BuildBV-02
How to log a bug
Produce one factual reproducible report; search for a matching report before proposing a new ticket.
Product statusAvailable now
Input3 required inputsObserved defect and expected behaviour · Existing reports · Initiative focus and approved Company Brain guidance
SkillsDraft a reproducible bug report · Prepare task context · Review an artifact against agreed criteriaEngineer + Software Engineer Agent
OutcomeBug report: title and impact, numbered reproduction, expected versus actual, environment and evidence, related reports.Artifact: Bug report
Owner
Engineer
Human + Agent
Participants · Agents
QASales & SupportSoftware Engineer Agent
Trigger
One defect is observed and the expected behaviour is known.
Required context
FilesObserved defect and expected behaviourJiraExisting reportsCompany BrainInitiative focus and approved Company Brain guidance
Optional context
FilesScreenshots or recordingsCodeEnvironment and affected code
Skills
Draft a reproducible bug reportPrepare task contextReview an artifact against agreed criteria
Suggested conversation arc
- 1Establish observed behaviourCapture the exact symptom, expected outcome, affected environment and user impact. Separate observations from suspected causes.Skills: Prepare task context
- 2Reproduce and check duplicatesAttempt the reported path in the actual product and retain steps, exact errors and evidence. Search existing reports; if intermittent, record attempts and observed frequency.
- 3Draft the defect reportUse the evidence to write a specific title, numbered reproduction, expected versus actual result, severity rationale and environment. Reference a duplicate instead of drafting a second issue when appropriate.Skills: Draft a reproducible bug report
- 4Confirm triage readinessRead as an engineer seeing the problem for the first time. Resolve missing steps and confirm the report or duplicate link; applying it to an external tracker requires the normal explicit source confirmation.Skills: Review an artifact against agreed criteria
Output
Bug report: title and impact, numbered reproduction, expected versus actual, environment and evidence, related reports.
Artifacts
Creates: Bug report
What good looks like
- One defect per report with an explicit observed-versus-assumed distinction.
- Severity is justified by evidence and gaps are named.
- A duplicate is referenced rather than filed twice.
Quality gate
The Engineer confirms the report or the duplicate link before it is applied to Jira.
Destination
Jira
Usually next
People and agents work from the same company knowledge. 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.
Choose one decision and review where delivery has drifted. Agree a useful first scope with a founder.