context-first-cli 2.2.0 → 2.2.1

package/dist/templates/commands/es/quality/metrics.md

@@ -9,11 +9,49 @@ Medir y documentar la calidad de la implementación mediante métricas objetivas
 - Complejidad del código
 - Deuda técnica
 - Rendimiento
-- Cumplimiento con estándares
+- Conformidad con estándares
 
-## 📋 Requisitos previos
+## 📋 Configuración del Proyecto
 
-- Implementación finalizada (después de `/work`)
+**⚠️ IMPORTANTE: ¡Siempre lea los archivos de configuración del proyecto ANTES de ejecutar este comando!**
+
+### Archivos Obligatorios
+
+1. **`context-manifest.json`** (raíz del orquestador)
+   - Lista de repositorios del proyecto
+   - Roles de cada repositorio (metaspecs, application, etc.)
+   - URLs y dependencias entre repositorios
+
+2. **`ai.properties.md`** (raíz del orquestador)
+   - Configuraciones del proyecto (`project_name`, `base_path`)
+   - Sistema de gestión de tareas (`task_management_system`)
+   - Credenciales y configuraciones específicas
+
+### Cómo Leer
+
+```bash
+# 1. Leer context-manifest.json
+cat context-manifest.json
+
+# 2. Leer ai.properties.md
+cat ai.properties.md
+```
+
+### Información Esencial
+
+Después de leer los archivos, tendrás:
+- ✅ Lista completa de repositorios del proyecto
+- ✅ Ubicación del repositorio de metaspecs
+- ✅ Base path para localizar repositorios
+- ✅ Sistema de gestión de tareas configurado
+- ✅ Configuraciones específicas del proyecto
+
+**🛑 NO continúe sin leer estos archivos!** Contienen información crítica para la correcta ejecución del comando.
+
+
+## 📋 Requisitos Previos
+
+- Implementación completada (después de `/work`)
 - Pruebas implementadas
 - Build funcionando
 
@@ -142,7 +180,7 @@ Si aplica, mida rendimiento:
 ## Tamaño e Impacto
 
 ### Líneas de Código
-- **Añadidas**: +X líneas
+- **Agregadas**: +X líneas
 - **Eliminadas**: -Y líneas
 - **Modificadas**: Z líneas
 
@@ -254,7 +292,7 @@ Si alguna métrica está fuera de lo aceptable:
 
 ## 🎯 Resultado
 
-Tras ejecutar este comando, tendrá:
+Después de ejecutar este comando, tendrás:
 - Informe completo de métricas
 - Comparación con baseline y metas
 - Identificación de problemas de calidad

package/dist/templates/commands/es/quality/observe.md

@@ -12,7 +12,44 @@ Crear un registro estructurado de decisiones técnicas y de producto, garantizan
 
 **IMPORTANTE**: Este comando NO genera decisiones nuevas. Solo REGISTRA decisiones que ya fueron tomadas en el proceso de desarrollo.
 
-## 📋 Requisitos previos
+## 📋 Configuración del Proyecto
+
+**⚠️ IMPORTANTE: ¡Siempre lea los archivos de configuración del proyecto ANTES de ejecutar este comando!**
+
+### Archivos Obligatorios
+
+1. **`context-manifest.json`** (raíz del orchestrator)
+   - Lista de repositorios del proyecto
+   - Roles de cada repositorio (metaspecs, application, etc.)
+   - URLs y dependencias entre repositorios
+
+2. **`ai.properties.md`** (raíz del orchestrator)
+   - Configuraciones del proyecto (`project_name`, `base_path`)
+   - Sistema de gestión de tareas (`task_management_system`)
+   - Credenciales y configuraciones específicas
+
+### Cómo Leer
+
+```bash
+# 1. Leer context-manifest.json
+cat context-manifest.json
+
+# 2. Leer ai.properties.md
+cat ai.properties.md
+```
+
+### Información Esencial
+
+Después de leer los archivos, tendrás:
+- ✅ Lista completa de repositorios del proyecto
+- ✅ Ubicación del repositorio de metaspecs
+- ✅ Base path para localizar repositorios
+- ✅ Sistema de gestión de tareas configurado
+- ✅ Configuraciones específicas del proyecto
+
+**🛑 NO continúe sin leer estos archivos!** Contienen información crítica para la correcta ejecución del comando.
+
+## 📋 Pre-requisitos
 
 - Haber ejecutado al menos uno de los comandos que generan decisiones:
   - `/spec` - genera PRD con decisiones de producto
@@ -28,7 +65,7 @@ Analice los archivos de la sesión (`./.sessions/<ISSUE-ID>/`) para identificar
 **Después de `/spec`** - Decisiones de Producto:
 - Lea `./.sessions/<ISSUE-ID>/prd.md`
 - Identifique decisiones en:
-  - Alcance (qué entra/no entra en la feature)
+  - Alcance (qué entra/no entra en la funcionalidad)
   - Personas atendidas (quién es el público objetivo)
   - Métricas de éxito (cómo medir resultados)
   - Requisitos no funcionales (performance, accesibilidad)
@@ -41,7 +78,7 @@ Analice los archivos de la sesión (`./.sessions/<ISSUE-ID>/`) para identificar
   - Elección de bibliotecas o herramientas
   - Patrones de implementación
   - Estructura de datos
-  - Estrategia de tests
+  - Estrategia de pruebas
 
 **Durante `/work`** - Decisiones de Implementación:
 - Lea `./.sessions/<ISSUE-ID>/work.md`
@@ -92,7 +129,7 @@ Guarde en `./.sessions/<ISSUE-ID>/decisions.md`:
 # Registro de Decisiones - [ISSUE-ID]
 
 ## Resumen
-[Breve resumen de las principales decisiones tomadas en esta feature]
+[Breve resumen de las principales decisiones tomadas en esta funcionalidad]
 
 ## Decisiones de Producto
 
@@ -161,7 +198,7 @@ Periódicamente, revise las decisiones tomadas:
 
 ## 🎯 Resultado
 
-Después de ejecutar este comando, tendrá:
+Después de ejecutar este comando, tendrás:
 - Registro completo de decisiones en `./.sessions/<ISSUE-ID>/decisions.md`
 - Trazabilidad de cada elección realizada
 - Documentación para futuras referencias

package/dist/templates/commands/es/warm-up.md

@@ -14,6 +14,44 @@ pwd
 
 Si no está en un workspace, pregunte al usuario qué workspace usar o si debe crear uno nuevo con `feature:start`.
 
+## 📋 Configuración del Proyecto
+
+**⚠️ IMPORTANTE: ¡Siempre lea los archivos de configuración del proyecto ANTES de ejecutar este comando!**
+
+### Archivos Obligatorios
+
+1. **`context-manifest.json`** (raíz del orchestrator)
+   - Lista de repositorios del proyecto
+   - Roles de cada repositorio (metaspecs, application, etc.)
+   - URLs y dependencias entre repositorios
+
+2. **`ai.properties.md`** (raíz del orchestrator)
+   - Configuraciones del proyecto (`project_name`, `base_path`)
+   - Sistema de gestión de tareas (`task_management_system`)
+   - Credenciales y configuraciones específicas
+
+### Cómo Leer
+
+```bash
+# 1. Leer context-manifest.json
+cat context-manifest.json
+
+# 2. Leer ai.properties.md
+cat ai.properties.md
+```
+
+### Información Esencial
+
+Después de leer los archivos, tendrá:
+- ✅ Lista completa de repositorios del proyecto
+- ✅ Ubicación del repositorio de metaspecs
+- ✅ Base path para localizar repositorios
+- ✅ Sistema de gestión de tareas configurado
+- ✅ Configuraciones específicas del proyecto
+
+**🛑 NO continúe sin leer estos archivos!** Contienen información crítica para la correcta ejecución del comando.
+
+
 ## 2. Cargar Configuración del Proyecto
 
 Ya está en el orchestrator del proyecto (raíz del repositorio actual).
@@ -32,7 +70,7 @@ Lea el `context-manifest.json` del orchestrator para entender:
 
 ## 4. Cargar MetaSpecs
 
-El repositorio de MetaSpecs es **separado** y está definido en `context-manifest.json` con `role: "metaspecs"`.
+El repositorio de MetaSpecs es **separado** y está definido en el `context-manifest.json` con `role: "metaspecs"`.
 
 **Localice el repositorio de metaspecs:**
 
@@ -46,14 +84,14 @@ El repositorio de MetaSpecs es **separado** y está definido en `context-manifes
 1. **`README.md`** - Visión general del proyecto y estructura de documentación
 2. **`index.md`** (en la raíz o en subcarpetas) - Índice de especificaciones disponibles
 
-**Use los índices como referencia** para navegar hasta las especificaciones específicas que necesita. No asuma que archivos específicos existen - siempre consulte los índices primero.
+**Use los índices como referencia** para navegar hasta las especificaciones específicas que necesite. No asuma que archivos específicos existen - siempre consulte los índices primero.
 
 ## 5. Cargar Sesión Actual (si existe)
 
 Verifique si existe una sesión guardada para este workspace:
 
 ```bash
-# Buscar sesión en orchestrator
+# Buscar sesión en el orchestrator
 ls -la .sessions/<ISSUE-ID>/ 2>/dev/null
 ```
 
@@ -68,18 +106,18 @@ Para cada repositorio presente en el workspace, lea:
 ## 7. Navegación Inteligente
 
 - **Código**: Use herramientas de búsqueda (glob, grep) para localizar archivos relevantes
-- **Documentación**: Use los índices de MetaSpecs como referencia
+- **Documentación**: Use los índices de los MetaSpecs como referencia
 - **Espere Instrucciones**: NO lea otros archivos ahora. Espere el próximo comando.
 
 ## 8. Principio Jidoka (Parar al Detectar Problemas)
 
-Si detecta desalineamiento, conflictos o problemas:
+Si detecta desalineamientos, conflictos o problemas:
 1. 🛑 **PARE** inmediatamente
 2. 📝 **DOCUMENTE** el problema encontrado
-3. 💬 **ALERTE** al usuario antes de proceder
+3. 💬 **ALERTE** al usuario antes de continuar
 
 ---
 
 **Argumentos proporcionados**: #$ARGUMENTS
 
-**Estado**: Contexto cargado. Esperando próximo comando.
+**Estado**: Contexto cargado. Esperando próximo comando.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "context-first-cli",
-  "version": "2.2.0",
+  "version": "2.2.1",
   "description": "A generic CLI to manage the Context-First development methodology across any project.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/templates/commands/en/products/refine.md

@@ -1,6 +1,6 @@
 # Requirements Refinement
 
-You are a product expert tasked with helping to refine requirements for the project.
+You are a product expert responsible for helping to refine requirements for the project.
 
 ## ⚠️ IMPORTANT: This Command DOES NOT Implement Code
 
@@ -17,6 +17,44 @@ You are a product expert tasked with helping to refine requirements for the proj
 
 ---
 
+## 📋 Project Setup
+
+**⚠️ IMPORTANT: Always read the project configuration files BEFORE running this command!**
+
+### Mandatory Files
+
+1. **`context-manifest.json`** (orchestrator root)
+   - List of project repositories
+   - Roles of each repository (metaspecs, application, etc.)
+   - URLs and dependencies between repositories
+
+2. **`ai.properties.md`** (orchestrator root)
+   - Project settings (`project_name`, `base_path`)
+   - Task management system (`task_management_system`)
+   - Credentials and specific configurations
+
+### How to Read
+
+```bash
+# 1. Read context-manifest.json
+cat context-manifest.json
+
+# 2. Read ai.properties.md
+cat ai.properties.md
+```
+
+### Essential Information
+
+After reading the files, you will have:
+- ✅ Complete list of project repositories
+- ✅ Location of the metaspecs repository
+- ✅ Base path to locate repositories
+- ✅ Configured task management system
+- ✅ Project-specific configurations
+
+**🛑 DO NOT proceed without reading these files!** They contain critical information for correct command execution.
+
+
 ## Objective
 
 Transform an initial requirement into a refined and validated specification, ready to become a complete PRD.
@@ -26,7 +64,7 @@ Transform an initial requirement into a refined and validated specification, rea
 ### 1. Clarification Phase
 
 Read the initial requirement and ask questions to achieve full clarity about:
-- **Objective**: Why build this?
+- **Goal**: Why build this?
 - **Business Value**: Which metric/persona does it impact?
 - **Scope**: What is included and what is NOT included?
 - **Interactions**: Which existing features/components are affected?
@@ -35,7 +73,7 @@ Keep asking questions until you have complete understanding.
 
 ### 2. Validation Against Metaspecs
 
-**IMPORTANT**: First read `ai.properties.md` to obtain the `base_path`. The indexes should ALREADY be in context (you ran `/warm-up`). Consult the indexes and read ONLY the relevant documents to validate the requirement.
+**IMPORTANT**: First read `ai.properties.md` to get the `base_path`. The indexes should ALREADY be in context (you ran `/warm-up`). Consult the indexes and read ONLY relevant documents to validate the requirement.
 
 **Validation Process**:
 
@@ -61,50 +99,50 @@ Keep asking questions until you have complete understanding.
    - ✅ Follows existing business rules
    - ⚠️ Identify conflicts or violations
 
-**If you identify violations**: 🛑 **STOP** and ask the user for clarification before proceeding (Jidoka Principle).
+**If violations are identified**: 🛑 **STOP** and ask the user for clarification before proceeding (Jidoka Principle).
 
 ### 3. Summary and Approval Phase
 
 Once you have gathered sufficient information and validated against metaspecs, present a structured summary with:
 - **Feature**: Feature name
-- **Objective**: Why build it (1-2 sentences)
+- **Goal**: Why build it (1-2 sentences)
 - **Business Value**: Metric, persona, roadmap phase (consult metaspecs)
-- **Scope**: What it INCLUDES and what it DOES NOT INCLUDE
+- **Scope**: What IS included and what IS NOT included
 - **Affected Components**: List based on current architecture (consult technical metaspecs)
 - **Validation against Metaspecs**: ✅ Approved / ⚠️ Attention needed
 - **Effort Estimate**: Small (< 1 day) / Medium (1-3 days) / Large (3-5 days) / Very Large (> 5 days)
 
-**Complexity Assessment and Suggestion to Break Down**:
+**Complexity Assessment and Suggestion to Split**:
 
-**If the implementation seems large** (> 5 days estimated effort):
-- 🚨 **Suggest breaking into multiple smaller issues**
-- Explain the rationale for the breakdown (e.g., "This feature involves 3 distinct areas that can be implemented independently")
-- Propose a **logical** breakdown based on:
+**If implementation seems large** (> 5 days estimated effort):
+- 🚨 **Suggest splitting into multiple smaller issues**
+- Explain the rationale for splitting (e.g., "This feature involves 3 distinct areas that can be implemented independently")
+- Propose a **logical** split based on:
   - Independent functionalities
   - Different repositories
   - Application layers (backend, frontend, infra)
   - Implementation phases (MVP, improvements, optimizations)
-- Example breakdown:
+- Example split:
   ```
   Original Issue: "Multi-channel notification system"
   
-  Suggested Breakdown:
+  Suggested Split:
   - FIN-201: Queue and worker infrastructure (backend)
   - FIN-202: Email notifications (backend + templates)
   - FIN-203: Push notifications (backend + mobile)
   - FIN-204: Notification preferences (frontend + backend)
   ```
-- **Important**: The final decision is the user's - they may accept the breakdown or keep it as a single issue
+- **Important**: Final decision is the user's - they may accept the split or keep it as a single issue
 
-**If the user accepts the breakdown**:
+**If the user accepts the split**:
 - Document each issue separately
 - Add cross-references between related issues
 - Suggest implementation order if dependencies exist
-- Each broken-down issue must go through the same refinement process
+- Each split issue must go through the same refinement process
 
-Request user approval and incorporate feedback if necessary.
+Request user approval and incorporate feedback if needed.
 
-**Tip**: You may search the codebase or internet before finalizing, if needed.
+**Tip**: You may search the codebase or internet before finalizing, if necessary.
 
 ### 4. Saving the Refined Requirements
 
@@ -131,23 +169,23 @@ Once the user approves, save the requirements:
    - **ALWAYS overwrite** the existing body (do not append)
 
 **Note**:
-- The local backup is ALWAYS saved and complete
+- Local backup is ALWAYS saved and complete
 - If API error occurs, manually verify if the issue was updated in the task manager
 
 **Output Template**:
 
-**IMPORTANT**: The standard template for refined requirements may be documented in the metaspecs repository. Check `{base_path}/{metaspecs-id}/specs/refined/` or similar.
+**IMPORTANT**: The standard template for refined requirements may be documented in the metaspecs repository. Consult `{base_path}/{metaspecs-id}/specs/refined/` or similar.
 
 **FULL Template** (for local backup `.sessions/<ISSUE-ID>/refined.md`):
 - **Metadata**: Issue, ID, Task Manager, Project, Date, Sprint, Priority
 - **🎯 WHY**: Reasons, business value, metric, persona, strategic alignment
 - **📦 WHAT**: Detailed features, affected components, integrations, full negative scope
-- **🔧 HOW**: Stack, coding standards, file structure, dependencies, implementation order, failure modes, performance/cost/UX considerations
+- **🔧 HOW**: Stack, coding patterns, file structure, dependencies, implementation order, failure modes, performance/cost/UX considerations
 - **✅ Validation against Metaspecs**: Consulted documents (business and technical), verified ADRs, validation result
 - **📊 Success Metrics**: Technical, product/UX, acceptance criteria
 - **🔄 Product Impact**: Alignment with objectives, enablers, mitigated risks
 - **⚠️ Known Limitations**: MVP limitations
-- **📝 Implementation Checklist**: Tasks by area (backend, frontend, testing, security, etc.)
+- **📝 Implementation Checklist**: Tasks by area (backend, frontend, tests, security, etc.)
 
 **Task Manager Template**:
 ```markdown
@@ -155,7 +193,7 @@ Once the user approves, save the requirements:
 
 **Sprint X** | **Y days** | **Priority**
 
-## Objective
+## Goal
 [1-2 paragraphs: what it is and why]
 
 ## Scope
@@ -176,12 +214,12 @@ Once the user approves, save the requirements:
 ❌ [item 1] ❌ [item 2] ❌ [item 3]
 
 ## Stack
-[Tech stack summary by area]
+[Tech stack summarized by area]
 
 ## Structure
 [SUMMARIZED file tree - main modules only]
 
-## Failure Modes (To Avoid)
+## Failure Modes (Avoid)
 🔴 [critical 1] 🔴 [critical 2]
 🟡 [medium 1] 🟡 [medium 2]
 
@@ -224,4 +262,4 @@ Once the user approves, save the requirements:
 
 **Example**: `/spec FIN-3`
 
-This command will create a complete PRD (Product Requirements Document) based on the refined requirements, detailing features, user stories, acceptance criteria, and final validations.
+This command will create a PRD (Product Requirements Document) complete based on the refined requirements, detailing features, user stories, acceptance criteria, and final validations.

package/templates/commands/en/products/spec.md

@@ -6,17 +6,54 @@ This command creates the complete specification (Product Requirements Document)
 
 **This command is ONLY for requirements documentation:**
 - ✅ Create PRD (Product Requirements Document)
-- ✅ Update issue in task manager via MCP
+- ✅ Update issue in the task manager via MCP
 - ✅ **READ** files from main repositories (read-only)
 - ❌ **DO NOT implement code**
 - ❌ **DO NOT edit code files**
 - ❌ **DO NOT checkout branches in main repositories**
-- ❌ **DO NOT commit**
+- ❌ **DO NOT make commits**
 
 **Next step**: `/start` to begin development.
 
 ---
 
+## 📋 Project Configuration
+
+**⚠️ IMPORTANT: Always read the project configuration files BEFORE running this command!**
+
+### Mandatory Files
+
+1. **`context-manifest.json`** (orchestrator root)
+   - List of project repositories
+   - Roles of each repository (metaspecs, application, etc.)
+   - URLs and dependencies between repositories
+
+2. **`ai.properties.md`** (orchestrator root)
+   - Project settings (`project_name`, `base_path`)
+   - Task management system (`task_management_system`)
+   - Credentials and specific configurations
+
+### How to Read
+
+```bash
+# 1. Read context-manifest.json
+cat context-manifest.json
+
+# 2. Read ai.properties.md
+cat ai.properties.md
+```
+
+### Essential Information
+
+After reading the files, you will have:
+- ✅ Complete list of project repositories
+- ✅ Location of the metaspecs repository
+- ✅ Base path to locate repositories
+- ✅ Configured task management system
+- ✅ Project-specific configurations
+
+**🛑 DO NOT proceed without reading these files!** They contain critical information for correct command execution.
+
 ## 📋 Prerequisites
 
 - Issue refined via `/refine`
@@ -29,7 +66,7 @@ This command creates the complete specification (Product Requirements Document)
 2. Find the repository with `"role": "metaspecs"`
 3. Read `ai.properties.md` to get the `base_path`
 4. The metaspecs are located at: `{base_path}/{metaspecs-repo-id}/`
-5. Read the relevant `index.md` files to ensure compliance with:
+5. Read relevant `index.md` files to ensure compliance with:
    - System architecture
    - Design patterns
    - Technical constraints
@@ -133,7 +170,7 @@ Create a complete PRD that will serve as the single source of truth for implemen
 - **External**: [external APIs, if any]
 
 ### Data Model
-[Describe changes to the data model, if any]
+[Describe changes to data model, if any]
 ```
 
 ### 6. Acceptance Criteria
@@ -162,7 +199,7 @@ Create a complete PRD that will serve as the single source of truth for implemen
 ```markdown
 ## Out of Scope
 
-Features that WILL NOT be implemented in this version:
+Features that will NOT be implemented in this version:
 - [Item 1]
 - [Item 2]
 

package/templates/commands/en/quality/metrics.md

@@ -11,6 +11,43 @@ Measure and document the quality of the implementation through objective metrics
 - Performance
 - Compliance with standards
 
+## 📋 Project Configuration
+
+**⚠️ IMPORTANT: Always read the project configuration files BEFORE running this command!**
+
+### Required Files
+
+1. **`context-manifest.json`** (orchestrator root)
+   - List of project repositories
+   - Roles of each repository (metaspecs, application, etc.)
+   - URLs and dependencies between repositories
+
+2. **`ai.properties.md`** (orchestrator root)
+   - Project settings (`project_name`, `base_path`)
+   - Task management system (`task_management_system`)
+   - Credentials and specific configurations
+
+### How to Read
+
+```bash
+# 1. Read context-manifest.json
+cat context-manifest.json
+
+# 2. Read ai.properties.md
+cat ai.properties.md
+```
+
+### Essential Information
+
+After reading the files, you will have:
+- ✅ Complete list of project repositories
+- ✅ Location of the metaspecs repository
+- ✅ Base path to locate repositories
+- ✅ Configured task management system
+- ✅ Project-specific configurations
+
+**🛑 DO NOT proceed without reading these files!** They contain critical information for the correct execution of the command.
+
 ## 📋 Prerequisites
 
 - Implementation completed (after `/work`)
@@ -57,14 +94,14 @@ Document:
 
 ### 2. Code Complexity
 
-Analyze the cyclomatic complexity of the modified files:
+Analyze the cyclomatic complexity of modified files:
 
 ```markdown
 ## Code Complexity
 
 ### Files with High Complexity
-- **arquivo1.ts**: Complexity 15 (recommended: < 10)
-- **arquivo2.ts**: Complexity 12
+- **file1.ts**: Complexity 15 (recommended: < 10)
+- **file2.ts**: Complexity 12
 
 ### Recommendations
 - [Refactoring suggestion 1]
@@ -163,12 +200,12 @@ Identify technical debt introduced or resolved:
 ```markdown
 ## Technical Debt
 
-### Introduced Debt
+### Debt Introduced
 - **Item 1**: [Description and justification]
   - Severity: High / Medium / Low
   - Resolution plan: [when and how to resolve]
 
-### Resolved Debt
+### Debt Resolved
 - **Item 1**: [What was resolved]
   - Impact: [improvement achieved]
 ```
@@ -185,7 +222,7 @@ Create `./.sessions/<ISSUE-ID>/metrics.md`:
 
 ## Executive Summary
 
-- **Test Coverage**: X% (target: Y%)
+- **Test Coverage**: X% (goal: Y%)
 - **Code Quality**: ✅ / ⚠️ / ❌
 - **Performance**: ✅ / ⚠️ / ❌
 - **Technical Debt**: Low / Medium / High
@@ -210,7 +247,7 @@ Create `./.sessions/<ISSUE-ID>/metrics.md`:
 
 ## Approval for Merge
 
-- [ ] Test coverage >= target
+- [ ] Test coverage >= goal
 - [ ] No critical quality issues
 - [ ] Performance within requirements
 - [ ] Technical debt documented and approved
@@ -229,18 +266,18 @@ If the project has goals defined in metaspecs, validate:
 - **Performance**: < 100ms
 
 ### Status
-- Coverage: ✅ 85% (target: 80%)
-- Complexity: ⚠️ 12 (target: 10) - Justified
-- Performance: ✅ 85ms (target: 100ms)
+- Coverage: ✅ 85% (goal: 80%)
+- Complexity: ⚠️ 12 (goal: 10) - Justified
+- Performance: ✅ 85ms (goal: 100ms)
 ```
 
 ## 🚨 Alerts
 
 If any metric is out of acceptable range:
-1. 🛑 **DOCUMENT** the problem
+1. 🛑 **DOCUMENT** the issue
 2. 💬 **ALERT** the user
 3. 🔧 **PROPOSE** corrective actions
-4. ⏸️ **CONSIDER** blocking the merge until resolved
+4. ⏸️ **CONSIDER** blocking the merge until resolution
 
 ---
 
@@ -252,11 +289,11 @@ If any metric is out of acceptable range:
 
 ---
 
-## 🎯 Result
+## 🎯 Outcome
 
 After running this command, you will have:
 - Complete metrics report
 - Comparison with baseline and goals
 - Identification of quality issues
-- Recommended actions
+- Recommendations for actions
 - Objective basis for merge approval