@autocode-cli/autocode 0.1.10 → 0.1.12

package/templates/prompts/git-tag.en.md

@@ -14,14 +14,10 @@ Create a version tag for the release. Follow semantic versioning.
 3. Create annotated tag: `git tag -a v<version> -m "<release notes>"`
 4. Push tag: `git push origin v<version>`
 5. Verify tag on remote
-6. 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
-7. Document: `autocode comment <key> "Tagged: v<version>"`
-8. Advance: `autocode next <key>`
-
-> Or return: `autocode move <key> <targetColumn>`
+6. Document: `autocode comment <ticket-key> "Tagged: v<version>"`
+7. Advance: `autocode next <ticket-key>`
+
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/git-tag.fr.md

@@ -14,14 +14,10 @@ Creer un tag de version pour la release. Suivre le versionnement semantique.
 3. Creer un tag annote : `git tag -a v<version> -m "<notes de release>"`
 4. Pousser le tag : `git push origin v<version>`
 5. Verifier le tag sur le distant
-6. 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
-7. Documenter : `autocode comment <key> "Tag cree : v<version>"`
-8. Avancer : `autocode next <key>`
-
-> Ou retour : `autocode move <key> <targetColumn>`
+6. Documenter : `autocode comment <ticket-key> "Tag cree : v<version>"`
+7. Avancer : `autocode next <ticket-key>`
+
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

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

@@ -11,21 +11,19 @@ Active development. Ticket is being worked on, code is being written.
 3. Plan modifications (files to create/modify)
 4. Implement the solution
 5. Test locally that it works
-6. Commit + push work done
-7. If out of scope work detected:
+6. 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> "Work completed"`
-9. 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
 
 - [ ] Feature/fix is implemented
 - [ ] Local tests pass
-- [ ] Code is committed and pushed
 - [ ] A comment summarizes work done
 
 ## Notes

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

@@ -11,21 +11,19 @@ Developpement actif. Le ticket est en cours de travail, le code est en cours d'e
 3. Planifier les modifications (fichiers a creer/modifier)
 4. Implementer la solution
 5. Tester localement que ca fonctionne
-6. Commit + push du travail effectue
-7. Si travail hors scope detecte :
+6. 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> "Travail effectue"`
-9. 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
 
 - [ ] Feature/fix implementee
 - [ ] Tests locaux passent
-- [ ] Code commite et pousse
 - [ ] Un commentaire resume le travail effectue
 
 ## Notes

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

@@ -11,21 +11,19 @@ Qualified tickets ready to be worked on. All information needed is available.
 3. Plan modifications (files to create/modify)
 4. Implement the solution
 5. Test locally that it works
-6. Commit + push work done
-7. If out of scope work detected:
+6. 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> "Work completed"`
-9. 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
 
 - [ ] Feature/fix is implemented
 - [ ] Local tests pass
-- [ ] Code is committed and pushed
 - [ ] A comment summarizes work done
 
 ## Notes

package/templates/prompts/ready.fr.md

@@ -11,21 +11,19 @@ Tickets qualifies prets a etre travailles. Toutes les informations necessaires s
 3. Planifier les modifications (fichiers a creer/modifier)
 4. Implementer la solution
 5. Tester localement que ca fonctionne
-6. Commit + push du travail effectue
-7. Si travail hors scope detecte :
+6. 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> "Travail effectue"`
-9. 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
 
 - [ ] Feature/fix implementee
 - [ ] Tests locaux passent
-- [ ] Code commite et pousse
 - [ ] Un commentaire resume le travail effectue
 
 ## Notes

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

@@ -10,15 +10,14 @@ Re-run all automated E2E tests to ensure refactoring did not introduce regressio
 2. Compare results with pre-refactoring run
 3. If new failures: identify cause (test or code issue)
 4. Fix any regressions before proceeding
-5. Commit test fixes if needed
-6. If out of scope work detected:
+5. 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
-7. Document: `autocode comment <key> "Retest Cypress OK"`
-8. 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

@@ -10,15 +10,14 @@ Re-executer tous les tests E2E automatises pour s'assurer que le refactoring n'a
 2. Comparer les resultats avec l'execution pre-refactoring
 3. Si nouveaux echecs : identifier la cause (probleme de test ou de code)
 4. Corriger toute regression avant de continuer
-5. Commiter les corrections de tests si necessaire
-6. Si travail hors scope detecte :
+5. 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
-7. Documenter : `autocode comment <key> "Retest Cypress OK"`
-8. 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

@@ -12,15 +12,14 @@ Code quality audit. Verify conventions and best practices are followed.
 4. Verify file size (components < 300 lines)
 5. Verify import organization
 6. Fix violations found
-7. Commit + push corrections
-8. If out of scope work detected:
+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
-9. Document: `autocode comment <key> "Review best practices OK"`
-10. 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

@@ -12,15 +12,14 @@ Audit qualite du code. Verifier que les conventions et bonnes pratiques sont res
 4. Verifier la taille des fichiers (composants < 300 lignes)
 5. Verifier l'organisation des imports
 6. Corriger les violations trouvees
-7. Commit + push des corrections
-8. Si travail hors scope detecte :
+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
-9. Documenter : `autocode comment <key> "Review best practices OK"`
-10. 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

@@ -12,15 +12,14 @@ Verify code integrates harmoniously with existing project architecture.
 4. Check error handling (uniform try/catch)
 5. Verify correct Pinia store usage
 6. Fix inconsistencies
-7. Commit + push
-8. If out of scope work detected:
+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
-9. Document: `autocode comment <key> "Review consistency OK"`
-10. 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

@@ -12,15 +12,14 @@ Verifier que le code s'integre harmonieusement avec l'architecture existante du
 4. Controler la gestion d'erreurs (try/catch uniforme)
 5. Verifier l'usage correct des stores Pinia
 6. Corriger les incoherences
-7. Commit + push
-8. Si travail hors scope detecte :
+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
-9. Documenter : `autocode comment <key> "Review consistency OK"`
-10. 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

@@ -12,15 +12,14 @@ Identify and eliminate code duplication. Factor into reusable functions/composab
 4. Detect copy-pasted business logic
 5. Extract to composable/service/shared function if >2 usages
 6. Update all existing calls
-7. Commit + push
-8. If out of scope work detected:
+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
-9. Document: `autocode comment <key> "Review no duplication OK"`
-10. 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

@@ -12,15 +12,14 @@ Identifier et eliminer la duplication de code. Factoriser en fonctions/composabl
 4. Detecter la logique metier copiee-collee
 5. Extraire en composable/service/fonction partagee si >2 usages
 6. Mettre a jour tous les appels existants
-7. Commit + push
-8. Si travail hors scope detecte :
+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
-9. Documenter : `autocode comment <key> "Review no duplication OK"`
-10. 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

@@ -13,15 +13,14 @@ Security audit. Identify and fix potential vulnerabilities (OWASP Top 10).
 5. Ensure API keys are in .env, never in code
 6. Audit API calls (injection, XSS)
 7. Fix vulnerabilities
-8. Commit + push
-9. If out of scope work detected:
+8. 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
-10. Document: `autocode comment <key> "Review security OK"`
-11. 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

@@ -13,15 +13,14 @@ Audit securite. Identifier et corriger les vulnerabilites potentielles (OWASP To
 5. S'assurer que les cles API sont dans .env, jamais dans le code
 6. Auditer les appels API (injection, XSS)
 7. Corriger les vulnerabilites
-8. Commit + push
-9. Si travail hors scope detecte :
+8. 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
-10. Documenter : `autocode comment <key> "Review security OK"`
-11. 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

@@ -2,7 +2,15 @@
 
 ## Role
 
-Break down large requirements into smaller, focused tickets to limit responsibility and improve traceability. Create atomic tasks that can be independently implemented and verified.
+Break down large requirements into smaller, focused tickets **when needed** to limit responsibility and improve traceability. Create atomic tasks that can be independently implemented and verified.
+
+## When to Split
+
+**Use judgment** - splitting is not always necessary:
+- **Split** when the task is large, involves multiple components, or would benefit from parallel work
+- **Don't split** when the task is small, focused, or already atomic
+
+If the task is small enough to be completed in one go, proceed directly without splitting.
 
 ## Actions
 
@@ -14,10 +22,10 @@ Break down large requirements into smaller, focused tickets to limit responsibil
 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

@@ -2,8 +2,15 @@
 
 ## Rôle
 
-Découper les besoins trop importants en tickets plus petits et ciblés pour limiter la responsabilité et améliorer la
-traçabilité. Créer des tâches atomiques pouvant être implémentées et vérifiées indépendamment.
+Découper les besoins trop importants en tickets plus petits et ciblés **si nécessaire** pour limiter la responsabilité et améliorer la traçabilité. Créer des tâches atomiques pouvant être implémentées et vérifiées indépendamment.
+
+## Quand Découper
+
+**Faire preuve de jugement** - le découpage n'est pas systématique :
+- **Découper** quand la tâche est large, implique plusieurs composants, ou bénéficierait d'un travail parallèle
+- **Ne pas découper** quand la tâche est petite, ciblée, ou déjà atomique
+
+Si la tâche est suffisamment petite pour être complétée en une fois, procéder directement sans découpage.
 
 ## Actions
 
@@ -15,10 +22,10 @@ traçabilité. Créer des tâches atomiques pouvant être implémentées et vér
 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

@@ -12,15 +12,14 @@ Write AND execute E2E automated tests to prevent regressions.
 4. Describe tests clearly (describe/it)
 5. Execute tests: npx cypress run
 6. If failures: fix tests or code
-7. Commit + push tests
-8. If out of scope work detected:
+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
-9. Document: `autocode comment <key> "Cypress tests OK"`
-10. 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