@autocode-cli/autocode 0.1.11 → 0.1.12

package/templates/prompts/in-progress.en.md

@@ -15,10 +15,10 @@ Active development. Ticket is being worked on, code is being written.
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-7. Document: `autocode comment <key> "Work completed"`
-8. Advance: `autocode next <key>`
+7. Document: `autocode comment <ticket-key> "Work completed"`
+8. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/in-progress.fr.md

@@ -15,10 +15,10 @@ Developpement actif. Le ticket est en cours de travail, le code est en cours d'e
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-7. Documenter : `autocode comment <key> "Travail effectue"`
-8. Avancer : `autocode next <key>`
+7. Documenter : `autocode comment <ticket-key> "Travail effectue"`
+8. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/qualification.en.md

@@ -16,10 +16,10 @@ Analyze and qualify the ticket requirement. Ensure the request is clear, feasibl
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-8. Document: `autocode comment <key> "Qualification complete: <summary>"`
-9. Advance: `autocode next <key>`
+8. Document: `autocode comment <ticket-key> "Qualification complete: <summary>"`
+9. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/qualification.fr.md

@@ -16,10 +16,10 @@ Analyser et qualifier le besoin du ticket. S'assurer que la demande est claire,
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <key> "Qualification terminee : <resume>"`
-9. Avancer : `autocode next <key>`
+8. Documenter : `autocode comment <ticket-key> "Qualification terminee : <resume>"`
+9. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/ready.en.md

@@ -15,10 +15,10 @@ Qualified tickets ready to be worked on. All information needed is available.
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-7. Document: `autocode comment <key> "Work completed"`
-8. Advance: `autocode next <key>`
+7. Document: `autocode comment <ticket-key> "Work completed"`
+8. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/ready.fr.md

@@ -15,10 +15,10 @@ Tickets qualifies prets a etre travailles. Toutes les informations necessaires s
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-7. Documenter : `autocode comment <key> "Travail effectue"`
-8. Avancer : `autocode next <key>`
+7. Documenter : `autocode comment <ticket-key> "Travail effectue"`
+8. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/retest-cypress.en.md

@@ -14,10 +14,10 @@ Re-run all automated E2E tests to ensure refactoring did not introduce regressio
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-6. Document: `autocode comment <key> "Retest Cypress OK"`
-7. Advance: `autocode next <key>`
+6. Document: `autocode comment <ticket-key> "Retest Cypress OK"`
+7. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/retest-cypress.fr.md

@@ -14,10 +14,10 @@ Re-executer tous les tests E2E automatises pour s'assurer que le refactoring n'a
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-6. Documenter : `autocode comment <key> "Retest Cypress OK"`
-7. Avancer : `autocode next <key>`
+6. Documenter : `autocode comment <ticket-key> "Retest Cypress OK"`
+7. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/retest-playwright.en.md

@@ -16,10 +16,10 @@ Post-refactoring validation with Playwright. Verify that refactoring did not bre
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-8. Document: `autocode comment <key> "Retest Playwright OK"`
-9. Advance: `autocode next <key>`
+8. Document: `autocode comment <ticket-key> "Retest Playwright OK"`
+9. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/retest-playwright.fr.md

@@ -16,10 +16,10 @@ Validation post-refactoring avec Playwright. Verifier que le refactoring n'a pas
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <key> "Retest Playwright OK"`
-9. Avancer : `autocode next <key>`
+8. Documenter : `autocode comment <ticket-key> "Retest Playwright OK"`
+9. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/retest.en.md

@@ -17,10 +17,10 @@ Re-run all tests after bug fixes or corrections. Ensure no regressions were intr
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-9. Document: `autocode comment <key> "Retest passed: all tests green"`
-10. Advance: `autocode next <key>`
+9. Document: `autocode comment <ticket-key> "Retest passed: all tests green"`
+10. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/retest.fr.md

@@ -17,10 +17,10 @@ Re-executer tous les tests apres corrections de bugs. S'assurer qu'aucune regres
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-9. Documenter : `autocode comment <key> "Retest OK : tous les tests verts"`
-10. Avancer : `autocode next <key>`
+9. Documenter : `autocode comment <ticket-key> "Retest OK : tous les tests verts"`
+10. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/review-best-practices.en.md

@@ -16,10 +16,10 @@ Code quality audit. Verify conventions and best practices are followed.
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-8. Document: `autocode comment <key> "Review best practices OK"`
-9. Advance: `autocode next <key>`
+8. Document: `autocode comment <ticket-key> "Review best practices OK"`
+9. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/review-best-practices.fr.md

@@ -16,10 +16,10 @@ Audit qualite du code. Verifier que les conventions et bonnes pratiques sont res
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <key> "Review best practices OK"`
-9. Avancer : `autocode next <key>`
+8. Documenter : `autocode comment <ticket-key> "Review best practices OK"`
+9. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/review-code.en.md

@@ -17,10 +17,10 @@ Perform peer code review. Ensure code quality, readability, and adherence to pro
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-9. Document: `autocode comment <key> "Code review passed: <summary>"`
-10. Advance: `autocode next <key>`
+9. Document: `autocode comment <ticket-key> "Code review passed: <summary>"`
+10. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/review-code.fr.md

@@ -17,10 +17,10 @@ Effectuer une revue de code. Assurer la qualite du code, sa lisibilite et le res
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-9. Documenter : `autocode comment <key> "Code review OK : <resume>"`
-10. Avancer : `autocode next <key>`
+9. Documenter : `autocode comment <ticket-key> "Code review OK : <resume>"`
+10. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/review-consistency.en.md

@@ -16,10 +16,10 @@ Verify code integrates harmoniously with existing project architecture.
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-8. Document: `autocode comment <key> "Review consistency OK"`
-9. Advance: `autocode next <key>`
+8. Document: `autocode comment <ticket-key> "Review consistency OK"`
+9. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/review-consistency.fr.md

@@ -16,10 +16,10 @@ Verifier que le code s'integre harmonieusement avec l'architecture existante du
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <key> "Review consistency OK"`
-9. Avancer : `autocode next <key>`
+8. Documenter : `autocode comment <ticket-key> "Review consistency OK"`
+9. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/review-no-duplication.en.md

@@ -16,10 +16,10 @@ Identify and eliminate code duplication. Factor into reusable functions/composab
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-8. Document: `autocode comment <key> "Review no duplication OK"`
-9. Advance: `autocode next <key>`
+8. Document: `autocode comment <ticket-key> "Review no duplication OK"`
+9. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/review-no-duplication.fr.md

@@ -16,10 +16,10 @@ Identifier et eliminer la duplication de code. Factoriser en fonctions/composabl
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <key> "Review no duplication OK"`
-9. Avancer : `autocode next <key>`
+8. Documenter : `autocode comment <ticket-key> "Review no duplication OK"`
+9. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/review-security.en.md

@@ -17,10 +17,10 @@ Security audit. Identify and fix potential vulnerabilities (OWASP Top 10).
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-9. Document: `autocode comment <key> "Review security OK"`
-10. Advance: `autocode next <key>`
+9. Document: `autocode comment <ticket-key> "Review security OK"`
+10. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/review-security.fr.md

@@ -17,10 +17,10 @@ Audit securite. Identifier et corriger les vulnerabilites potentielles (OWASP To
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-9. Documenter : `autocode comment <key> "Review security OK"`
-10. Avancer : `autocode next <key>`
+9. Documenter : `autocode comment <ticket-key> "Review security OK"`
+10. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/specification.en.md

@@ -16,10 +16,10 @@ Write detailed technical specifications for the ticket. Define the implementatio
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-8. Document: `autocode comment <key> "Specification complete: <technical approach>"`
-9. Advance: `autocode next <key>`
+8. Document: `autocode comment <ticket-key> "Specification complete: <technical approach>"`
+9. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/specification.fr.md

@@ -16,10 +16,10 @@ Rediger les specifications techniques detaillees pour le ticket. Definir clairem
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <key> "Specification terminee : <approche technique>"`
-9. Avancer : `autocode next <key>`
+8. Documenter : `autocode comment <ticket-key> "Specification terminee : <approche technique>"`
+9. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/splitter.en.md

@@ -22,10 +22,10 @@ If the task is small enough to be completed in one go, proceed directly without
 6. Verify no functionality has been forgotten or duplicated across tickets
 7. Create an integration ticket that references all sub-tickets to validate cohesion
 8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-9. Document: `autocode comment <key> "[summary]"`
-10. Advance: `autocode next <key>`
+9. Document: `autocode comment <ticket-key> "[summary]"`
+10. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/splitter.fr.md

@@ -22,10 +22,10 @@ Si la tâche est suffisamment petite pour être complétée en une fois, procéd
 6. Vérifier qu'aucune fonctionnalité n'a été oubliée ou dupliquée entre les tickets
 7. Créer un ticket d'intégration qui référence tous les sous-tickets pour valider la cohésion
 8. Si travail hors scope détecté : `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-9. Documenter : `autocode comment <key> "[résumé]"`
-10. Avancer : `autocode next <key>`
+9. Documenter : `autocode comment <ticket-key> "[résumé]"`
+10. Avancer : `autocode next <ticket-key>`
 
-> Ou retourner : `autocode move <key> <targetColumn>`
+> Ou retourner : `autocode move <ticket-key> <target-column-slug>`
 
 ## Critères de Validation
 

package/templates/prompts/testing-cypress.en.md

@@ -16,10 +16,10 @@ Write AND execute E2E automated tests to prevent regressions.
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-8. Document: `autocode comment <key> "Cypress tests OK"`
-9. Advance: `autocode next <key>`
+8. Document: `autocode comment <ticket-key> "Cypress tests OK"`
+9. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/testing-cypress.fr.md

@@ -16,10 +16,10 @@ Rediger ET executer des tests E2E automatises pour prevenir les regressions.
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <key> "Tests Cypress OK"`
-9. Avancer : `autocode next <key>`
+8. Documenter : `autocode comment <ticket-key> "Tests Cypress OK"`
+9. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/testing-integration.en.md

@@ -17,10 +17,10 @@ Run integration tests to verify components work correctly together. Ensure syste
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-9. Document: `autocode comment <key> "Integration tests passed"`
-10. Advance: `autocode next <key>`
+9. Document: `autocode comment <ticket-key> "Integration tests passed"`
+10. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/testing-integration.fr.md

@@ -17,10 +17,10 @@ Executer les tests d'integration pour verifier que les composants fonctionnent c
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-9. Documenter : `autocode comment <key> "Tests d'integration OK"`
-10. Avancer : `autocode next <key>`
+9. Documenter : `autocode comment <ticket-key> "Tests d'integration OK"`
+10. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/testing-playwright.en.md

@@ -16,10 +16,10 @@ Live functional testing with Playwright. Manually verify feature works by naviga
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-8. Document: `autocode comment <key> "Playwright tests OK"`
-9. Advance: `autocode next <key>`
+8. Document: `autocode comment <ticket-key> "Playwright tests OK"`
+9. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/testing-playwright.fr.md

@@ -16,10 +16,10 @@ Test fonctionnel live avec Playwright. Verifier manuellement que la feature fonc
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <key> "Tests Playwright OK"`
-9. Avancer : `autocode next <key>`
+8. Documenter : `autocode comment <ticket-key> "Tests Playwright OK"`
+9. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/testing-unit.en.md

@@ -17,10 +17,10 @@ Write and run unit tests for the implemented feature. Ensure code coverage and r
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-9. Document: `autocode comment <key> "Unit tests passed: <coverage>%"`
-10. Advance: `autocode next <key>`
+9. Document: `autocode comment <ticket-key> "Unit tests passed: <coverage>%"`
+10. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/testing-unit.fr.md

@@ -17,10 +17,10 @@ Ecrire et executer les tests unitaires pour la fonctionnalite implementee. Assur
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-9. Documenter : `autocode comment <key> "Tests unitaires OK : <couverture>%"`
-10. Avancer : `autocode next <key>`
+9. Documenter : `autocode comment <ticket-key> "Tests unitaires OK : <couverture>%"`
+10. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/update-docs.en.md

@@ -15,10 +15,10 @@ Document changes for future developers and users.
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-7. Document: `autocode comment <key> "Documentation updated"`
-8. Advance: `autocode next <key>`
+7. Document: `autocode comment <ticket-key> "Documentation updated"`
+8. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/update-docs.fr.md

@@ -15,10 +15,10 @@ Documenter les changements pour les futurs developpeurs et utilisateurs.
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-7. Documenter : `autocode comment <key> "Documentation mise a jour"`
-8. Avancer : `autocode next <key>`
+7. Documenter : `autocode comment <ticket-key> "Documentation mise a jour"`
+8. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/validate-staging.en.md

@@ -12,14 +12,10 @@ Final validation: verify everything works in staging AND git repo is clean.
 4. Verify visually everything is OK
 5. Capture proof (screenshot)
 6. Confirm feature works
-7. If out of scope work detected:
-   - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
-   - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-   - In scope: handle directly in current ticket
-8. Document: `autocode comment <key> "Staging validation OK"`
-9. Advance: `autocode next <key>`
-
-> Or return: `autocode move <key> <targetColumn>`
+7. Document: `autocode comment <ticket-key> "Staging validation OK"`
+8. Advance: `autocode next <ticket-key>`
+
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/validate-staging.fr.md

@@ -12,14 +12,10 @@ Validation finale : verifier que tout fonctionne en staging ET que le repo git e
 4. Verifier visuellement que tout est OK
 5. Capturer une preuve (screenshot)
 6. Confirmer que la feature fonctionne
-7. Si travail hors scope detecte :
-   - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
-   - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
-   - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <key> "Validation staging OK"`
-9. Avancer : `autocode next <key>`
-
-> Ou retour : `autocode move <key> <targetColumn>`
+7. Documenter : `autocode comment <ticket-key> "Validation staging OK"`
+8. Avancer : `autocode next <ticket-key>`
+
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation