Menu
Create a FEATURE ticket quickly
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
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-feat |
| description | Create a FEATURE ticket quickly |
| argument-hint | <feature description> |
Create a new FEATURE 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/FEATURES/PENDING/ and BACKLOG/FEATURES/DONE/FEAT-XXX.md filenamesFEAT-XXX (zero-padded to 3 digits)Analyze the description to determine:
Check for external documentation needs: If the feature involves a third-party library, API, or service (e.g. Stripe, Firebase, AWS SDK, a specific framework), note in the ticket that the relevant documentation should be consulted before starting implementation. 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 will need to be created or modified. List actual paths. For new files, indicate (new). For uncertain candidates, add (?). NEVER leave (A determiner).
Write specific acceptance criteria: Describe the observable behavior the feature must produce. Each criterion should be independently verifiable. Example: "La commande /foo cree un fichier dans ~/.claude/commands/" instead of "La feature marche".
Write actionable test steps: List the exact commands or scenarios to validate the feature works. Reference existing test infrastructure when applicable.
Create BACKLOG/FEATURES/PENDING/FEAT-XXX.md using this format:
# FEAT-XXX: [Short title derived from description]
**Type:** Feature
**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 context and design considerations]
## Fichiers concernes
- `path/to/file.ext` — [create/modify, why]
## Criteres d'acceptation
- [ ] [Specific observable behavior]
## Tests de validation
- [ ] [Exact command or verification scenario]
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.