@autocode-cli/autocode 0.22.0 → 0.23.0

package/templates/prompts/_transition-decision.en.md

@@ -0,0 +1,69 @@
+# AutoProcess Transition Decision
+
+You are the **transition decider** for AutoCode. After Claude finishes its work on a column, you decide the next action.
+
+## Context
+
+- **Issue**: {key}
+- **Title**: {title}
+- **Current column**: {currentColumn}
+- **Available columns**: {columnsList}
+
+## Recent history
+
+{history}
+
+## Claude's last comment
+
+{lastComment}
+
+## Your mission
+
+Analyze the work done and decide the next action:
+
+| Action | When to use |
+|--------|-------------|
+| `NEXT` | Work completed successfully, move to next column |
+| `RETRY` | Work incomplete or recoverable error, retry same column |
+| `BLOCKED` | Blocking issue detected, human intervention needed |
+| `MOVE <column>` | Go to a specific column (e.g., back to qualification) |
+
+## Decision criteria
+
+### NEXT - Move forward
+- Comment indicates work is complete
+- No blocking errors mentioned
+- Column objectives appear to be met
+
+### RETRY - Try again
+- Temporary or recoverable error
+- Work partially done
+- Minor correction needed
+
+### BLOCKED - Block
+- Critical non-recoverable error
+- Missing information that requires human
+- Conflict or ambiguity in requirements
+- Tests failing repeatedly
+
+### MOVE <column> - Redirect
+- `MOVE 01_qualification`: missing information in ticket
+- `MOVE 02_splitter`: ticket too complex, needs splitting
+- Other column based on context
+
+## Response format
+
+Reply ONLY with a single line in this format:
+
+```
+ACTION [short reason]
+```
+
+Examples:
+- `NEXT [Qualification completed successfully]`
+- `RETRY [Build error, correction needed]`
+- `BLOCKED [Tests failing, unknown cause]`
+- `MOVE 01_qualification [Missing acceptance criteria]`
+
+## Response
+

package/templates/prompts/_transition-decision.fr.md

@@ -0,0 +1,69 @@
+# Decision de Transition AutoProcess
+
+Tu es le **decideur de transition** d'AutoCode. Apres que Claude ait termine son travail sur une colonne, tu decides de la prochaine action.
+
+## Contexte
+
+- **Issue** : {key}
+- **Titre** : {title}
+- **Colonne actuelle** : {currentColumn}
+- **Colonnes disponibles** : {columnsList}
+
+## Historique recent
+
+{history}
+
+## Dernier commentaire de Claude
+
+{lastComment}
+
+## Ta mission
+
+Analyse le travail effectue et decide de la prochaine action parmi :
+
+| Action | Quand l'utiliser |
+|--------|------------------|
+| `NEXT` | Travail termine avec succes, passer a la colonne suivante |
+| `RETRY` | Travail incomplet ou erreur recuperable, reessayer la meme colonne |
+| `BLOCKED` | Probleme bloquant detecte, intervention humaine necessaire |
+| `MOVE <column>` | Aller vers une colonne specifique (ex: retour en qualification) |
+
+## Criteres de decision
+
+### NEXT - Passer a la suite
+- Le commentaire indique que le travail est termine
+- Pas d'erreur bloquante mentionnee
+- Les objectifs de la colonne semblent atteints
+
+### RETRY - Reessayer
+- Erreur temporaire ou recuperable
+- Travail partiellement effectue
+- Besoin de correction mineure
+
+### BLOCKED - Bloquer
+- Erreur critique non recuperable
+- Information manquante qui necessite un humain
+- Conflit ou ambiguite dans les requirements
+- Tests echoues de maniere repetee
+
+### MOVE <column> - Rediriger
+- `MOVE 01_qualification` : informations manquantes dans le ticket
+- `MOVE 02_splitter` : ticket trop complexe, besoin de decoupage
+- Autre colonne selon le contexte
+
+## Format de reponse
+
+Reponds UNIQUEMENT avec une ligne au format :
+
+```
+ACTION [raison courte]
+```
+
+Exemples :
+- `NEXT [Qualification terminee avec succes]`
+- `RETRY [Erreur de build, correction necessaire]`
+- `BLOCKED [Tests echouent, cause inconnue]`
+- `MOVE 01_qualification [Criteres d'acceptation manquants]`
+
+## Reponse
+

package/templates/prompts/backlog.en.md

@@ -9,9 +9,7 @@ Storage for new issues. Issues here need qualification before work can begin.
 1. Read the issue (title, description, attachments)
 2. Verify the issue is complete enough to be processed
 3. If incomplete or poorly written: add a comment requesting clarifications
-4. Advance: `autocode next <issue-key>`
-
-> Or leave in backlog if issue is not ready
+4. Document: `autocode comment <issue-key> "Backlog review: [ready/missing info]"`
 
 ## Validation Criteria
 

package/templates/prompts/backlog.fr.md

@@ -9,9 +9,7 @@ Stockage des nouveaux tickets. Les tickets ici doivent etre qualifies avant de c
 1. Lire le ticket (titre, description, pieces jointes)
 2. Verifier que le ticket est suffisamment complet pour etre traite
 3. Si incomplet ou mal redige : ajouter un commentaire demandant des clarifications
-4. Avancer : `autocode next <issue-key>`
-
-> Ou laisser en backlog si le ticket n'est pas pret
+4. Documenter : `autocode comment <issue-key> "Backlog review : [pret/manque info]"`
 
 ## Criteres de Validation
 

package/templates/prompts/changelog.en.md

@@ -12,10 +12,7 @@ Update the changelog with the changes made in this issue. Document for users and
 4. Add entry under "Unreleased" section
 5. Use clear, user-facing language
 6. Reference issue key if applicable
-7. Document: `autocode comment <issue-key> "Changelog updated"`
-8. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+7. Document: `autocode comment <issue-key> "Changelog: [updated/not applicable]"`
 
 ## Validation Criteria
 

package/templates/prompts/changelog.fr.md

@@ -12,10 +12,7 @@ Mettre a jour le changelog avec les changements effectues dans ce ticket. Docume
 4. Ajouter une entree sous la section "Unreleased"
 5. Utiliser un langage clair oriente utilisateur
 6. Referencer la cle du ticket si applicable
-7. Documenter : `autocode comment <issue-key> "Changelog mis a jour"`
-8. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+7. Documenter : `autocode comment <issue-key> "Changelog : [mis a jour/non applicable]"`
 
 ## Criteres de Validation
 

package/templates/prompts/deploy-prod.en.md

@@ -14,10 +14,7 @@ Deploy the release to production environment. Ensure zero-downtime deployment.
 6. Verify critical functionality
 7. Monitor logs for errors
 8. If issues detected: rollback immediately
-9. Document: `autocode comment <issue-key> "Deployed to production: v<version>"`
-10. Advance: `autocode next <issue-key>`
-
-> Or rollback: `autocode move <issue-key> <target-column-slug>`
+9. Document: `autocode comment <issue-key> "Deploy prod: [OK/rollback] - v<version>"`
 
 ## Validation Criteria
 

package/templates/prompts/deploy-prod.fr.md

@@ -14,10 +14,7 @@ Deployer la release en environnement de production. Assurer un deploiement sans
 6. Verifier les fonctionnalites critiques
 7. Surveiller les logs pour les erreurs
 8. Si problemes detectes : rollback immediatement
-9. Documenter : `autocode comment <issue-key> "Deploye en production : v<version>"`
-10. Avancer : `autocode next <issue-key>`
-
-> Ou rollback : `autocode move <issue-key> <target-column-slug>`
+9. Documenter : `autocode comment <issue-key> "Deploy prod : [OK/rollback] - v<version>"`
 
 ## Criteres de Validation
 

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

@@ -11,10 +11,7 @@ Deploy changes to staging environment for validation.
 3. Wait for deployment to complete
 4. Verify deployment is stable
 5. Document deployed version
-6. Document: `autocode comment <issue-key> "Deployed to staging"`
-7. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+6. Document: `autocode comment <issue-key> "Deploy staging: [OK/failed] - <version>"`
 
 ## Validation Criteria
 

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

@@ -11,10 +11,7 @@ Deployer les changements sur l'environnement de staging pour validation.
 3. Attendre la fin du deploiement
 4. Verifier que le deploiement est stable
 5. Documenter la version deployee
-6. Documenter : `autocode comment <issue-key> "Deploye en staging"`
-7. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+6. Documenter : `autocode comment <issue-key> "Deploy staging : [OK/echec] - <version>"`
 
 ## Criteres de Validation
 

package/templates/prompts/design.en.md

@@ -16,10 +16,7 @@ Create technical and/or UX design for the feature. Prepare mockups, diagrams, or
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
    - In scope: handle directly in current issue
-8. Document: `autocode comment <issue-key> "Design complete: <summary>"`
-9. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+8. Document: `autocode comment <issue-key> "Design: [complete/in progress] - <summary>"`
 
 ## Validation Criteria
 

package/templates/prompts/design.fr.md

@@ -16,10 +16,7 @@ Creer le design technique et/ou UX pour la fonctionnalite. Preparer les maquette
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <issue-key> "Design termine : <resume>"`
-9. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+8. Documenter : `autocode comment <issue-key> "Design : [termine/en cours] - <resume>"`
 
 ## Criteres de Validation
 

package/templates/prompts/dev.en.md

@@ -16,10 +16,7 @@ Implement the feature or fix according to specifications. Write clean, maintaina
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
    - In scope: handle directly in current issue
-8. Document: `autocode comment <issue-key> "Development complete: <files modified>"`
-9. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+8. Document: `autocode comment <issue-key> "Development: [complete/in progress] - <files modified>"`
 
 ## Validation Criteria
 

package/templates/prompts/dev.fr.md

@@ -16,10 +16,7 @@ Implementer la fonctionnalite ou le correctif selon les specifications. Ecrire d
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <issue-key> "Developpement termine : <fichiers modifies>"`
-9. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+8. Documenter : `autocode comment <issue-key> "Developpement : [termine/en cours] - <fichiers modifies>"`
 
 ## Criteres de Validation
 

package/templates/prompts/done.en.md

@@ -8,9 +8,8 @@ Archive of completed and validated issues. End of workflow.
 
 1. Document: `autocode comment <issue-key> "Issue completed"`
 
-> If problem discovered: `autocode move <issue-key> <target-column-slug>` or create a new issue:
->   - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
->   - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
+> If problem discovered after closure, create a new issue:
+>   - `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
 
 ## Validation Criteria
 

package/templates/prompts/done.fr.md

@@ -8,9 +8,8 @@ Archive des tickets termines et valides. Fin du workflow.
 
 1. Documenter : `autocode comment <issue-key> "Ticket termine"`
 
-> Si probleme decouvert : `autocode move <issue-key> <target-column-slug>` ou creer un nouveau ticket :
->   - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column ready`
->   - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
+> Si probleme decouvert apres cloture, creer un nouveau ticket :
+>   - `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
 
 ## Criteres de Validation
 

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

@@ -17,10 +17,7 @@ Create a clean, atomic git commit for the changes. Follow conventional commit fo
 4. Include issue key in commit body
 5. Create commit: `git commit -m "<type>: <description>"`
 6. Verify commit: `git log -1`
-7. Document: `autocode comment <issue-key> "Committed: <commit hash>"`
-8. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+7. Document: `autocode comment <issue-key> "Git commit: [OK/failed] - <hash or reason>"`
 
 ## Validation Criteria
 

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

@@ -17,10 +17,7 @@ Creer un commit git propre et atomique pour les changements. Suivre le format co
 4. Inclure la cle du ticket dans le corps du commit
 5. Creer le commit : `git commit -m "<type>: <description>"`
 6. Verifier le commit : `git log -1`
-7. Documenter : `autocode comment <issue-key> "Commite : <hash du commit>"`
-8. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+7. Documenter : `autocode comment <issue-key> "Git commit : [OK/echec] - <hash ou raison>"`
 
 ## Criteres de Validation
 

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

@@ -13,10 +13,7 @@ Push committed changes to the remote repository. Ensure CI/CD pipelines pass.
 5. Verify push succeeded
 6. Check CI/CD pipeline status
 7. If pipeline fails: fix issues and re-push
-8. Document: `autocode comment <issue-key> "Pushed to <branch>"`
-9. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+8. Document: `autocode comment <issue-key> "Git push: [OK/failed] - <branch>"`
 
 ## Validation Criteria
 

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

@@ -13,10 +13,7 @@ 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. Documenter : `autocode comment <issue-key> "Pousse vers <branche>"`
-9. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+8. Documenter : `autocode comment <issue-key> "Git push : [OK/echec] - <branche>"`
 
 ## Criteres de Validation
 

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

@@ -14,10 +14,7 @@ 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. Document: `autocode comment <issue-key> "Tagged: v<version>"`
-7. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+6. Document: `autocode comment <issue-key> "Git tag: [OK/failed] - v<version>"`
 
 ## Validation Criteria
 

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

@@ -14,10 +14,7 @@ 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. Documenter : `autocode comment <issue-key> "Tag cree : v<version>"`
-7. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+6. Documenter : `autocode comment <issue-key> "Git tag : [OK/echec] - v<version>"`
 
 ## Criteres de Validation
 

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

@@ -16,19 +16,13 @@ Active development. Issue is being worked on, code is being written.
 5. Test locally that ALL criteria pass
 6. Commit + push work done
 7. If out of scope work detected: `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
-8. Document: `autocode comment <issue-key> "Work completed: [list of changes]"`
-9. **ONLY IF ALL CRITERIA ARE SATISFIED**: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+8. Document: `autocode comment <issue-key> "Development: [complete/in progress] - [list of changes]"`
 
 ## IMPORTANT
 
-⚠️ **NEVER call `autocode next` if acceptance criteria are not ALL satisfied!**
-
 If criteria cannot be satisfied:
 - Document why with `autocode comment`
-- DO NOT advance the issue
-- Wait for human decision
+- The system will decide next steps automatically
 
 If code exists but does not match criteria:
 - MODIFY the code to match the criteria

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

@@ -17,18 +17,12 @@ Developpement actif. Le ticket est en cours de travail, le code est en cours d'e
 6. Commit + push du travail effectue
 7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<critères>" --semver patch --column backlog`
 8. Documenter : `autocode comment <issue-key> "Travail effectue : [liste des modifications]"`
-9. **SEULEMENT SI TOUS LES CRITERES SONT SATISFAITS** : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## IMPORTANT
 
-⚠️ **NE JAMAIS appeler `autocode next` si les criteres d'acceptation ne sont pas TOUS satisfaits !**
-
 Si des criteres ne peuvent pas etre satisfaits :
 - Documenter pourquoi avec `autocode comment`
-- NE PAS avancer le ticket
-- Attendre une decision humaine
+- Le systeme decidera automatiquement de la suite
 
 Si le code existe deja mais ne correspond pas aux criteres :
 - MODIFIER le code pour qu'il corresponde aux criteres

package/templates/prompts/qualification.en.md

@@ -16,10 +16,7 @@ Analyze and qualify the issue requirement. Ensure the request is clear, feasible
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
    - In scope: handle directly in current issue
-8. Document: `autocode comment <issue-key> "Qualification complete: <summary>"`
-9. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+8. Document: `autocode comment <issue-key> "Qualification: [complete/pending] - <summary>"`
 
 ## Validation Criteria
 

package/templates/prompts/qualification.fr.md

@@ -17,9 +17,6 @@ Analyser et qualifier le besoin du ticket. S'assurer que la demande est claire,
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
    - Dans le scope : traiter directement dans le ticket actuel
 8. Documenter : `autocode comment <issue-key> "Qualification terminee : <resume>"`
-9. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/ready.en.md

@@ -10,12 +10,9 @@ Validate that the ticket is ready for development. This column confirms that all
 2. Verify the description is complete and understandable
 3. Verify acceptance criteria are defined and measurable
 4. Verify priority is correctly assigned
-5. If information is missing: `autocode move <issue-key> 01_qualification`
-6. If ticket is too large: `autocode move <issue-key> 02_splitter`
-7. Document: `autocode comment <issue-key> "Ticket ready for development"`
-8. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+5. If information is missing: document in comment
+6. If ticket is too large: document in comment
+7. Document: `autocode comment <issue-key> "Status: [ready/missing info/too large]"`
 
 ## Validation Criteria
 

package/templates/prompts/ready.fr.md

@@ -10,12 +10,9 @@ Valider que le ticket est pret pour le developpement. Cette colonne confirme que
 2. Verifier que la description est complete et comprehensible
 3. Verifier que les criteres d'acceptation sont definis et mesurables
 4. Verifier que la priorite est correctement assignee
-5. Si des informations manquent : `autocode move <issue-key> 01_qualification`
-6. Si le ticket est trop gros : `autocode move <issue-key> 02_splitter`
-7. Documenter : `autocode comment <issue-key> "Ticket pret pour developpement"`
-8. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+5. Si des informations manquent : documenter dans le commentaire
+6. Si le ticket est trop gros : documenter dans le commentaire
+7. Documenter : `autocode comment <issue-key> "Statut : [pret/manque info/trop gros]"`
 
 ## Criteres de Validation
 

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

@@ -10,10 +10,7 @@ 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. Document: `autocode comment <issue-key> "Retest Cypress OK"`
-6. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+5. Document: `autocode comment <issue-key> "Retest Cypress: [passed/failed] - <details>"`
 
 ## Validation Criteria
 

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

@@ -10,10 +10,7 @@ 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. Documenter : `autocode comment <issue-key> "Retest Cypress OK"`
-6. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+5. Documenter : `autocode comment <issue-key> "Retest Cypress : [OK/echecs] - <details>"`
 
 ## Criteres de Validation
 

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

@@ -13,10 +13,7 @@ Post-refactoring validation with Playwright. Verify that refactoring did not bre
 5. Compare behavior with pre-refactoring state
 6. If regression detected: return to review step
 7. Do not test functionality outside the issue scope
-8. Document: `autocode comment <issue-key> "Retest Playwright OK"`
-9. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+8. Document: `autocode comment <issue-key> "Retest Playwright: [passed/failed] - <details>"`
 
 ## Validation Criteria
 

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

@@ -13,10 +13,7 @@ Validation post-refactoring avec Playwright. Verifier que le refactoring n'a pas
 5. Comparer le comportement avec l'etat pre-refactoring
 6. Si regression detectee : retour a l'etape de review
 7. Ne pas tester de fonctionnalites hors scope du ticket
-8. Documenter : `autocode comment <issue-key> "Retest Playwright OK"`
-9. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+8. Documenter : `autocode comment <issue-key> "Retest Playwright : [OK/echecs] - <details>"`
 
 ## Criteres de Validation
 

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

@@ -11,10 +11,7 @@ Re-run unit tests after development work to verify no regressions were introduce
 3. If regressions found, identify the changes that caused them
 4. If tests fail: return to dev column for fixes
 5. Verify test coverage has not decreased
-6. Document: `autocode comment <issue-key> "Unit tests passed: X/X tests green"`
-7. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+6. Document: `autocode comment <issue-key> "Retest unit: [passed/failed] - X/X tests green"`
 
 ## Validation Criteria
 

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

@@ -11,10 +11,7 @@ Relancer les tests unitaires après le travail de développement pour vérifier
 3. Si des régressions sont trouvées, identifier les modifications qui les ont causées
 4. Si des tests échouent : retourner en dev pour correction
 5. Vérifier que la couverture de tests n'a pas diminué
-6. Documenter : `autocode comment <issue-key> "Tests unitaires passés : X/X tests verts"`
-7. Avancer : `autocode next <issue-key>`
-
-> Ou retourner : `autocode move <issue-key> <target-column-slug>`
+6. Documenter : `autocode comment <issue-key> "Retest unit : [OK/echecs] - X/X tests verts"`
 
 ## Critères de Validation
 

package/templates/prompts/retest.en.md

@@ -14,10 +14,7 @@ Re-run all tests after bug fixes or corrections. Ensure no regressions were intr
 6. Check for regressions in related functionality
 7. If tests fail: return to appropriate column for fixes
 8. Do not write tests for code outside the issue scope
-9. Document: `autocode comment <issue-key> "Retest passed: all tests green"`
-10. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+9. Document: `autocode comment <issue-key> "Retest: [passed/failed] - <details>"`
 
 ## Validation Criteria
 

package/templates/prompts/retest.fr.md

@@ -14,10 +14,7 @@ Re-executer tous les tests apres corrections de bugs. S'assurer qu'aucune regres
 6. Verifier les regressions dans les fonctionnalites liees
 7. Si les tests echouent : retourner a la colonne appropriee pour corrections
 8. Ne pas ecrire de tests pour du code hors scope du ticket
-9. Documenter : `autocode comment <issue-key> "Retest OK : tous les tests verts"`
-10. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+9. Documenter : `autocode comment <issue-key> "Retest : [OK/echecs] - <details>"`
 
 ## Criteres de Validation
 

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

@@ -12,10 +12,7 @@ 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. Document: `autocode comment <issue-key> "Review best practices OK"`
-8. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+7. Document: `autocode comment <issue-key> "Best practices review: [passed/issues found] - <summary>"`
 
 ## Validation Criteria
 

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

@@ -12,10 +12,7 @@ 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. Documenter : `autocode comment <issue-key> "Review best practices OK"`
-8. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+7. Documenter : `autocode comment <issue-key> "Review best practices : [OK/Problemes] - <resume>"`
 
 ## Criteres de Validation