@autocode-cli/autocode 0.1.9 → 0.1.10

package/dist/cli/commands/new.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"new.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/new.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAMpC;;GAEG;AACH,wBAAgB,UAAU,IAAI,OAAO,CA8CpC"}
+{"version":3,"file":"new.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/new.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAOpC;;GAEG;AACH,wBAAgB,UAAU,IAAI,OAAO,CAiEpC"}

package/dist/cli/commands/new.js

@@ -2,7 +2,8 @@
  * new command - Create a new ticket
  */
 import { Command } from 'commander';
-import { createTicket } from '../../core/ticket.js';
+import { createTicket, moveTicket } from '../../core/ticket.js';
+import { getColumnByName, getColumnBySlug, getColumns } from '../../core/column.js';
 import { getConfig } from '../../utils/config.js';
 import { logger } from '../../utils/logger.js';
 /**
@@ -18,13 +19,14 @@ export function newCommand() {
         .option('-l, --labels <labels>', 'Comma-separated labels')
         .option('-a, --acceptance <criteria>', 'Comma-separated acceptance criteria')
         .option('-s, --semver <type>', 'Semver type (major/minor/patch/none)', 'patch')
+        .option('-c, --column <column>', 'Target column (default: backlog)')
         .action((title, description, options) => {
         const config = getConfig();
         const priority = validatePriority(options.priority);
         const semver = validateSemver(options.semver);
         const labels = options.labels ? options.labels.split(',').map((l) => l.trim()) : [];
         const acceptanceCriteria = options.acceptance ? options.acceptance.split(',').map((c) => c.trim()) : [];
-        const ticket = createTicket(config.root, {
+        let ticket = createTicket(config.root, {
             title,
             priority,
             labels,
@@ -32,6 +34,22 @@ export function newCommand() {
             acceptance_criteria: acceptanceCriteria,
             semver,
         });
+        // Move to target column if specified
+        if (options.column) {
+            const targetColumn = getColumnByName(options.column) || getColumnBySlug(options.column);
+            if (!targetColumn) {
+                logger.error(`Column '${options.column}' not found`);
+                logger.info('Available columns:');
+                for (const col of getColumns()) {
+                    console.log(`  - ${col.name} (${col.slug})`);
+                }
+                process.exit(1);
+            }
+            const moved = moveTicket(config.root, ticket.key, targetColumn.name, true);
+            if (moved) {
+                ticket = moved;
+            }
+        }
         logger.success(`Created ticket ${logger.bold(ticket.key)}`);
         logger.row('Title', ticket.title);
         logger.row('Priority', logger.priority(ticket.priority));

package/dist/cli/commands/new.js.map

@@ -1 +1 @@
-{"version":3,"file":"new.js","sourceRoot":"","sources":["../../../src/cli/commands/new.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AACpC,OAAO,EAAE,YAAY,EAAE,MAAM,sBAAsB,CAAC;AACpD,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAClD,OAAO,EAAE,MAAM,EAAE,MAAM,uBAAuB,CAAC;AAG/C;;GAEG;AACH,MAAM,UAAU,UAAU;IACxB,MAAM,GAAG,GAAG,IAAI,OAAO,CAAC,KAAK,CAAC,CAAC;IAE/B,GAAG;SACA,WAAW,CAAC,qBAAqB,CAAC;SAClC,QAAQ,CAAC,SAAS,EAAE,cAAc,CAAC;SACnC,QAAQ,CAAC,eAAe,EAAE,oBAAoB,CAAC;SAC/C,MAAM,CAAC,2BAA2B,EAAE,kBAAkB,EAAE,IAAI,CAAC;SAC7D,MAAM,CAAC,uBAAuB,EAAE,wBAAwB,CAAC;SACzD,MAAM,CAAC,6BAA6B,EAAE,qCAAqC,CAAC;SAC5E,MAAM,CAAC,qBAAqB,EAAE,sCAAsC,EAAE,OAAO,CAAC;SAC9E,MAAM,CAAC,CAAC,KAAK,EAAE,WAAW,EAAE,OAAO,EAAE,EAAE;QACtC,MAAM,MAAM,GAAG,SAAS,EAAE,CAAC;QAE3B,MAAM,QAAQ,GAAG,gBAAgB,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC;QACpD,MAAM,MAAM,GAAG,cAAc,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;QAC9C,MAAM,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,CAAC,CAAC,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,GAAG,CAAC,CAAC,CAAS,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;QAC5F,MAAM,kBAAkB,GAAG,OAAO,CAAC,UAAU,CAAC,CAAC,CAAC,OAAO,CAAC,UAAU,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,GAAG,CAAC,CAAC,CAAS,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;QAEhH,MAAM,MAAM,GAAG,YAAY,CAAC,MAAM,CAAC,IAAI,EAAE;YACvC,KAAK;YACL,QAAQ;YACR,MAAM;YACN,WAAW,EAAE,WAAW,IAAI,EAAE;YAC9B,mBAAmB,EAAE,kBAAkB;YACvC,MAAM;SACP,CAAC,CAAC;QAEH,MAAM,CAAC,OAAO,CAAC,kBAAkB,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QAC5D,MAAM,CAAC,GAAG,CAAC,OAAO,EAAE,MAAM,CAAC,KAAK,CAAC,CAAC;QAClC,MAAM,CAAC,GAAG,CAAC,UAAU,EAAE,MAAM,CAAC,QAAQ,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC,CAAC;QACzD,MAAM,CAAC,GAAG,CAAC,QAAQ,EAAE,MAAM,CAAC,MAAM,CAAC,CAAC;QAEpC,IAAI,MAAM,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YACtB,MAAM,CAAC,GAAG,CAAC,QAAQ,EAAE,MAAM,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC;QAC1C,CAAC;QAED,IAAI,kBAAkB,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YAClC,MAAM,CAAC,GAAG,CAAC,YAAY,EAAE,kBAAkB,CAAC,MAAM,GAAG,WAAW,CAAC,CAAC;QACpE,CAAC;QAED,MAAM,CAAC,KAAK,EAAE,CAAC;QACf,MAAM,CAAC,IAAI,CAAC,4BAA4B,MAAM,CAAC,GAAG,EAAE,CAAC,CAAC;IACxD,CAAC,CAAC,CAAC;IAEL,OAAO,GAAG,CAAC;AACb,CAAC;AAED;;GAEG;AACH,SAAS,gBAAgB,CAAC,KAAa;IACrC,MAAM,KAAK,GAAe,CAAC,IAAI,EAAE,IAAI,EAAE,IAAI,EAAE,IAAI,CAAC,CAAC;IACnD,MAAM,KAAK,GAAG,KAAK,CAAC,WAAW,EAAc,CAAC;IAE9C,IAAI,KAAK,CAAC,QAAQ,CAAC,KAAK,CAAC,EAAE,CAAC;QAC1B,OAAO,KAAK,CAAC;IACf,CAAC;IAED,MAAM,CAAC,IAAI,CAAC,qBAAqB,KAAK,aAAa,CAAC,CAAC;IACrD,OAAO,IAAI,CAAC;AACd,CAAC;AAED;;GAEG;AACH,SAAS,cAAc,CAAC,KAAa;IACnC,MAAM,KAAK,GAAiB,CAAC,OAAO,EAAE,OAAO,EAAE,OAAO,EAAE,MAAM,CAAC,CAAC;IAChE,MAAM,KAAK,GAAG,KAAK,CAAC,WAAW,EAAgB,CAAC;IAEhD,IAAI,KAAK,CAAC,QAAQ,CAAC,KAAK,CAAC,EAAE,CAAC;QAC1B,OAAO,KAAK,CAAC;IACf,CAAC;IAED,MAAM,CAAC,IAAI,CAAC,mBAAmB,KAAK,gBAAgB,CAAC,CAAC;IACtD,OAAO,OAAO,CAAC;AACjB,CAAC"}
+{"version":3,"file":"new.js","sourceRoot":"","sources":["../../../src/cli/commands/new.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AACpC,OAAO,EAAE,YAAY,EAAE,UAAU,EAAE,MAAM,sBAAsB,CAAC;AAChE,OAAO,EAAE,eAAe,EAAE,eAAe,EAAE,UAAU,EAAE,MAAM,sBAAsB,CAAC;AACpF,OAAO,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAClD,OAAO,EAAE,MAAM,EAAE,MAAM,uBAAuB,CAAC;AAG/C;;GAEG;AACH,MAAM,UAAU,UAAU;IACxB,MAAM,GAAG,GAAG,IAAI,OAAO,CAAC,KAAK,CAAC,CAAC;IAE/B,GAAG;SACA,WAAW,CAAC,qBAAqB,CAAC;SAClC,QAAQ,CAAC,SAAS,EAAE,cAAc,CAAC;SACnC,QAAQ,CAAC,eAAe,EAAE,oBAAoB,CAAC;SAC/C,MAAM,CAAC,2BAA2B,EAAE,kBAAkB,EAAE,IAAI,CAAC;SAC7D,MAAM,CAAC,uBAAuB,EAAE,wBAAwB,CAAC;SACzD,MAAM,CAAC,6BAA6B,EAAE,qCAAqC,CAAC;SAC5E,MAAM,CAAC,qBAAqB,EAAE,sCAAsC,EAAE,OAAO,CAAC;SAC9E,MAAM,CAAC,uBAAuB,EAAE,kCAAkC,CAAC;SACnE,MAAM,CAAC,CAAC,KAAK,EAAE,WAAW,EAAE,OAAO,EAAE,EAAE;QACtC,MAAM,MAAM,GAAG,SAAS,EAAE,CAAC;QAE3B,MAAM,QAAQ,GAAG,gBAAgB,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC;QACpD,MAAM,MAAM,GAAG,cAAc,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;QAC9C,MAAM,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,CAAC,CAAC,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,GAAG,CAAC,CAAC,CAAS,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;QAC5F,MAAM,kBAAkB,GAAG,OAAO,CAAC,UAAU,CAAC,CAAC,CAAC,OAAO,CAAC,UAAU,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,GAAG,CAAC,CAAC,CAAS,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;QAEhH,IAAI,MAAM,GAAG,YAAY,CAAC,MAAM,CAAC,IAAI,EAAE;YACrC,KAAK;YACL,QAAQ;YACR,MAAM;YACN,WAAW,EAAE,WAAW,IAAI,EAAE;YAC9B,mBAAmB,EAAE,kBAAkB;YACvC,MAAM;SACP,CAAC,CAAC;QAEH,qCAAqC;QACrC,IAAI,OAAO,CAAC,MAAM,EAAE,CAAC;YACnB,MAAM,YAAY,GAAG,eAAe,CAAC,OAAO,CAAC,MAAM,CAAC,IAAI,eAAe,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;YACxF,IAAI,CAAC,YAAY,EAAE,CAAC;gBAClB,MAAM,CAAC,KAAK,CAAC,WAAW,OAAO,CAAC,MAAM,aAAa,CAAC,CAAC;gBACrD,MAAM,CAAC,IAAI,CAAC,oBAAoB,CAAC,CAAC;gBAClC,KAAK,MAAM,GAAG,IAAI,UAAU,EAAE,EAAE,CAAC;oBAC/B,OAAO,CAAC,GAAG,CAAC,OAAO,GAAG,CAAC,IAAI,KAAK,GAAG,CAAC,IAAI,GAAG,CAAC,CAAC;gBAC/C,CAAC;gBACD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;YAClB,CAAC;YAED,MAAM,KAAK,GAAG,UAAU,CAAC,MAAM,CAAC,IAAI,EAAE,MAAM,CAAC,GAAG,EAAE,YAAY,CAAC,IAAI,EAAE,IAAI,CAAC,CAAC;YAC3E,IAAI,KAAK,EAAE,CAAC;gBACV,MAAM,GAAG,KAAK,CAAC;YACjB,CAAC;QACH,CAAC;QAED,MAAM,CAAC,OAAO,CAAC,kBAAkB,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QAC5D,MAAM,CAAC,GAAG,CAAC,OAAO,EAAE,MAAM,CAAC,KAAK,CAAC,CAAC;QAClC,MAAM,CAAC,GAAG,CAAC,UAAU,EAAE,MAAM,CAAC,QAAQ,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC,CAAC;QACzD,MAAM,CAAC,GAAG,CAAC,QAAQ,EAAE,MAAM,CAAC,MAAM,CAAC,CAAC;QAEpC,IAAI,MAAM,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YACtB,MAAM,CAAC,GAAG,CAAC,QAAQ,EAAE,MAAM,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC;QAC1C,CAAC;QAED,IAAI,kBAAkB,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YAClC,MAAM,CAAC,GAAG,CAAC,YAAY,EAAE,kBAAkB,CAAC,MAAM,GAAG,WAAW,CAAC,CAAC;QACpE,CAAC;QAED,MAAM,CAAC,KAAK,EAAE,CAAC;QACf,MAAM,CAAC,IAAI,CAAC,4BAA4B,MAAM,CAAC,GAAG,EAAE,CAAC,CAAC;IACxD,CAAC,CAAC,CAAC;IAEL,OAAO,GAAG,CAAC;AACb,CAAC;AAED;;GAEG;AACH,SAAS,gBAAgB,CAAC,KAAa;IACrC,MAAM,KAAK,GAAe,CAAC,IAAI,EAAE,IAAI,EAAE,IAAI,EAAE,IAAI,CAAC,CAAC;IACnD,MAAM,KAAK,GAAG,KAAK,CAAC,WAAW,EAAc,CAAC;IAE9C,IAAI,KAAK,CAAC,QAAQ,CAAC,KAAK,CAAC,EAAE,CAAC;QAC1B,OAAO,KAAK,CAAC;IACf,CAAC;IAED,MAAM,CAAC,IAAI,CAAC,qBAAqB,KAAK,aAAa,CAAC,CAAC;IACrD,OAAO,IAAI,CAAC;AACd,CAAC;AAED;;GAEG;AACH,SAAS,cAAc,CAAC,KAAa;IACnC,MAAM,KAAK,GAAiB,CAAC,OAAO,EAAE,OAAO,EAAE,OAAO,EAAE,MAAM,CAAC,CAAC;IAChE,MAAM,KAAK,GAAG,KAAK,CAAC,WAAW,EAAgB,CAAC;IAEhD,IAAI,KAAK,CAAC,QAAQ,CAAC,KAAK,CAAC,EAAE,CAAC;QAC1B,OAAO,KAAK,CAAC;IACf,CAAC;IAED,MAAM,CAAC,IAAI,CAAC,mBAAmB,KAAK,gBAAgB,CAAC,CAAC;IACtD,OAAO,OAAO,CAAC;AACjB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@autocode-cli/autocode",
-  "version": "0.1.9",
+  "version": "0.1.10",
   "description": "Filesystem-based ticket system with web dashboard",
   "type": "module",
   "main": "dist/index.js",

package/templates/prompts/backlog.en.md

@@ -12,7 +12,10 @@ Storage for new tickets. Tickets here need qualification before work can begin.
 4. Define acceptance criteria if missing
 5. Set priority (P0-P3) based on impact and urgency
 6. Identify scope and potentially affected files
-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 done"`
 9. Advance: `autocode next <key>`
 

package/templates/prompts/backlog.fr.md

@@ -12,7 +12,10 @@ Stockage des nouveaux tickets. Les tickets ici doivent etre qualifies avant de c
 4. Definir les criteres d'acceptation si manquants
 5. Definir la priorite (P0-P3) selon l'impact et l'urgence
 6. Identifier le perimetre et les fichiers potentiellement impactes
-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> "Qualification effectuee"`
 9. Avancer : `autocode next <key>`
 

package/templates/prompts/changelog.en.md

@@ -13,7 +13,10 @@ Update the changelog with the changes made in this ticket. Document for users an
 5. Use clear, user-facing language
 6. Reference ticket key if applicable
 7. Commit + push changelog update
-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> "Changelog updated"`
 10. Advance: `autocode next <key>`
 

package/templates/prompts/changelog.fr.md

@@ -13,7 +13,10 @@ Mettre a jour le changelog avec les changements effectues dans ce ticket. Docume
 5. Utiliser un langage clair oriente utilisateur
 6. Referencer la cle du ticket si applicable
 7. Commit + push de la mise a jour du changelog
-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> "Changelog mis a jour"`
 10. Avancer : `autocode next <key>`
 

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

@@ -14,7 +14,10 @@ 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. If out of scope work detected: `autocode new "<title>" "<description>" -p P0 -l "urgent" -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> "Deployed to production: v<version>"`
 11. Advance: `autocode next <key>`
 

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

@@ -14,7 +14,10 @@ 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. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P0 -l "urgent" -a "<criteres>" -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> "Deploye en production : v<version>"`
 11. Avancer : `autocode next <key>`
 

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

@@ -11,7 +11,10 @@ Deploy changes to staging environment for validation.
 3. Wait for deployment to complete
 4. Verify deployment is stable
 5. Document deployed version
-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> "Deployed to staging"`
 8. Advance: `autocode next <key>`
 

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

@@ -11,7 +11,10 @@ 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. 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> "Deploye en staging"`
 8. Avancer : `autocode next <key>`
 

package/templates/prompts/design.en.md

@@ -12,7 +12,10 @@ Create technical and/or UX design for the feature. Prepare mockups, diagrams, or
 4. Create sequence diagrams for complex flows
 5. Define state management approach if applicable
 6. Document design decisions and trade-offs
-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> "Design complete: <summary>"`
 9. Advance: `autocode next <key>`
 

package/templates/prompts/design.fr.md

@@ -12,7 +12,10 @@ Creer le design technique et/ou UX pour la fonctionnalite. Preparer les maquette
 4. Creer des diagrammes de sequence pour les flux complexes
 5. Definir l'approche de gestion d'etat si applicable
 6. Documenter les decisions de design et compromis
-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> "Design termine : <resume>"`
 9. Avancer : `autocode next <key>`
 

package/templates/prompts/dev.en.md

@@ -13,7 +13,10 @@ Implement the feature or fix according to specifications. Write clean, maintaina
 5. Handle edge cases and errors gracefully
 6. Test locally before committing
 7. Commit + push with descriptive message
-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> "Development complete: <files modified>"`
 10. Advance: `autocode next <key>`
 

package/templates/prompts/dev.fr.md

@@ -13,7 +13,10 @@ Implementer la fonctionnalite ou le correctif selon les specifications. Ecrire d
 5. Gerer les cas limites et erreurs elegamment
 6. Tester localement avant de commiter
 7. Commit + push avec message descriptif
-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> "Developpement termine : <fichiers modifies>"`
 10. Avancer : `autocode next <key>`
 

package/templates/prompts/done.en.md

@@ -8,7 +8,9 @@ Archive of completed and validated tickets. End of workflow.
 
 1. Document: `autocode comment <key> "Ticket completed"`
 
-> If problem discovered: `autocode move <key> <targetColumn>` or `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+> If problem discovered: `autocode move <key> <targetColumn>` or create a new ticket:
+>   - 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`
 
 ## Validation Criteria
 

package/templates/prompts/done.fr.md

@@ -8,7 +8,9 @@ Archive des tickets termines et valides. Fin du workflow.
 
 1. Documenter : `autocode comment <key> "Ticket termine"`
 
-> Si probleme decouvert : `autocode move <key> <targetColumn>` ou `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+> Si probleme decouvert : `autocode move <key> <targetColumn>` ou creer un nouveau ticket :
+>   - 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`
 
 ## Criteres de Validation
 

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

@@ -17,7 +17,10 @@ Create a clean, atomic git commit for the changes. Follow conventional commit fo
 4. Include ticket key in commit body
 5. Create commit: `git commit -m "<type>: <description>"`
 6. Verify commit: `git log -1`
-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> "Committed: <commit hash>"`
 9. Advance: `autocode next <key>`
 

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

@@ -17,7 +17,10 @@ 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. 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> "Commite : <hash du commit>"`
 9. Avancer : `autocode next <key>`
 

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

@@ -13,7 +13,10 @@ 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. 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> "Pushed to <branch>"`
 10. Advance: `autocode next <key>`
 

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

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

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

@@ -14,7 +14,10 @@ Create a version tag for the release. Follow semantic versioning.
 3. Create annotated tag: `git tag -a v<version> -m "<release notes>"`
 4. Push tag: `git push origin v<version>`
 5. Verify tag on remote
-6. If out of scope work detected: `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>`
 

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

@@ -14,7 +14,10 @@ Creer un tag de version pour la release. Suivre le versionnement semantique.
 3. Creer un tag annote : `git tag -a v<version> -m "<notes de release>"`
 4. Pousser le tag : `git push origin v<version>`
 5. Verifier le tag sur le distant
-6. Si travail hors scope detecte : `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>`
 

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

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

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

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

package/templates/prompts/qualification.en.md

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

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

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

package/templates/prompts/ready.fr.md

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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/testing-cypress.en.md

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

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

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

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

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

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

@@ -14,7 +14,10 @@ Executer les tests d'integration pour verifier que les composants fonctionnent c
 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`
+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> "Tests d'integration OK"`
 11. Avancer : `autocode next <key>`
 

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

@@ -14,7 +14,10 @@ Write and run unit tests for the implemented feature. Ensure code coverage and r
 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`
+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> "Unit tests passed: <coverage>%"`
 11. Advance: `autocode next <key>`
 

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

@@ -14,7 +14,10 @@ Ecrire et executer les tests unitaires pour la fonctionnalite implementee. Assur
 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`
+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> "Tests unitaires OK : <couverture>%"`
 11. Avancer : `autocode next <key>`
 

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

@@ -12,7 +12,10 @@ Document changes for future developers and users.
 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`
+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> "Documentation updated"`
 9. Advance: `autocode next <key>`
 

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

@@ -12,7 +12,10 @@ Documenter les changements pour les futurs developpeurs et utilisateurs.
 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`
+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> "Documentation mise a jour"`
 9. Avancer : `autocode next <key>`
 

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

@@ -13,7 +13,10 @@ Final validation: verify everything works in staging AND git repo is clean.
 5. Verify visually everything is OK
 6. Capture proof (screenshot)
 7. Confirm feature works
-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> "Staging validation OK"`
 10. Advance: `autocode next <key>`
 

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

@@ -13,7 +13,10 @@ Validation finale : verifier que tout fonctionne en staging ET que le repo git e
 5. Verifier visuellement que tout est OK
 6. Capturer une preuve (screenshot)
 7. Confirmer que la feature fonctionne
-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> "Validation staging OK"`
 10. Avancer : `autocode next <key>`