@autocode-cli/autocode 0.1.9 → 0.1.11

package/templates/prompts/qualification.fr.md

@@ -12,7 +12,10 @@ 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>`
 

package/templates/prompts/ready.en.md

@@ -11,10 +11,12 @@ 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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-8. Document: `autocode comment <key> "Work completed"`
-9. Advance: `autocode next <key>`
+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> "Work completed"`
+8. Advance: `autocode next <key>`
 
 > Or return: `autocode move <key> <targetColumn>`
 
@@ -22,7 +24,6 @@ Qualified tickets ready to be worked on. All information needed is available.
 
 - [ ] 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,10 +11,12 @@ 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 : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
-8. Documenter : `autocode comment <key> "Travail effectue"`
-9. Avancer : `autocode next <key>`
+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> "Travail effectue"`
+8. Avancer : `autocode next <key>`
 
 > Ou retour : `autocode move <key> <targetColumn>`
 
@@ -22,7 +24,6 @@ Tickets qualifies prets a etre travailles. Toutes les informations necessaires s
 
 - [ ] 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,10 +10,12 @@ 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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-7. Document: `autocode comment <key> "Retest Cypress OK"`
-8. Advance: `autocode next <key>`
+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
+6. Document: `autocode comment <key> "Retest Cypress OK"`
+7. Advance: `autocode next <key>`
 
 > Or return: `autocode move <key> <targetColumn>`
 

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

@@ -10,10 +10,12 @@ 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 : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
-7. Documenter : `autocode comment <key> "Retest Cypress OK"`
-8. Avancer : `autocode next <key>`
+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
+6. Documenter : `autocode comment <key> "Retest Cypress OK"`
+7. Avancer : `autocode next <key>`
 
 > Ou retour : `autocode move <key> <targetColumn>`
 

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

@@ -12,7 +12,10 @@ 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>`
 

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

@@ -12,7 +12,10 @@ 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>`
 

package/templates/prompts/retest.en.md

@@ -13,7 +13,10 @@ 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>`
 

package/templates/prompts/retest.fr.md

@@ -13,7 +13,10 @@ 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>`
 

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

@@ -12,10 +12,12 @@ 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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-9. Document: `autocode comment <key> "Review best practices OK"`
-10. Advance: `autocode next <key>`
+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> "Review best practices OK"`
+9. Advance: `autocode next <key>`
 
 > Or return: `autocode move <key> <targetColumn>`
 

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

@@ -12,10 +12,12 @@ 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 : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
-9. Documenter : `autocode comment <key> "Review best practices OK"`
-10. Avancer : `autocode next <key>`
+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> "Review best practices OK"`
+9. Avancer : `autocode next <key>`
 
 > Ou retour : `autocode move <key> <targetColumn>`
 

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

@@ -13,7 +13,10 @@ 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>`
 

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

@@ -13,7 +13,10 @@ 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>`
 

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

@@ -12,10 +12,12 @@ 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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-9. Document: `autocode comment <key> "Review consistency OK"`
-10. Advance: `autocode next <key>`
+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> "Review consistency OK"`
+9. Advance: `autocode next <key>`
 
 > Or return: `autocode move <key> <targetColumn>`
 

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

@@ -12,10 +12,12 @@ 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 : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
-9. Documenter : `autocode comment <key> "Review consistency OK"`
-10. Avancer : `autocode next <key>`
+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> "Review consistency OK"`
+9. Avancer : `autocode next <key>`
 
 > Ou retour : `autocode move <key> <targetColumn>`
 

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

@@ -12,10 +12,12 @@ 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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-9. Document: `autocode comment <key> "Review no duplication OK"`
-10. Advance: `autocode next <key>`
+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> "Review no duplication OK"`
+9. Advance: `autocode next <key>`
 
 > Or return: `autocode move <key> <targetColumn>`
 

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

@@ -12,10 +12,12 @@ 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 : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
-9. Documenter : `autocode comment <key> "Review no duplication OK"`
-10. Avancer : `autocode next <key>`
+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> "Review no duplication OK"`
+9. Avancer : `autocode next <key>`
 
 > Ou retour : `autocode move <key> <targetColumn>`
 

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

@@ -13,10 +13,12 @@ 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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-10. Document: `autocode comment <key> "Review security OK"`
-11. Advance: `autocode next <key>`
+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 security OK"`
+10. Advance: `autocode next <key>`
 
 > Or return: `autocode move <key> <targetColumn>`
 

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

@@ -13,10 +13,12 @@ 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 : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
-10. Documenter : `autocode comment <key> "Review security OK"`
-11. Avancer : `autocode next <key>`
+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 security OK"`
+10. Avancer : `autocode next <key>`
 
 > Ou retour : `autocode move <key> <targetColumn>`
 

package/templates/prompts/specification.en.md

@@ -12,7 +12,10 @@ 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>`
 

package/templates/prompts/specification.fr.md

@@ -12,7 +12,10 @@ 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>`
 

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
 

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
 

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

@@ -12,10 +12,12 @@ 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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-9. Document: `autocode comment <key> "Cypress tests OK"`
-10. Advance: `autocode next <key>`
+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> "Cypress tests OK"`
+9. Advance: `autocode next <key>`
 
 > Or return: `autocode move <key> <targetColumn>`
 

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

@@ -12,10 +12,12 @@ Rediger ET executer des tests E2E automatises pour prevenir les regressions.
 4. Decrire les tests clairement (describe/it)
 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`
-9. Documenter : `autocode comment <key> "Tests Cypress OK"`
-10. Avancer : `autocode next <key>`
+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> "Tests Cypress OK"`
+9. Avancer : `autocode next <key>`
 
 > Ou retour : `autocode move <key> <targetColumn>`
 

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

@@ -13,10 +13,12 @@ Run integration tests to verify components work correctly together. Ensure syste
 5. Test database operations
 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`
-10. Document: `autocode comment <key> "Integration tests passed"`
-11. Advance: `autocode next <key>`
+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> "Integration tests passed"`
+10. Advance: `autocode next <key>`
 
 > Or return: `autocode move <key> <targetColumn>`
 

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

@@ -13,10 +13,12 @@ Executer les tests d'integration pour verifier que les composants fonctionnent c
 5. Tester les operations base de donnees
 6. Tester les connexions aux services externes
 7. Corriger les tests en echec
-8. Commit + push des fichiers de test
-9. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
-10. Documenter : `autocode comment <key> "Tests d'integration OK"`
-11. Avancer : `autocode next <key>`
+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 d'integration OK"`
+10. Avancer : `autocode next <key>`
 
 > Ou retour : `autocode move <key> <targetColumn>`
 

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

@@ -12,7 +12,10 @@ Live functional testing with Playwright. Manually verify feature works by naviga
 4. Test edge cases
 5. Verify error handling
 6. Capture screenshots if needed
-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> "Playwright tests OK"`
 9. Advance: `autocode next <key>`
 

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

@@ -12,7 +12,10 @@ Test fonctionnel live avec Playwright. Verifier manuellement que la feature fonc
 4. Tester les cas limites
 5. Verifier la gestion d'erreurs
 6. Capturer des screenshots si necessaire
-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> "Tests Playwright OK"`
 9. Avancer : `autocode next <key>`
 

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

@@ -13,10 +13,12 @@ Write and run unit tests for the implemented feature. Ensure code coverage and r
 5. Run all unit tests: `npm test` or equivalent
 6. Fix any failing tests
 7. Verify coverage meets project standards
-8. Commit + push test files
-9. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-10. Document: `autocode comment <key> "Unit tests passed: <coverage>%"`
-11. Advance: `autocode next <key>`
+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> "Unit tests passed: <coverage>%"`
+10. Advance: `autocode next <key>`
 
 > Or return: `autocode move <key> <targetColumn>`
 

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

@@ -13,10 +13,12 @@ Ecrire et executer les tests unitaires pour la fonctionnalite implementee. Assur
 5. Executer tous les tests unitaires : `npm test` ou equivalent
 6. Corriger les tests en echec
 7. Verifier que la couverture respecte les standards du projet
-8. Commit + push des fichiers de test
-9. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
-10. Documenter : `autocode comment <key> "Tests unitaires OK : <couverture>%"`
-11. Avancer : `autocode next <key>`
+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 unitaires OK : <couverture>%"`
+10. Avancer : `autocode next <key>`
 
 > Ou retour : `autocode move <key> <targetColumn>`
 

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

@@ -11,10 +11,12 @@ Document changes for future developers and users.
 3. Document new features
 4. Update existing guides if impacted
 5. Verify doc consistency
-6. Commit + push
-7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-8. Document: `autocode comment <key> "Documentation updated"`
-9. Advance: `autocode next <key>`
+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> "Documentation updated"`
+8. Advance: `autocode next <key>`
 
 > Or return: `autocode move <key> <targetColumn>`
 

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

@@ -11,10 +11,12 @@ Documenter les changements pour les futurs developpeurs et utilisateurs.
 3. Documenter les nouvelles features
 4. Mettre a jour les guides existants si impactes
 5. Verifier la coherence de la doc
-6. Commit + push
-7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
-8. Documenter : `autocode comment <key> "Documentation mise a jour"`
-9. Avancer : `autocode next <key>`
+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> "Documentation mise a jour"`
+8. Avancer : `autocode next <key>`
 
 > Ou retour : `autocode move <key> <targetColumn>`