Menu
Read all open bugs in .ags/project/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /ags-design-review.
Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /ags-project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.
Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /ags-brainstorm is approved and before /ags-map-systems or any GDD authoring begins.
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
| name | ags-bug-triage |
| description | Read all open bugs in .ags/project/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization. |
| argument-hint | [sprint | full | trend] |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Write, Edit, AskUserQuestion |
Language: Talk to user in language from .ags/project/user-interaction.md. Fall back to English if file missing. Files on disk always English per .ags/rules/user-interaction.md.
Processes open bug backlog into prioritised, sprint-assigned action list. Distinguishes severity (impact?) from priority (urgency?), detects systemic trends, ensures no critical bug lost between sprints.
Output: .ags/project/qa/bug-triage-[date].md
When to run:
/ags-team-qa completes and new bugs have been filed| Artifact | Created by | If missing |
|---|---|---|
.ags/project/bugs/ with ≥1 bug file | /ags-bug-report | STOP. "No bugs to triage. Run /ags-bug-report first." |
Active epic in .ags/project/stage.md | /ags-create-epics | WARN: cannot map bugs to active epic. |
If STOP triggers, exit verdict BLOCKED.
Modes:
/ags-bug-triage sprint — triage against the current sprint; assign fixable bugs
to the sprint backlog; defer the rest/ags-bug-triage full — full triage of all bugs regardless of sprint scope/ags-bug-triage trend — trend analysis only (no assignment); read-only reportGlob for bug reports in priority order:
.ags/project/qa/bugs/*.md — individual bug report files (preferred format).ags/project/qa/bugs.md — single consolidated bug log (fallback).ags/project/qa/qa-plan-*.md "Bugs Found" table (last resort)If no bug files found:
"No bug files found in
.ags/project/qa/bugs/. If bugs are tracked in a different location, adjust the glob pattern. If no bugs exist yet, there is nothing to triage."
Stop and report. Do not proceed if no bugs exist.
Read the most recently modified file in .ags/project/epics/ to understand:
If no sprint file exists: note "No sprint plan found — assigning to backlog only."
Read .ags/rules/coding.md for severity/priority definitions if they
exist. If they do not exist, use the standard definitions in Step 3.
For each bug, extract or infer:
| Severity | Definition |
|---|---|
| S1 — Critical | Game crashes, data loss, or complete feature failure. Cannot proceed past this point. |
| S2 — High | Major feature broken but game is still playable. Significant wrong behaviour. |
| S3 — Medium | Feature degraded but a workaround exists. Minor wrong behaviour. |
| S4 — Low | Visual glitch, cosmetic issue, typo. No gameplay impact. |
| Priority | Definition |
|---|---|
| P1 — Fix this sprint | Blocks QA, blocks release, or is regression from last sprint |
| P2 — Fix soon | Should be resolved before the next major milestone |
| P3 — Backlog | Would be good to fix, but no active blocking impact |
| P4 — Won't fix / Deferred | Accepted risk or out of scope for current product scope |
For each P1/P2 bug in sprint mode:
Sprint: [current])Priority overflow — consider pulling from sprintFor full mode: assign all P1 to current sprint, P2 to next sprint estimate,
P3+ to backlog.
Flag bugs that suggest systematic problems:
After classifying all bugs, generate trend metrics:
# Bug Triage Report
> **Date**: [date]
> **Mode**: [sprint | full | trend]
> **Generated by**: /ags-bug-triage
> **Open bugs processed**: [N]
> **Sprint in scope**: [sprint name, or "N/A"]
---
## Triage Summary
| Priority | Count | Notes |
|----------|-------|-------|
| P1 — Fix this sprint | [N] | [N] assigned to sprint, [N] overflow |
| P2 — Fix soon | [N] | Scheduled for next sprint |
| P3 — Backlog | [N] | Deferred |
| P4 — Won't fix | [N] | Accepted risk |
**Critical (S1/S2) unfixed count**: [N]
---
## P1 Bugs — Fix This Sprint
| ID | System | Severity | Summary | Assigned to | Story |
|----|--------|----------|---------|-------------|-------|
| BUG-NNN | [system] | S[1-4] | [one-line description] | [sprint] | [story path] |
---
## P2 Bugs — Fix Soon
| ID | System | Severity | Summary | Target Sprint |
|----|--------|----------|---------|---------------|
| BUG-NNN | [system] | S[1-4] | [one-line description] | Sprint [N+1] |
---
## P3/P4 Bugs — Backlog / Won't Fix
| ID | System | Severity | Summary | Disposition |
|----|--------|----------|---------|-------------|
| BUG-NNN | [system] | S4 | [one-line description] | Backlog |
---
## Systemic Issues Flagged
[List any patterns from Step 3 deviation check, or "None identified."]
---
## Trend Analysis
**Volume**: [N] open / [+N] net change this sprint
**Hot spot**: [system with most bugs]
**Regressions**: [N] bugs against completed stories
**Aged bugs (>2 sprints old)**: [N]
[If N aged S1/S2 bugs > 0:]
> ⚠️ [N] high-severity bugs have been open for more than 2 sprints without
> assignment. These represent accepted risk that should be explicitly reviewed.
---
## Recommended Actions
1. [Most urgent action — usually "fix P1 bugs before QA hand-off"]
2. [Second action — usually "investigate [hot spot system] quality"]
3. [Third action — optional improvement]
Present the report in conversation, then ask:
"May I write this triage report to .ags/project/qa/bug-triage-[date].md?"
Write only after approval.
After writing:
/ags-help to see current capacity."/ags-smoke-check to re-gate."If user declined write: Verdict: BLOCKED — user declined write.