Log, classify, prioritise, and track defects found during test execution. Produce a structured bug triage log that drives resolution and feeds into the QA sign-off decision.
Inputs
Test execution report: {output_path}/qa/test-execution.md
Developer contact: @sml-agent-developer for fix ownership
Deliverable
{output_path}/qa/bug-triage.md
Bug Triage Log Structure
# Bug Triage Log — {project_name}
## Summary
| Severity | Open | In Progress | Resolved | Won't Fix |
|----------|------|------------|----------|-----------|
| P1 — Blocker | N | N | N | N |
| P2 — Critical | N | N | N | N |
| P3 — Major | N | N | N | N |
| P4 — Minor | N | N | N | N |
## Bug Log
### BUG-001 — {short summary}
- **Severity**: P1 / P2 / P3 / P4
- **Status**: Open / In Progress / Resolved / Won't Fix
- **Found in TC**: TC-XXX
- **Summary**: Brief one-line description
- **Steps to Reproduce**:
1. Step 1
2. Step 2
- **Expected**: What should happen
- **Actual**: What happened instead
- **Evidence**: Link to screenshot / log
- **Assigned to**: Developer / Team
- **Resolution**: (filled when resolved)
- **Verified by QA**: Yes / No
Severity Definitions
Severity
Definition
Example
P1 — Blocker
System crash, data loss, security breach, prevents core functionality
Login broken for all users
P2 — Critical
Major feature broken, significant impact, no workaround
Payment processing fails
P3 — Major
Feature works partially, workaround available
Report exports wrong format
P4 — Minor
Cosmetic, low-impact, good-to-fix
Button text has typo
Triage Process
For each failure in the test execution report, create a bug entry.
Track resolution — re-test when developer marks as fixed.
Update status field and set Verified by QA: Yes when confirmed resolved.
Validation Checklist
All test failures have a bug entry
All bugs have severity, steps, and expected/actual
All P1/P2 bugs have an assigned owner
Resolved bugs verified by QA re-test
Next Skill
When all P1/P2 bugs resolved → QA Sign-off (#file:_superml/skills/6-quality/qa-signoff/SKILL.md)
1---2name: bug-triage3description: Skill: Bug Triage4---5# Skill: Bug Triage67> **Activation**: `#file:_superml/skills/6-quality/bug-triage/SKILL.md`89---1011## Purpose1213Log, classify, prioritise, and track defects found during test execution. Produce a structured bug triage log that drives resolution and feeds into the QA sign-off decision.1415---1617## Inputs1819- Test execution report: `{output_path}/qa/test-execution.md`20- Developer contact: `@sml-agent-developer` for fix ownership2122---2324## Deliverable2526**`{output_path}/qa/bug-triage.md`**2728---2930## Bug Triage Log Structure3132```markdown33# Bug Triage Log — {project_name}3435## Summary36| Severity | Open | In Progress | Resolved | Won't Fix |37|----------|------|------------|----------|-----------|38| P1 — Blocker | N | N | N | N |39| P2 — Critical | N | N | N | N |40| P3 — Major | N | N | N | N |41| P4 — Minor | N | N | N | N |4243## Bug Log4445### BUG-001 — {short summary}46- **Severity**: P1 / P2 / P3 / P447- **Status**: Open / In Progress / Resolved / Won't Fix48- **Found in TC**: TC-XXX49- **Summary**: Brief one-line description50- **Steps to Reproduce**:51 1. Step 152 2. Step 253- **Expected**: What should happen54- **Actual**: What happened instead55- **Evidence**: Link to screenshot / log56- **Assigned to**: Developer / Team57- **Resolution**: (filled when resolved)58- **Verified by QA**: Yes / No59```6061---6263## Severity Definitions6465| Severity | Definition | Example |66|----------|-----------|---------|67| **P1 — Blocker** | System crash, data loss, security breach, prevents core functionality | Login broken for all users |68| **P2 — Critical** | Major feature broken, significant impact, no workaround | Payment processing fails |69| **P3 — Major** | Feature works partially, workaround available | Report exports wrong format |70| **P4 — Minor** | Cosmetic, low-impact, good-to-fix | Button text has typo |7172---7374## Triage Process75761. For each failure in the test execution report, create a bug entry.772. Assign severity using the table above.783. Assign ownership — P1/P2 → developer immediately; P3/P4 → sprint backlog.794. Track resolution — re-test when developer marks as fixed.805. Update `status` field and set `Verified by QA: Yes` when confirmed resolved.8182---8384## Validation Checklist8586- [ ] All test failures have a bug entry87- [ ] All bugs have severity, steps, and expected/actual88- [ ] All P1/P2 bugs have an assigned owner89- [ ] Resolved bugs verified by QA re-test9091---9293## Next Skill9495When all P1/P2 bugs resolved → **QA Sign-off** (`#file:_superml/skills/6-quality/qa-signoff/SKILL.md`)
Run npx skillmds@latest add gabrielmoreira/bug-triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Skill: Bug Triage It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.
gabrielmoreira