Menu
Create a BUG ticket quickly
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Compresser une session de debug en cours et produire un prompt forensique strict (donnees -> hypothese unique -> test decisif -> STOP). A utiliser quand un debug long ou complexe derive vers la speculation, ou quand le contexte de la conv est sature et qu'il faut basculer sur une session vierge sans perdre les eliminations deja faites.
Switch to supervisor/CTO mode — plan, delegate to workers, never write code directly
Auto-bootstrap codebase indexing in any project. Detects the stack, dispatches to the native installer if supported (Dart in v0.1), or generates a stack-appropriate indexer with strict guardrails (official AST parser, format contract, auto-validation, refinement loop) for TypeScript, Python, Go, or Rust.
Switch to expert-comptable / fiscaliste mode — optimisation fiscale FR, structuration de societes, expatriation, patrimoine
Generate API_CONTRACT.md by scanning existing routes and controllers
Check if API_CONTRACT.md is in sync with the actual code
| name | backlog-bug |
| description | Create a BUG ticket quickly |
| argument-hint | <bug description> |
Create a new BUG ticket in the backlog.
$ARGUMENTS
Check that BACKLOG/ exists. If not, tell the user to run /backlog-init first and stop.
Calculate the next ID by scanning files (NEVER read INDEX.md for the ID):
BACKLOG/BUGS/PENDING/ and BACKLOG/BUGS/DONE/BUG-XXX.md filenamesBUG-XXX (zero-padded to 3 digits)Analyze the description to determine:
Check for external documentation needs: If the bug involves a third-party library, API, or service (e.g. Stripe, Firebase, AWS SDK), note in the ticket that the relevant documentation should be consulted before starting the fix. Add a line in the description: 📖 Consulter: [doc URL or doc name].
Identify affected files: Based on the description and your knowledge of the codebase, determine which files are involved. If you can identify them, list the actual paths. If unsure, list the most likely candidates with a (?) marker. NEVER leave (A determiner) — always make your best assessment.
Write specific acceptance criteria: Describe the expected behavior AFTER the fix. Not "le bug est corrige" — describe what should happen concretely. Example: "La commande install.sh ne crash plus quand le dossier cible n'existe pas" instead of "Le bug est corrige".
Write actionable test steps: List the exact commands to run or manual steps to reproduce/verify. Reference the project's existing test commands when relevant (bash tests/test.sh, bun test, etc.).
Create BACKLOG/BUGS/PENDING/BUG-XXX.md using this format:
# BUG-XXX: [Short title derived from description]
**Type:** Bug
**Statut:** A faire
**Priorite:** [determined]
**Complexite:** [estimated]
**Tags:** [relevant]
**Depends on:** none
**Blocked by:** —
**Date creation:** [today YYYY-MM-DD]
---
## Description
[User's description, enriched with root cause analysis if possible]
## Fichiers concernes
- `path/to/file.ext` — [why this file is involved]
## Criteres d'acceptation
- [ ] [Specific expected behavior after fix]
- [ ] Aucune regression introduite
## Tests de validation
- [ ] [Exact command or manual verification step]
Regenerate INDEX.md — run the full /backlog-status logic (scan all tickets, rewrite INDEX.md entirely, display stats).
Confirm with the ticket ID and path.