backlog-implisted

Create a new IMPROVEMENT ticket in the backlog. ## Input $ARGUMENTS ## Steps 1. **Check** that `BACKLOG/` exists. If not, tell the user to run `/backlog-init` first and stop. 2. **Calculate the next ID** by scanning files (NEVER read INDEX.md for the ID): - List all files in `BACKLOG/IMPROVEMENTS/PENDING/` and `BACKLOG/IMPROVEMENTS/DONE/` - Extract all numbers from `IMP-XXX.md` filenames - Next ID = max number found + 1 (or 001 if no files exist) - Format: `IMP-XXX` (zero-padded to 3 digits) 3. **Analyze** the description to determine: - Priorite (Critique / Haute / Moyenne / Basse) - Complexite (XS / S / M / L / XL) - Tags (free-form, relevant to the improvement) 4. **Check for external documentation needs**: If the improvement involves a third-party library, API, or service (e.g. migrating to a new SDK version, adopting a framework pattern), note in the ticket that the relevant documentation should be consulted before starting. Add a line in the description: `📖 Consulter: [doc URL or doc name]`. 5. **Identify affected files**: Based on the description and your knowledge of the codebase, determine which files will be modified. List actual paths. For uncertain candidates, add `(?)`. NEVER leave `(A determiner)`. 6. **Write specific acceptance criteria**: Describe the measurable improvement — what changes concretely? Performance gain, reduced complexity, better DX? Each criterion must be verifiable. Example: "Le hook s'execute en < 100ms au lieu