@keber/qa-framework 1.11.3 → 1.13.0

package/docs/skills-architecture.md

@@ -16,9 +16,9 @@ The 3-layer skill architecture reduces this to ~500 tokens for a typical task, l
 
 | Layer | Location | Size | Purpose |
 |---|---|---|---|
-| 1 — Descriptor | YAML frontmatter in `SKILL.md` | ~50 tokens | Name + description; used for relevance detection |
-| 2 — Process outline | `SKILL.md` body | ~400–600 tokens | Step-by-step process without code; always loaded when skill applies |
-| 3 — Reference material | `references/*.md` | ~500–1500 tokens each | Detailed templates, code patterns, decision trees; loaded on demand |
+| 1 - Descriptor | YAML frontmatter in `SKILL.md` | ~50 tokens | Name + description; used for relevance detection |
+| 2 - Process outline | `SKILL.md` body | ~400-600 tokens | Step-by-step process without code; always loaded when skill applies |
+| 3 - Reference material | `references/*.md` | ~500-1500 tokens each | Detailed templates, code patterns, decision trees; loaded on demand |
 
 The agent reads Layer 2 to understand what to do, then loads only the specific `references/` files it needs for the current step.
 
@@ -26,7 +26,7 @@ The agent reads Layer 2 to understand what to do, then loads only the specific `
 
 ## Pipeline Sequence
 
-Skills map to the QA pipeline stages defined in `copilot-instructions.md`. The file acts as a **pipeline sequencer** — it defines which stage comes before which, and what the prerequisite is. Skills are the implementation of each stage.
+Skills map to the QA pipeline stages defined in `copilot-instructions.md`. The file acts as a **pipeline sequencer** - it defines which stage comes before which, and what the prerequisite is. Skills are the implementation of each stage.
 
 ```
 Stage 1: qa-module-analysis      (no prerequisite)
@@ -61,12 +61,12 @@ Optional (any time after Stage 4):
 |---|---|---|
 | `qa-module-analysis` | Stage 1 process (4 phases) | `exploration-checklist.md`, `spec-file-formats.md` |
 | `qa-spec-generation` | Stage 2 rules + anti-patterns | `spec-file-formats.md` (shared with qa-module-analysis) |
-| `qa-test-plan` | Stage 3 — priority + feasibility rules | `priority-and-feasibility.md` (includes full template) |
-| `qa-test-cases` | Stage 4 — TC document rules | `test-case-template.md` |
-| `qa-automation` | Stage 5 — patterns + completion checklist | `patterns.md`, `config-checklist.md` |
-| `qa-test-stabilization` | Stage 5b — 8 steps + confidence scoring | `classification-protocol.md` (includes report template) |
-| `qa-ado-integration` | Optional ADO sync — 6 steps | `scripts-and-config.md` |
-| `qa-maintenance` | Stage 6 — update rules | `update-rules.md` |
+| `qa-test-plan` | Stage 3 - Plan de Pruebas generation | `plan-de-pruebas-template.md` (includes priority + feasibility rules) |
+| `qa-test-cases` | Stage 4 - TC document rules | `test-case-template.md` |
+| `qa-automation` | Stage 5 - patterns + completion checklist | `patterns.md`, `config-checklist.md` |
+| `qa-test-stabilization` | Stage 5b - 8 steps + confidence scoring | `classification-protocol.md` (includes report template) |
+| `qa-ado-integration` | Optional ADO sync - 6 steps | `scripts-and-config.md` |
+| `qa-maintenance` | Stage 6 - update rules | `update-rules.md` |
 
 ---
 
@@ -85,7 +85,7 @@ When a consumer project runs `npm install @keber/qa-framework`, the `postinstall
     SKILL.md
   ...
 
-→ copies to →
+-> copies to ->
 
 {consumer-project}/.github/skills/
   qa-module-analysis/
@@ -96,7 +96,7 @@ When a consumer project runs `npm install @keber/qa-framework`, the `postinstall
   ...
 ```
 
-The copy uses `writeIfMissing` — it will not overwrite files that already exist in the consumer project. This allows consumer projects to customize their `.github/skills/` without losing changes on re-install.
+The copy uses `writeIfMissing` - it will not overwrite files that already exist in the consumer project. This allows consumer projects to customize their `.github/skills/` without losing changes on re-install.
 
 ---
 
@@ -112,7 +112,7 @@ Consumer projects can extend the skills by adding skill folders directly to `.gi
      Describe when this skill should be triggered.
    ---
    ```
-2. Add the skill body following the same 4-section structure: prerequisite → steps → rules → outputs
+2. Add the skill body following the same 4-section structure: prerequisite -> steps -> rules -> outputs
 3. Optionally add `references/*.md` for detailed templates
 4. Reference the skill from `copilot-instructions.md` if it's part of your pipeline
 
@@ -124,13 +124,13 @@ Project-specific skills are not overwritten by `npm install` updates.
 
 | Former file | New skill | Token reduction |
 |---|---|---|
-| `agent-instructions/00-module-analysis.md` | `.github/skills/qa-module-analysis/SKILL.md` | ~2,500 → ~500 + on-demand references |
-| `agent-instructions/01-spec-generation.md` | `.github/skills/qa-spec-generation/SKILL.md` | ~2,800 → ~400 + shared references |
-| `agent-instructions/02-test-plan-generation.md` | `.github/skills/qa-test-plan/SKILL.md` | ~2,200 → ~400 + test-plan-template |
-| `agent-instructions/03-test-case-generation.md` | `.github/skills/qa-test-cases/SKILL.md` | ~2,100 → ~400 + tc-template |
-| `agent-instructions/04-automation-generation.md` | `.github/skills/qa-automation/SKILL.md` | ~3,500 → ~500 + patterns + config |
-| `agent-instructions/04b-test-stabilization.md` | `.github/skills/qa-test-stabilization/SKILL.md` | ~3,800 → ~500 + classification |
-| `agent-instructions/05-ado-integration.md` | `.github/skills/qa-ado-integration/SKILL.md` | ~2,400 → ~400 + scripts |
-| `agent-instructions/06-maintenance.md` | `.github/skills/qa-maintenance/SKILL.md` | ~1,700 → ~400 + update-rules |
-
-**Total context reduction**: ~21,000 tokens → ~3,500 tokens (Layer 2 only) + selective Layer 3 loading
+| `agent-instructions/00-module-analysis.md` | `.github/skills/qa-module-analysis/SKILL.md` | ~2,500 -> ~500 + on-demand references |
+| `agent-instructions/01-spec-generation.md` | `.github/skills/qa-spec-generation/SKILL.md` | ~2,800 -> ~400 + shared references |
+| `agent-instructions/02-test-plan-generation.md` | `.github/skills/qa-test-plan/SKILL.md` | ~2,200 -> ~400 + test-plan-template |
+| `agent-instructions/03-test-case-generation.md` | `.github/skills/qa-test-cases/SKILL.md` | ~2,100 -> ~400 + tc-template |
+| `agent-instructions/04-automation-generation.md` | `.github/skills/qa-automation/SKILL.md` | ~3,500 -> ~500 + patterns + config |
+| `agent-instructions/04b-test-stabilization.md` | `.github/skills/qa-test-stabilization/SKILL.md` | ~3,800 -> ~500 + classification |
+| `agent-instructions/05-ado-integration.md` | `.github/skills/qa-ado-integration/SKILL.md` | ~2,400 -> ~400 + scripts |
+| `agent-instructions/06-maintenance.md` | `.github/skills/qa-maintenance/SKILL.md` | ~1,700 -> ~400 + update-rules |
+
+**Total context reduction**: ~21,000 tokens -> ~3,500 tokens (Layer 2 only) + selective Layer 3 loading

package/docs/spec-driven-philosophy.md

@@ -1,6 +1,6 @@
 # docs/spec-driven-philosophy.md
 
-## Spec-Driven Automated Testing — Core Philosophy
+## Spec-Driven Automated Testing - Core Philosophy
 
 This document explains the methodology that underpins the entire `qa-framework`.
 
@@ -34,7 +34,7 @@ A test case with origin `PENDING-CODE` or `BLOCKED-PERMISSIONS` must be in `test
 ## The Spec-Before-Automation Rule
 
 ```
-Specification exists FIRST → Automation comes second
+Specification exists FIRST -> Automation comes second
 ```
 
 Automation artifacts (spec files, page objects) always reference a spec TC-ID. It is never acceptable to write a Playwright test without a corresponding TC in `05-test-scenarios.md`.
@@ -90,10 +90,10 @@ E2E tests should NOT try to cover:
 
 | Priority | Meaning | Target in automation |
 |---|---|---|
-| **P0** | Critical — system unusable without this | Must be automated |
-| **P1** | High — significant impact if broken | Should be automated |
-| **P2** | Medium — moderate impact | Automate if feasible |
-| **P3** | Low — minor impact | Manual testing acceptable |
+| **P0** | Critical - system unusable without this | Must be automated |
+| **P1** | High - significant impact if broken | Should be automated |
+| **P2** | Medium - moderate impact | Automate if feasible |
+| **P3** | Low - minor impact | Manual testing acceptable |
 
 In the automation suite, P0 tests form the **smoke suite** that runs on every CI build.
 P1 tests run on scheduled runs or before each release.
@@ -165,6 +165,6 @@ This framework supports both:
 | Maintenance after code change | Agent + Human review |
 
 The handoff between agent and human should always happen at a known checkpoint:
-- After the spec set is produced → human reviews before automation is written
-- After automation is written → human reviews coverage mapping
-- After a defect is filed → human decides priority and fix approach
+- After the spec set is produced -> human reviews before automation is written
+- After automation is written -> human reviews coverage mapping
+- After a defect is filed -> human decides priority and fix approach

package/docs/usage-with-agent.md

@@ -1,12 +1,14 @@
 # docs/usage-with-agent.md
 
-## Using `qa-framework` with an IDE Agent (GitHub Copilot)
+## Using `qa-framework` with an IDE Agent (GitHub Copilot or Claude Code)
 
 ---
 
 ## Overview
 
-This framework is designed so that an IDE agent (such as GitHub Copilot in VS Code) can:
+`init` and `upgrade` always generate artifacts for both GitHub Copilot and Claude Code
+in parallel - there is no agent detection. This framework is designed so that either
+IDE agent can:
 
 1. Understand the QA structure by reading the agent instruction files
 2. Navigate the `qa/` directory predictably
@@ -42,11 +44,11 @@ This framework is designed so that an IDE agent (such as GitHub Copilot in VS Co
 
 ---
 
-## Setting Up Agent Instructions in VS Code
+## Setting Up Agent Instructions in VS Code (GitHub Copilot)
 
-### Option A — Workspace instructions file (recommended)
+### Option A - Workspace instructions file (recommended)
 
-`init` generates `.github/copilot-instructions.md` automatically. It contains the full
+`init` generates `.github/instructions/qa-framework.instructions.md` automatically. It contains the full
 pipeline sequencer with 11 agent behavior rules, the QA pipeline table, and ADO detection.
 No manual setup needed.
 
@@ -56,7 +58,7 @@ To regenerate after an upgrade:
 npx qa-framework upgrade
 ```
 
-### Option B — Reference skills directly in the agent conversation
+### Option B - Reference skills directly in the agent conversation
 
 Paste a skill path into the Copilot chat:
 
@@ -64,7 +66,7 @@ Paste a skill path into the Copilot chat:
 Read .github/skills/qa-module-analysis/SKILL.md and analyze the module at {URL}
 ```
 
-### Option C — Individual task prompts
+### Option C - Individual task prompts
 
 For each major QA task, ask the agent to load the relevant skill:
 
@@ -75,6 +77,82 @@ tests for the submodule {name}
 
 ---
 
+## Setting Up Agent Instructions in Claude Code
+
+`init` and `upgrade` generate two Claude-Code-native artifacts automatically, no manual
+setup needed:
+
+- `.claude/rules/qa-framework.md` - the Claude Code equivalent of the Copilot
+  `.instructions.md` file. It has no frontmatter, which means it loads unconditionally in
+  every session (the same effect as `applyTo: '**'`). It contains the same 11 agent
+  behavior rules and pipeline table as the Copilot instructions, with every skill
+  reference expressed as a `/qa-{name}` slash command instead of "load this file".
+- `.claude/commands/qa-{name}.md` - one thin wrapper per skill, generated dynamically
+  from whatever folders exist under `.github/skills/` at install/upgrade time. Each
+  wrapper is a single instruction: `Read the full skill at .github/skills/qa-{name}/SKILL.md
+  FIRST, then follow its instructions exactly`, plus the stage prerequisite. There is zero
+  duplication of skill content and therefore zero drift - if a skill is updated, every
+  command that points to it picks up the change with no regeneration needed.
+
+### Using a command
+
+In a Claude Code session, invoke the pipeline stage directly:
+
+```
+/qa-module-analysis
+```
+
+Claude reads `.github/skills/qa-module-analysis/SKILL.md` and follows it exactly, the
+same way the Copilot pipeline table routes to that file.
+
+### Regenerating after an upgrade
+
+```bash
+npx qa-framework upgrade
+```
+
+This refreshes both `.claude/commands/qa-*.md` and `.claude/rules/qa-framework.md` the
+same safe way it refreshes the Copilot artifacts (framework-owned, always overwritten
+with the current version; nothing else under `.claude/` is touched).
+
+---
+
+## Optional: ANALISIS/PLAN Mode (Claude Code only, ADO-gated)
+
+Some teams run a sprint-centric manual testing workflow in parallel with the 6-stage
+pipeline: an analysis document, a test plan trace-linked to Azure DevOps work items,
+ad-hoc QA advisory chat, and a sprint closing results report. This mode is:
+
+- **Optional** - off by default.
+- **Gated** by `integrations.azureDevOps.sprintCycle.enabled` in
+  `qa/qa-framework.config.json` (it requires Azure DevOps enabled, since most of the
+  agents depend on ADO work items or an ADO-generated execution report).
+- **Claude Code only, by design, not by omission.** Each agent is a Claude Code subagent
+  with its own `tools`/`model` frontmatter (e.g. `qa-asesoria` intentionally has no
+  `Write`/`Bash`). GitHub Copilot has no equivalent primitive, so no `.github/` artifact
+  is generated for this mode.
+
+When enabled, `init`/`upgrade` generate six subagents under `.claude/agents/`:
+
+| Agent | Purpose |
+|---|---|
+| `qa-analisis.md` | Analysis document: test universe, automation feasibility, P0-P3 prioritization, excluded universe, traceability matrix |
+| `qa-plan.md` | Default mode: executive summary + a trace-linked test case table, executable within the configured manual-testing timebox |
+| `qa-asesoria.md` | Chat-only QA advisory (no `Write`/`Bash`) - answers point questions, redirects to `qa-plan`/`qa-analisis` when a full document is actually needed |
+| `qa-reporte-ejecucion.md` | Exports the ADO test plan results, versions the raw export under `ado-export-<YYYY-MM-DD>/` and writes the sprint `Reporte-de-Ejecucion-de-Pruebas-<project>-Sprint-<N>.md` (summary + promoted findings) |
+| `qa-informe-resultados.md` | Narrative sprint closing report built from the Reporte produced by `qa-reporte-ejecucion`; updates incrementally, never overwrites prior sections |
+| `qa-investigador.md` | Investigates one concrete root cause against the real environment and returns a verdict with evidence. Gets Playwright MCP browser tools for every `parallelLanes` lane with an `mcpNamespace`; with no such lane it works without a browser |
+
+Sprint duration, manual-testing timebox, date format, timezone and the approval threshold
+(`approvalThresholdPercent`, default 85) are parameterized from
+`integrations.azureDevOps.sprintCycle` (with neutral defaults - 8-day sprint, 2-day
+timebox, `dd-mm-aaaa`, `America/Santiago` - when a field is omitted). The optional
+`conventions.decimalSeparator` and `conventions.defectIdPrefix` override values otherwise
+derived from the locale and the project name. See [docs/installation.md](installation.md)
+for the config shape.
+
+---
+
 ## Typical Agent Session Workflow
 
 ### Session 1: Initial Module Analysis
@@ -124,7 +202,7 @@ tests for the submodule {name}
 
 ### DO
 
-- Read `qa/AGENT-NEXT-STEPS.md` at the start of each conversation (auto-enforced by copilot-instructions.md)
+- Read `qa/AGENT-NEXT-STEPS.md` at the start of each conversation (auto-enforced by `.github/instructions/qa-framework.instructions.md` for Copilot, or `.claude/rules/qa-framework.md` for Claude Code)
 - Load the relevant skill from `.github/skills/` before starting any QA task
 - Save all artifacts in the exact path specified by `qa/QA-STRUCTURE-GUIDE.md`
 - Use TC-ID, RN-ID, FL-ID naming consistently
@@ -181,7 +259,8 @@ This performs:
 ## Continuing from a Previous Session
 
 The agent reads `qa/AGENT-NEXT-STEPS.md` automatically at the start of every conversation
-(enforced by `.github/copilot-instructions.md` rule 0). For additional context:
+(enforced by rule 0 in `.github/instructions/qa-framework.instructions.md` for Copilot,
+or `.claude/rules/qa-framework.md` for Claude Code). For additional context:
 
 ```
 "Read qa/README.md and qa/memory/INDEX.md, then tell me where we left off."

package/examples/module-example/suppliers/00-inventory.md

@@ -1,4 +1,4 @@
-# Suppliers — Inventory
+# Suppliers - Inventory
 
 **Module**: Suppliers (SUP)
 **Submodule**: Create / Edit / List

package/examples/module-example/suppliers/suppliers-create.spec.ts

@@ -15,16 +15,16 @@
 
 import { test, expect } from '@playwright/test';
 
-// EXEC_IDX: unique per minute-window — prevents data collisions between runs
+// EXEC_IDX: unique per minute-window - prevents data collisions between runs
 const EXEC_IDX = Math.floor(Date.now() / 60_000) % 100_000;
 
 test.describe('Suppliers > Create @P0', () => {
 
   /**
-   * [TC-SUP-CR-001] Create supplier — happy path @P0
+   * [TC-SUP-CR-001] Create supplier - happy path @P0
    * Verifies the complete create flow for a valid supplier.
    */
-  test('[TC-SUP-CR-001] Create supplier — happy path @P0', async ({ page }) => {
+  test('[TC-SUP-CR-001] Create supplier - happy path @P0', async ({ page }) => {
     const supplierName = `QA-Supplier-${EXEC_IDX}`;
     const supplierRut  = `${EXEC_IDX}-K`;
     const supplierEmail = `qa-supplier-${EXEC_IDX}@example.com`;
@@ -57,10 +57,10 @@ test.describe('Suppliers > Create @P0', () => {
   });
 
   /**
-   * [TC-SUP-CR-002] Create supplier — required fields validation @P0
+   * [TC-SUP-CR-002] Create supplier - required fields validation @P0
    * Verifies that the form prevents submission when required fields are empty.
    */
-  test('[TC-SUP-CR-002] Create supplier — required fields validation @P0', async ({ page }) => {
+  test('[TC-SUP-CR-002] Create supplier - required fields validation @P0', async ({ page }) => {
     await page.goto('/suppliers');
     await page.locator('button:has-text("New Supplier")').click();
     await expect(page.locator('.supplier-modal')).toBeVisible();
@@ -79,12 +79,12 @@ test.describe('Suppliers > Create @P0', () => {
   });
 
   /**
-   * [TC-SUP-CR-003] Create supplier — duplicate RUT rejected @P0
+   * [TC-SUP-CR-003] Create supplier - duplicate RUT rejected @P0
    *
-   * NOTE: test.skip active — DEF-001: Duplicate RUT check not enforced server-side.
+   * NOTE: test.skip active - DEF-001: Duplicate RUT check not enforced server-side.
    *       Reactivate when ADO #99001 is resolved.
    */
-  test('[TC-SUP-CR-003] Create supplier — duplicate RUT rejected @P0', async ({ page }) => {
+  test('[TC-SUP-CR-003] Create supplier - duplicate RUT rejected @P0', async ({ page }) => {
     test.skip(true,
       'DEF-001: Duplicate RUT validation not enforced. Reactivate when ADO #99001 is resolved.'
     );

package/integrations/ado-powershell/README.md

@@ -1,4 +1,4 @@
-# Integration — ADO PowerShell Scripts
+# Integration - ADO PowerShell Scripts
 
 PowerShell scripts for Azure DevOps Test Plan management.
 All scripts are parameterized and project-agnostic.

package/integrations/ado-powershell/scripts/sync-ado-titles.ps1

@@ -61,7 +61,7 @@ foreach ($entry in $mapping) {
                 Select-Object -First 1
 
     if (-not $specFile) {
-        Write-Warning "  [NOT FOUND] $($entry.specFile) — skipping WI $adoId"
+        Write-Warning "  [NOT FOUND] $($entry.specFile) - skipping WI $adoId"
         $skipped++
         continue
     }
@@ -84,7 +84,7 @@ foreach ($entry in $mapping) {
 
     if ($PSCmdlet.ShouldProcess("WI #$adoId", "Update title to: $newTitle")) {
         Invoke-RestMethod -Method Patch -Uri $patchUrl -Headers $headers -Body $body | Out-Null
-        Write-Host "  [SYNCED] WI #$adoId → $newTitle"
+        Write-Host "  [SYNCED] WI #$adoId -> $newTitle"
         $synced++
     }
 }

package/integrations/playwright/README.md

@@ -1,4 +1,4 @@
-# Integration — Playwright
+# Integration - Playwright
 
 This directory documents how `@playwright/test` is configured within the
 `keber/qa-framework` opinionated setup.
@@ -40,9 +40,9 @@ suite execution.
 
 ## Debugging checklist
 
-1. `PWDEBUG=1 npx playwright test` — step through in inspector
-2. `--headed` — watch the browser
-3. `--trace on` — record full trace; open with `npx playwright show-trace`
+1. `PWDEBUG=1 npx playwright test` - step through in inspector
+2. `--headed` - watch the browser
+3. `--trace on` - record full trace; open with `npx playwright show-trace`
 4. Increase `actionTimeout` if the app has slow server-side rendering
 5. Add `await page.waitForLoadState('networkidle')` before assertions on
    dynamically loaded content

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@keber/qa-framework",
-  "version": "1.11.3",
+  "version": "1.13.0",
   "description": "Reusable spec-driven QA framework for IDE-agent-assisted automated testing. Installable as an npm package. Provides structure, templates, agent instructions, and optional integrations for Playwright and Azure DevOps.",
   "keywords": [
     "qa",
@@ -21,7 +21,11 @@
     "postinstall": "node scripts/init.js --skip-if-exists",
     "init": "node scripts/cli.js init",
     "generate": "node scripts/cli.js generate",
-    "validate": "node scripts/cli.js validate"
+    "validate": "node scripts/cli.js validate",
+    "check-accents": "node scripts/check-spanish-accents.js",
+    "check-chars": "node scripts/check-forbidden-chars.js",
+    "test": "node --test test/*.test.js",
+    "version": "node scripts/sync-version.js && git add README.md .github/copilot-instructions.md qa-framework.config.json"
   },
   "files": [
     "agent-instructions/",
@@ -36,7 +40,7 @@
     "qa-framework.config.json"
   ],
   "engines": {
-    "node": ">=18"
+    "node": ">=20"
   },
   "peerDependencies": {
     "@keber/ado-qa": ">=1.0.0",

package/qa-framework.config.json

@@ -1,6 +1,6 @@
 {
   "$schema": "./qa-framework.config.schema.json",
-  "frameworkVersion": "1.10.0",
+  "frameworkVersion": "1.13.0",
 
   "project": {
     "name": "{{PROJECT_NAME}}",
@@ -27,7 +27,7 @@
     "testCaseIdPattern": "TC-{MODULE}-{SUBMODULE}-{NUM}",
     "businessRuleIdPattern": "RN-{MODULE}-{NUM}",
     "workflowIdPattern": "FL-{MODULE}-{NUM}",
-    "defectIdPattern": "DEF-{NUM}",
+    "defectIdPattern": "DEF-{PREFIX}-{NUM}",
     "testNamingPattern": "[{ID}] {title} @{priority}",
     "timestampFormat": "YYYY-MM-DD_HH-MM-SS",
     "tcPriorityLevels": ["P0", "P1", "P2", "P3"]
@@ -42,6 +42,20 @@
     }
   ],
 
+  "parallelLanes": {
+    "enabled": false,
+    "lanes": [
+      {
+        "id": "1",
+        "account": "QA_USER",
+        "storageState": ".auth/user-default.json",
+        "mcpNamespace": null,
+        "runnerProject": "chromium",
+        "capabilities": []
+      }
+    ]
+  },
+
   "integrations": {
     "playwright": {
       "enabled": false,
@@ -69,7 +83,15 @@
       "variableGroup": "{{ADO_VARIABLE_GROUP}}",
       "pipelineFile": "qa/08-azure-integration/pipelines/azure-pipeline-qa.yml",
       "moduleRegistry": "qa/08-azure-integration/module-registry.json",
-      "reporterPackage": "@alex_neo/playwright-azure-reporter"
+      "reporterPackage": "@alex_neo/playwright-azure-reporter",
+      "sprintCycle": {
+        "enabled": false,
+        "sprintDurationDays": 8,
+        "manualTestingTimeboxDays": 2,
+        "dateFormat": "dd-mm-aaaa",
+        "timezone": "America/Santiago",
+        "approvalThresholdPercent": 85
+      }
     }
   },