@autocode-cli/autocode 0.1.8 → 0.1.10

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

@@ -13,11 +13,14 @@ Pousser les changements commites vers le depot distant. S'assurer que les pipeli
 5. Verifier que le push a reussi
 6. Verifier le statut du pipeline CI/CD
 7. Si le pipeline echoue : corriger les problemes et re-pousser
-8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+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
 9. Documenter : `autocode comment <key> "Pousse vers <branche>"`
 10. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

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

@@ -14,11 +14,14 @@ 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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

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

@@ -14,11 +14,14 @@ 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 : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+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> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

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

@@ -12,11 +12,14 @@ Active development. Ticket is being worked on, code is being written.
 4. Implement the solution
 5. Test locally that it works
 6. Commit + push work done
-7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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> "Work completed"`
 9. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

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

@@ -12,11 +12,14 @@ Developpement actif. Le ticket est en cours de travail, le code est en cours d'e
 4. Implementer la solution
 5. Tester localement que ca fonctionne
 6. Commit + push du travail effectue
-7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+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> "Travail effectue"`
 9. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

package/templates/prompts/qualification.en.md

@@ -12,11 +12,14 @@ Analyze and qualify the ticket requirement. Ensure the request is clear, feasibl
 4. Estimate complexity (simple/medium/complex)
 5. Identify dependencies with other tickets or systems
 6. If clarification needed: add comment with questions
-7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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> "Qualification complete: <summary>"`
 9. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

package/templates/prompts/qualification.fr.md

@@ -12,11 +12,14 @@ Analyser et qualifier le besoin du ticket. S'assurer que la demande est claire,
 4. Estimer la complexite (simple/moyenne/complexe)
 5. Identifier les dependances avec d'autres tickets ou systemes
 6. Si clarification necessaire : ajouter un commentaire avec les questions
-7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+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> "Qualification terminee : <resume>"`
 9. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

package/templates/prompts/ready.en.md

@@ -12,11 +12,14 @@ Qualified tickets ready to be worked on. All information needed is available.
 4. Implement the solution
 5. Test locally that it works
 6. Commit + push work done
-7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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> "Work completed"`
 9. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

package/templates/prompts/ready.fr.md

@@ -12,11 +12,14 @@ Tickets qualifies prets a etre travailles. Toutes les informations necessaires s
 4. Implementer la solution
 5. Tester localement que ca fonctionne
 6. Commit + push du travail effectue
-7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+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> "Travail effectue"`
 9. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

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

@@ -11,11 +11,14 @@ Re-run all automated E2E tests to ensure refactoring did not introduce regressio
 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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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> "Retest Cypress OK"`
 8. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

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

@@ -11,11 +11,14 @@ Re-executer tous les tests E2E automatises pour s'assurer que le refactoring n'a
 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 : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+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> "Retest Cypress OK"`
 8. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

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

@@ -12,11 +12,14 @@ Post-refactoring validation with Playwright. Verify that refactoring did not bre
 4. Verify edge cases still work
 5. Compare behavior with pre-refactoring state
 6. If regression detected: return to review step
-7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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> "Retest Playwright OK"`
 9. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

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

@@ -12,11 +12,14 @@ Validation post-refactoring avec Playwright. Verifier que le refactoring n'a pas
 4. Verifier que les cas limites fonctionnent toujours
 5. Comparer le comportement avec l'etat pre-refactoring
 6. Si regression detectee : retour a l'etape de review
-7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+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> "Retest Playwright OK"`
 9. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

package/templates/prompts/retest.en.md

@@ -13,11 +13,14 @@ Re-run all tests after bug fixes or corrections. Ensure no regressions were intr
 5. Verify the original issue is fixed
 6. Check for regressions in related functionality
 7. If tests fail: return to appropriate column for fixes
-8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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
 9. Document: `autocode comment <key> "Retest passed: all tests green"`
 10. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

package/templates/prompts/retest.fr.md

@@ -13,11 +13,14 @@ Re-executer tous les tests apres corrections de bugs. S'assurer qu'aucune regres
 5. Verifier que le probleme original est corrige
 6. Verifier les regressions dans les fonctionnalites liees
 7. Si les tests echouent : retourner a la colonne appropriee pour corrections
-8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+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
 9. Documenter : `autocode comment <key> "Retest OK : tous les tests verts"`
 10. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

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

@@ -13,11 +13,14 @@ Code quality audit. Verify conventions and best practices are followed.
 5. Verify import organization
 6. Fix violations found
 7. Commit + push corrections
-8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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
 9. Document: `autocode comment <key> "Review best practices OK"`
 10. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

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

@@ -13,11 +13,14 @@ Audit qualite du code. Verifier que les conventions et bonnes pratiques sont res
 5. Verifier l'organisation des imports
 6. Corriger les violations trouvees
 7. Commit + push des corrections
-8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+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
 9. Documenter : `autocode comment <key> "Review best practices OK"`
 10. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

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

@@ -13,11 +13,14 @@ Perform peer code review. Ensure code quality, readability, and adherence to pro
 5. Check error handling
 6. Suggest improvements if needed
 7. If issues found: add comment with feedback and return to dev
-8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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
 9. Document: `autocode comment <key> "Code review passed: <summary>"`
 10. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

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

@@ -13,11 +13,14 @@ Effectuer une revue de code. Assurer la qualite du code, sa lisibilite et le res
 5. Verifier la gestion des erreurs
 6. Suggerer des ameliorations si necessaire
 7. Si problemes trouves : ajouter un commentaire avec feedback et retourner au dev
-8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+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
 9. Documenter : `autocode comment <key> "Code review OK : <resume>"`
 10. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

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

@@ -13,11 +13,14 @@ Verify code integrates harmoniously with existing project architecture.
 5. Verify correct Pinia store usage
 6. Fix inconsistencies
 7. Commit + push
-8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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
 9. Document: `autocode comment <key> "Review consistency OK"`
 10. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

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

@@ -13,11 +13,14 @@ Verifier que le code s'integre harmonieusement avec l'architecture existante du
 5. Verifier l'usage correct des stores Pinia
 6. Corriger les incoherences
 7. Commit + push
-8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+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
 9. Documenter : `autocode comment <key> "Review consistency OK"`
 10. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

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

@@ -13,11 +13,14 @@ Identify and eliminate code duplication. Factor into reusable functions/composab
 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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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
 9. Document: `autocode comment <key> "Review no duplication OK"`
 10. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

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

@@ -13,11 +13,14 @@ Identifier et eliminer la duplication de code. Factoriser en fonctions/composabl
 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 : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+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
 9. Documenter : `autocode comment <key> "Review no duplication OK"`
 10. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

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

@@ -14,11 +14,14 @@ Security audit. Identify and fix potential vulnerabilities (OWASP Top 10).
 6. Audit API calls (injection, XSS)
 7. Fix vulnerabilities
 8. Commit + push
-9. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+9. 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>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

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

@@ -14,11 +14,14 @@ Audit securite. Identifier et corriger les vulnerabilites potentielles (OWASP To
 6. Auditer les appels API (injection, XSS)
 7. Corriger les vulnerabilites
 8. Commit + push
-9. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+9. 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>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

package/templates/prompts/specification.en.md

@@ -12,11 +12,14 @@ Write detailed technical specifications for the ticket. Define the implementatio
 4. Define data structures if applicable
 5. Specify API contracts if applicable
 6. Document edge cases and error handling
-7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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> "Specification complete: <technical approach>"`
 9. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

package/templates/prompts/specification.fr.md

@@ -12,11 +12,14 @@ Rediger les specifications techniques detaillees pour le ticket. Definir clairem
 4. Definir les structures de donnees si applicable
 5. Specifier les contrats API si applicable
 6. Documenter les cas limites et la gestion d'erreurs
-7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+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> "Specification terminee : <approche technique>"`
 9. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

package/templates/prompts/splitter.en.md

@@ -0,0 +1,31 @@
+# Splitter
+
+## 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.
+
+## Actions
+
+1. Analyze the requirement to identify distinct functional components
+2. Identify natural boundaries between features, layers, or responsibilities
+3. Define clear acceptance criteria for each sub-ticket
+4. Ensure each split ticket is independently testable and deployable
+5. Create sub-tickets: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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>`
+
+> Or return: `autocode move <key> <targetColumn>`
+
+## Validation Criteria
+
+- [ ] All sub-tickets are atomic and independently implementable
+- [ ] No functionality from the original requirement has been forgotten
+- [ ] An integration ticket exists to verify all parts work together cohesively
+- [ ] Each sub-ticket has clear acceptance criteria
+
+## Notes
+
+Smaller tickets reduce cognitive load and merge conflicts. Always create an integration ticket to ensure the split parts form a coherent whole.

package/templates/prompts/splitter.fr.md

@@ -0,0 +1,33 @@
+# Splitter
+
+## 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.
+
+## Actions
+
+1. Analyser le besoin pour identifier les composants fonctionnels distincts
+2. Identifier les frontières naturelles entre fonctionnalités, couches ou responsabilités
+3. Définir des critères d'acceptation clairs pour chaque sous-ticket
+4. S'assurer que chaque ticket découpé est testable et déployable indépendamment
+5. Créer les sous-tickets : `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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>`
+
+> Ou retourner : `autocode move <key> <targetColumn>`
+
+## Critères de Validation
+
+- [ ] Tous les sous-tickets sont atomiques et implémentables indépendamment
+- [ ] Aucune fonctionnalité du besoin original n'a été oubliée
+- [ ] Un ticket d'intégration existe pour vérifier que toutes les parties fonctionnent ensemble
+- [ ] Chaque sous-ticket possède des critères d'acceptation clairs
+
+## Notes
+
+Les tickets plus petits réduisent la charge cognitive et les conflits de merge. Toujours créer un ticket d'intégration
+pour s'assurer que les parties découpées forment un tout cohérent.

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

@@ -13,11 +13,14 @@ Write AND execute E2E automated tests to prevent regressions.
 5. Execute tests: npx cypress run
 6. If failures: fix tests or code
 7. Commit + push tests
-8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+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
 9. Document: `autocode comment <key> "Cypress tests OK"`
 10. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria
 

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

@@ -13,11 +13,14 @@ Rediger ET executer des tests E2E automatises pour prevenir les regressions.
 5. Executer les tests : npx cypress run
 6. Si echecs : corriger les tests ou le code
 7. Commit + push des tests
-8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+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
 9. Documenter : `autocode comment <key> "Tests Cypress OK"`
 10. Avancer : `autocode next <key>`
 
-> Ou retour : `autocode move <key> <column>`
+> Ou retour : `autocode move <key> <targetColumn>`
 
 ## Criteres de Validation
 

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

@@ -14,11 +14,14 @@ Run integration tests to verify components work correctly together. Ensure syste
 6. Test external service connections
 7. Fix any failing tests
 8. Commit + push test files
-9. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+9. 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> "Integration tests passed"`
 11. Advance: `autocode next <key>`
 
-> Or return: `autocode move <key> <column>`
+> Or return: `autocode move <key> <targetColumn>`
 
 ## Validation Criteria