context-first-cli 2.0.0 → 2.0.2

package/dist/templates/commands/en/engineer/pre-pr.md

@@ -30,19 +30,36 @@ Ensure that the implementation is complete, tested, and ready for review before
 For each modified repository:
 
 ```bash
-cd <repositório>
+cd <repository>
 
 # Check status
 git status
 
-# Check linting
-npm run lint  # or equivalent command
-
-# Check formatting
-npm run format:check  # or equivalent command
-
-# Check build
-npm run build  # or equivalent command
+# Check linting (examples by stack):
+# Node.js: npm run lint / yarn lint / pnpm lint
+# Python: flake8 . / pylint src/ / black --check .
+# Java: mvn checkstyle:check / gradle check
+# Go: golangci-lint run / go vet ./...
+# Ruby: rubocop
+# Rust: cargo clippy
+# PHP: ./vendor/bin/phpcs
+# C#: dotnet format --verify-no-changes
+
+# Check formatting (examples by stack):
+# Node.js: npm run format:check / prettier --check .
+# Python: black --check . / autopep8 --diff .
+# Java: mvn formatter:validate
+# Go: gofmt -l . / go fmt ./...
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Check build (examples by stack):
+# Node.js: npm run build / yarn build
+# Python: python setup.py build
+# Java: mvn compile / gradle build
+# Go: go build ./...
+# Ruby: rake build
+# Rust: cargo build
 ```
 
 Checklist:
@@ -67,16 +84,35 @@ Checklist:
 For each repository:
 
 ```bash
-cd <repositório>
-
-# Run unit tests
-npm run test:unit  # or equivalent command
-
-# Run integration tests
-npm run test:integration  # or equivalent command
-
-# Check coverage
-npm run test:coverage  # or equivalent command
+cd <repository>
+
+# Run unit tests (examples by stack):
+# Node.js: npm run test:unit / jest / vitest
+# Python: pytest tests/unit / python -m unittest
+# Java: mvn test / gradle test
+# Go: go test ./... -short
+# Ruby: rspec spec/unit / rake test:unit
+# Rust: cargo test --lib
+# PHP: ./vendor/bin/phpunit --testsuite=unit
+# C#: dotnet test --filter Category=Unit
+
+# Run integration tests (examples by stack):
+# Node.js: npm run test:integration
+# Python: pytest tests/integration
+# Java: mvn verify / gradle integrationTest
+# Go: go test ./... -run Integration
+# Ruby: rspec spec/integration
+# Rust: cargo test --test '*'
+# PHP: ./vendor/bin/phpunit --testsuite=integration
+
+# Check coverage (examples by stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
 ```
 
 Checklist:

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

@@ -24,10 +24,17 @@ Measure and document the quality of the implementation through objective metrics
 For each modified repository:
 
 ```bash
-cd <repositório>
-
-# Run tests with coverage
-npm run test:coverage  # or equivalent command
+cd <repository>
+
+# Run tests with coverage (examples by stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
+# C#: dotnet test /p:CollectCoverage=true
 
 # Capture results
 ```
@@ -67,14 +74,29 @@ Analyze the cyclomatic complexity of the modified files:
 ### 3. Code Quality
 
 ```bash
-# Run linting
-npm run lint
-
-# Check formatting
-npm run format:check
-
-# Static analysis (if available)
-npm run analyze
+# Run linting (examples by stack):
+# Node.js: npm run lint / eslint .
+# Python: flake8 . / pylint src/
+# Java: mvn checkstyle:check
+# Go: golangci-lint run
+# Ruby: rubocop
+# Rust: cargo clippy
+
+# Check formatting (examples by stack):
+# Node.js: prettier --check .
+# Python: black --check .
+# Java: mvn formatter:validate
+# Go: gofmt -l .
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Static analysis (examples by stack):
+# Node.js: npm run analyze (if configured)
+# Python: mypy src/ / bandit -r src/
+# Java: mvn pmd:check / spotbugs:check
+# Go: go vet ./...
+# Ruby: brakeman (for Rails)
+# Rust: cargo audit
 ```
 
 Document:

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

@@ -16,11 +16,11 @@ If you're not in a workspace, ask the user which workspace to use or if you shou
 
 ## 2. Load Project Configuration
 
-Identify the project's orchestrator:
+You are already in the project's orchestrator (current repository root).
 
-1. **Look for the `.contextrc.json` file** in any of the workspace repositories
-2. This file contains the orchestrator repository URL
-3. If the orchestrator is not cloned locally yet, clone it
+1. **Verify you're at the orchestrator root**: `pwd` should show the orchestrator directory
+2. **Read the `context-manifest.json` file** at the orchestrator root
+3. **Read the `ai.properties.md` file** to get local configurations (base_path, etc.)
 
 ## 3. Load Project Manifest
 
@@ -32,7 +32,14 @@ Read the `context-manifest.json` from the orchestrator to understand:
 
 ## 4. Load MetaSpecs
 
-The MetaSpecs repository is defined in `context-manifest.json` (usually with `role: "specs-provider"`).
+The MetaSpecs repository is **separate** and defined in `context-manifest.json` with `role: "metaspecs"`.
+
+**Locate the metaspecs repository:**
+
+1. Read `context-manifest.json` and find the repository with `role: "metaspecs"`
+2. Get the `id` of that repository (e.g., "my-project-metaspecs")
+3. Read `ai.properties.md` to get the `base_path`
+4. The metaspecs repository is at: `{base_path}/{metaspecs-id}/`
 
 **Always read the index files first:**
 

package/dist/templates/commands/es/engineer/pre-pr.md

@@ -30,19 +30,36 @@ Garantizar que la implementación está completa, probada y lista para revisión
 Para cada repositorio modificado:
 
 ```bash
-cd <repositório>
+cd <repositorio>
 
 # Verificar estado
 git status
 
-# Verificar linting
-npm run lint  # o comando equivalente
-
-# Verificar formateo
-npm run format:check  # o comando equivalente
-
-# Verificar build
-npm run build  # o comando equivalente
+# Verificar linting (ejemplos por stack):
+# Node.js: npm run lint / yarn lint / pnpm lint
+# Python: flake8 . / pylint src/ / black --check .
+# Java: mvn checkstyle:check / gradle check
+# Go: golangci-lint run / go vet ./...
+# Ruby: rubocop
+# Rust: cargo clippy
+# PHP: ./vendor/bin/phpcs
+# C#: dotnet format --verify-no-changes
+
+# Verificar formateo (ejemplos por stack):
+# Node.js: npm run format:check / prettier --check .
+# Python: black --check . / autopep8 --diff .
+# Java: mvn formatter:validate
+# Go: gofmt -l . / go fmt ./...
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Verificar build (ejemplos por stack):
+# Node.js: npm run build / yarn build
+# Python: python setup.py build
+# Java: mvn compile / gradle build
+# Go: go build ./...
+# Ruby: rake build
+# Rust: cargo build
 ```
 
 Checklist:
@@ -67,16 +84,35 @@ Checklist:
 Para cada repositorio:
 
 ```bash
-cd <repositório>
-
-# Ejecutar pruebas unitarias
-npm run test:unit  # o comando equivalente
-
-# Ejecutar pruebas de integración
-npm run test:integration  # o comando equivalente
-
-# Verificar cobertura
-npm run test:coverage  # o comando equivalente
+cd <repositorio>
+
+# Ejecutar pruebas unitarias (ejemplos por stack):
+# Node.js: npm run test:unit / jest / vitest
+# Python: pytest tests/unit / python -m unittest
+# Java: mvn test / gradle test
+# Go: go test ./... -short
+# Ruby: rspec spec/unit / rake test:unit
+# Rust: cargo test --lib
+# PHP: ./vendor/bin/phpunit --testsuite=unit
+# C#: dotnet test --filter Category=Unit
+
+# Ejecutar pruebas de integración (ejemplos por stack):
+# Node.js: npm run test:integration
+# Python: pytest tests/integration
+# Java: mvn verify / gradle integrationTest
+# Go: go test ./... -run Integration
+# Ruby: rspec spec/integration
+# Rust: cargo test --test '*'
+# PHP: ./vendor/bin/phpunit --testsuite=integration
+
+# Verificar cobertura (ejemplos por stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
 ```
 
 Checklist:

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

@@ -24,10 +24,17 @@ Medir y documentar la calidad de la implementación mediante métricas objetivas
 Para cada repositorio modificado:
 
 ```bash
-cd <repositório>
-
-# Ejecutar pruebas con cobertura
-npm run test:coverage  # ou comando equivalente
+cd <repositorio>
+
+# Ejecutar pruebas con cobertura (ejemplos por stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
+# C#: dotnet test /p:CollectCoverage=true
 
 # Capturar resultados
 ```
@@ -67,14 +74,29 @@ Analice la complejidad ciclomática de los archivos modificados:
 ### 3. Calidad del Código
 
 ```bash
-# Ejecutar linting
-npm run lint
-
-# Verificar formato
-npm run format:check
-
-# Análisis estático (si está disponible)
-npm run analyze
+# Ejecutar linting (ejemplos por stack):
+# Node.js: npm run lint / eslint .
+# Python: flake8 . / pylint src/
+# Java: mvn checkstyle:check
+# Go: golangci-lint run
+# Ruby: rubocop
+# Rust: cargo clippy
+
+# Verificar formato (ejemplos por stack):
+# Node.js: prettier --check .
+# Python: black --check .
+# Java: mvn formatter:validate
+# Go: gofmt -l .
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Análisis estático (ejemplos por stack):
+# Node.js: npm run analyze (si está configurado)
+# Python: mypy src/ / bandit -r src/
+# Java: mvn pmd:check / spotbugs:check
+# Go: go vet ./...
+# Ruby: brakeman (para Rails)
+# Rust: cargo audit
 ```
 
 Documente:

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

@@ -16,11 +16,11 @@ Si no está en un workspace, pregunte al usuario qué workspace usar o si debe c
 
 ## 2. Cargar Configuración del Proyecto
 
-Identifique el orchestrator del proyecto:
+Ya está en el orchestrator del proyecto (raíz del repositorio actual).
 
-1. **Busque el archivo `.contextrc.json`** en cualquiera de los repositorios del workspace
-2. Este archivo contiene la URL del repositorio orchestrator
-3. Si el orchestrator aún no está clonado localmente, clónelo
+1. **Verifique que está en la raíz del orchestrator**: `pwd` debe mostrar el directorio del orchestrator
+2. **Lea el archivo `context-manifest.json`** en la raíz del orchestrator
+3. **Lea el archivo `ai.properties.md`** para obtener configuraciones locales (base_path, etc.)
 
 ## 3. Cargar Manifiesto del Proyecto
 
@@ -32,7 +32,14 @@ Lea el `context-manifest.json` del orchestrator para entender:
 
 ## 4. Cargar MetaSpecs
 
-El repositorio de MetaSpecs está definido en `context-manifest.json` (generalmente con `role: "specs-provider"`).
+El repositorio de MetaSpecs es **separado** y está definido en `context-manifest.json` con `role: "metaspecs"`.
+
+**Localice el repositorio de metaspecs:**
+
+1. Lea `context-manifest.json` y encuentre el repositorio con `role: "metaspecs"`
+2. Obtenga el `id` de ese repositorio (ej: "my-project-metaspecs")
+3. Lea `ai.properties.md` para obtener el `base_path`
+4. El repositorio de metaspecs está en: `{base_path}/{metaspecs-id}/`
 
 **Lea siempre los archivos de índice primero:**
 

package/dist/templates/commands/pt-BR/engineer/pre-pr.md

@@ -35,14 +35,31 @@ cd <repositório>
 # Verificar status
 git status
 
-# Verificar linting
-npm run lint  # ou comando equivalente
-
-# Verificar formatação
-npm run format:check  # ou comando equivalente
-
-# Verificar build
-npm run build  # ou comando equivalente
+# Verificar linting (exemplos por stack):
+# Node.js: npm run lint / yarn lint / pnpm lint
+# Python: flake8 . / pylint src/ / black --check .
+# Java: mvn checkstyle:check / gradle check
+# Go: golangci-lint run / go vet ./...
+# Ruby: rubocop
+# Rust: cargo clippy
+# PHP: ./vendor/bin/phpcs
+# C#: dotnet format --verify-no-changes
+
+# Verificar formatação (exemplos por stack):
+# Node.js: npm run format:check / prettier --check .
+# Python: black --check . / autopep8 --diff .
+# Java: mvn formatter:validate
+# Go: gofmt -l . / go fmt ./...
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Verificar build (exemplos por stack):
+# Node.js: npm run build / yarn build
+# Python: python setup.py build
+# Java: mvn compile / gradle build
+# Go: go build ./...
+# Ruby: rake build
+# Rust: cargo build
 ```
 
 Checklist:
@@ -69,14 +86,33 @@ Para cada repositório:
 ```bash
 cd <repositório>
 
-# Executar testes unitários
-npm run test:unit  # ou comando equivalente
-
-# Executar testes de integração
-npm run test:integration  # ou comando equivalente
-
-# Verificar cobertura
-npm run test:coverage  # ou comando equivalente
+# Executar testes unitários (exemplos por stack):
+# Node.js: npm run test:unit / jest / vitest
+# Python: pytest tests/unit / python -m unittest
+# Java: mvn test / gradle test
+# Go: go test ./... -short
+# Ruby: rspec spec/unit / rake test:unit
+# Rust: cargo test --lib
+# PHP: ./vendor/bin/phpunit --testsuite=unit
+# C#: dotnet test --filter Category=Unit
+
+# Executar testes de integração (exemplos por stack):
+# Node.js: npm run test:integration
+# Python: pytest tests/integration
+# Java: mvn verify / gradle integrationTest
+# Go: go test ./... -run Integration
+# Ruby: rspec spec/integration
+# Rust: cargo test --test '*'
+# PHP: ./vendor/bin/phpunit --testsuite=integration
+
+# Verificar cobertura (exemplos por stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
 ```
 
 Checklist:

package/dist/templates/commands/pt-BR/quality/metrics.md

@@ -26,8 +26,15 @@ Para cada repositório modificado:
 ```bash
 cd <repositório>
 
-# Executar testes com cobertura
-npm run test:coverage  # ou comando equivalente
+# Executar testes com cobertura (exemplos por stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
+# C#: dotnet test /p:CollectCoverage=true
 
 # Capturar resultados
 ```
@@ -67,14 +74,29 @@ Analise a complexidade ciclomática dos arquivos modificados:
 ### 3. Qualidade do Código
 
 ```bash
-# Executar linting
-npm run lint
-
-# Verificar formatação
-npm run format:check
-
-# Análise estática (se disponível)
-npm run analyze
+# Executar linting (exemplos por stack):
+# Node.js: npm run lint / eslint .
+# Python: flake8 . / pylint src/
+# Java: mvn checkstyle:check
+# Go: golangci-lint run
+# Ruby: rubocop
+# Rust: cargo clippy
+
+# Verificar formatação (exemplos por stack):
+# Node.js: prettier --check .
+# Python: black --check .
+# Java: mvn formatter:validate
+# Go: gofmt -l .
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Análise estática (exemplos por stack):
+# Node.js: npm run analyze (se configurado)
+# Python: mypy src/ / bandit -r src/
+# Java: mvn pmd:check / spotbugs:check
+# Go: go vet ./...
+# Ruby: brakeman (para Rails)
+# Rust: cargo audit
 ```
 
 Documente:

package/dist/templates/commands/pt-BR/warm-up.md

@@ -16,11 +16,11 @@ Se não estiver em um workspace, pergunte ao usuário qual workspace usar ou se
 
 ## 2. Carregar Configuração do Projeto
 
-Identifique o orchestrator do projeto:
+Você já está no orchestrator do projeto (raiz do repositório atual).
 
-1. **Procure o arquivo `.contextrc.json`** em qualquer um dos repositórios do workspace
-2. Este arquivo contém a URL do repositório orchestrator
-3. Se o orchestrator ainda não estiver clonado localmente, clone-o
+1. **Verifique se está na raiz do orchestrator**: `pwd` deve mostrar o diretório do orchestrator
+2. **Leia o arquivo `context-manifest.json`** na raiz do orchestrator
+3. **Leia o arquivo `ai.properties.md`** para obter configurações locais (base_path, etc.)
 
 ## 3. Carregar Manifesto do Projeto
 
@@ -32,7 +32,14 @@ Leia o `context-manifest.json` do orchestrator para entender:
 
 ## 4. Carregar MetaSpecs
 
-O repositório de MetaSpecs está definido no `context-manifest.json` (geralmente com `role: "specs-provider"`).
+O repositório de MetaSpecs é **separado** e está definido no `context-manifest.json` com `role: "metaspecs"`.
+
+**Localize o repositório de metaspecs:**
+
+1. Leia `context-manifest.json` e encontre o repositório com `role: "metaspecs"`
+2. Obtenha o `id` desse repositório (ex: "my-project-metaspecs")
+3. Leia `ai.properties.md` para obter o `base_path`
+4. O repositório de metaspecs está em: `{base_path}/{metaspecs-id}/`
 
 **Leia sempre os arquivos de índice primeiro:**
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "context-first-cli",
-  "version": "2.0.0",
+  "version": "2.0.2",
   "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/engineer/pre-pr.md

@@ -30,19 +30,36 @@ Ensure that the implementation is complete, tested, and ready for review before
 For each modified repository:
 
 ```bash
-cd <repositório>
+cd <repository>
 
 # Check status
 git status
 
-# Check linting
-npm run lint  # or equivalent command
-
-# Check formatting
-npm run format:check  # or equivalent command
-
-# Check build
-npm run build  # or equivalent command
+# Check linting (examples by stack):
+# Node.js: npm run lint / yarn lint / pnpm lint
+# Python: flake8 . / pylint src/ / black --check .
+# Java: mvn checkstyle:check / gradle check
+# Go: golangci-lint run / go vet ./...
+# Ruby: rubocop
+# Rust: cargo clippy
+# PHP: ./vendor/bin/phpcs
+# C#: dotnet format --verify-no-changes
+
+# Check formatting (examples by stack):
+# Node.js: npm run format:check / prettier --check .
+# Python: black --check . / autopep8 --diff .
+# Java: mvn formatter:validate
+# Go: gofmt -l . / go fmt ./...
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Check build (examples by stack):
+# Node.js: npm run build / yarn build
+# Python: python setup.py build
+# Java: mvn compile / gradle build
+# Go: go build ./...
+# Ruby: rake build
+# Rust: cargo build
 ```
 
 Checklist:
@@ -67,16 +84,35 @@ Checklist:
 For each repository:
 
 ```bash
-cd <repositório>
-
-# Run unit tests
-npm run test:unit  # or equivalent command
-
-# Run integration tests
-npm run test:integration  # or equivalent command
-
-# Check coverage
-npm run test:coverage  # or equivalent command
+cd <repository>
+
+# Run unit tests (examples by stack):
+# Node.js: npm run test:unit / jest / vitest
+# Python: pytest tests/unit / python -m unittest
+# Java: mvn test / gradle test
+# Go: go test ./... -short
+# Ruby: rspec spec/unit / rake test:unit
+# Rust: cargo test --lib
+# PHP: ./vendor/bin/phpunit --testsuite=unit
+# C#: dotnet test --filter Category=Unit
+
+# Run integration tests (examples by stack):
+# Node.js: npm run test:integration
+# Python: pytest tests/integration
+# Java: mvn verify / gradle integrationTest
+# Go: go test ./... -run Integration
+# Ruby: rspec spec/integration
+# Rust: cargo test --test '*'
+# PHP: ./vendor/bin/phpunit --testsuite=integration
+
+# Check coverage (examples by stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
 ```
 
 Checklist:

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

@@ -24,10 +24,17 @@ Measure and document the quality of the implementation through objective metrics
 For each modified repository:
 
 ```bash
-cd <repositório>
-
-# Run tests with coverage
-npm run test:coverage  # or equivalent command
+cd <repository>
+
+# Run tests with coverage (examples by stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
+# C#: dotnet test /p:CollectCoverage=true
 
 # Capture results
 ```
@@ -67,14 +74,29 @@ Analyze the cyclomatic complexity of the modified files:
 ### 3. Code Quality
 
 ```bash
-# Run linting
-npm run lint
-
-# Check formatting
-npm run format:check
-
-# Static analysis (if available)
-npm run analyze
+# Run linting (examples by stack):
+# Node.js: npm run lint / eslint .
+# Python: flake8 . / pylint src/
+# Java: mvn checkstyle:check
+# Go: golangci-lint run
+# Ruby: rubocop
+# Rust: cargo clippy
+
+# Check formatting (examples by stack):
+# Node.js: prettier --check .
+# Python: black --check .
+# Java: mvn formatter:validate
+# Go: gofmt -l .
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Static analysis (examples by stack):
+# Node.js: npm run analyze (if configured)
+# Python: mypy src/ / bandit -r src/
+# Java: mvn pmd:check / spotbugs:check
+# Go: go vet ./...
+# Ruby: brakeman (for Rails)
+# Rust: cargo audit
 ```
 
 Document:

package/templates/commands/en/warm-up.md

@@ -16,11 +16,11 @@ If you're not in a workspace, ask the user which workspace to use or if you shou
 
 ## 2. Load Project Configuration
 
-Identify the project's orchestrator:
+You are already in the project's orchestrator (current repository root).
 
-1. **Look for the `.contextrc.json` file** in any of the workspace repositories
-2. This file contains the orchestrator repository URL
-3. If the orchestrator is not cloned locally yet, clone it
+1. **Verify you're at the orchestrator root**: `pwd` should show the orchestrator directory
+2. **Read the `context-manifest.json` file** at the orchestrator root
+3. **Read the `ai.properties.md` file** to get local configurations (base_path, etc.)
 
 ## 3. Load Project Manifest
 
@@ -32,7 +32,14 @@ Read the `context-manifest.json` from the orchestrator to understand:
 
 ## 4. Load MetaSpecs
 
-The MetaSpecs repository is defined in `context-manifest.json` (usually with `role: "specs-provider"`).
+The MetaSpecs repository is **separate** and defined in `context-manifest.json` with `role: "metaspecs"`.
+
+**Locate the metaspecs repository:**
+
+1. Read `context-manifest.json` and find the repository with `role: "metaspecs"`
+2. Get the `id` of that repository (e.g., "my-project-metaspecs")
+3. Read `ai.properties.md` to get the `base_path`
+4. The metaspecs repository is at: `{base_path}/{metaspecs-id}/`
 
 **Always read the index files first:**
 

package/templates/commands/es/engineer/pre-pr.md

@@ -30,19 +30,36 @@ Garantizar que la implementación está completa, probada y lista para revisión
 Para cada repositorio modificado:
 
 ```bash
-cd <repositório>
+cd <repositorio>
 
 # Verificar estado
 git status
 
-# Verificar linting
-npm run lint  # o comando equivalente
-
-# Verificar formateo
-npm run format:check  # o comando equivalente
-
-# Verificar build
-npm run build  # o comando equivalente
+# Verificar linting (ejemplos por stack):
+# Node.js: npm run lint / yarn lint / pnpm lint
+# Python: flake8 . / pylint src/ / black --check .
+# Java: mvn checkstyle:check / gradle check
+# Go: golangci-lint run / go vet ./...
+# Ruby: rubocop
+# Rust: cargo clippy
+# PHP: ./vendor/bin/phpcs
+# C#: dotnet format --verify-no-changes
+
+# Verificar formateo (ejemplos por stack):
+# Node.js: npm run format:check / prettier --check .
+# Python: black --check . / autopep8 --diff .
+# Java: mvn formatter:validate
+# Go: gofmt -l . / go fmt ./...
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Verificar build (ejemplos por stack):
+# Node.js: npm run build / yarn build
+# Python: python setup.py build
+# Java: mvn compile / gradle build
+# Go: go build ./...
+# Ruby: rake build
+# Rust: cargo build
 ```
 
 Checklist:
@@ -67,16 +84,35 @@ Checklist:
 Para cada repositorio:
 
 ```bash
-cd <repositório>
-
-# Ejecutar pruebas unitarias
-npm run test:unit  # o comando equivalente
-
-# Ejecutar pruebas de integración
-npm run test:integration  # o comando equivalente
-
-# Verificar cobertura
-npm run test:coverage  # o comando equivalente
+cd <repositorio>
+
+# Ejecutar pruebas unitarias (ejemplos por stack):
+# Node.js: npm run test:unit / jest / vitest
+# Python: pytest tests/unit / python -m unittest
+# Java: mvn test / gradle test
+# Go: go test ./... -short
+# Ruby: rspec spec/unit / rake test:unit
+# Rust: cargo test --lib
+# PHP: ./vendor/bin/phpunit --testsuite=unit
+# C#: dotnet test --filter Category=Unit
+
+# Ejecutar pruebas de integración (ejemplos por stack):
+# Node.js: npm run test:integration
+# Python: pytest tests/integration
+# Java: mvn verify / gradle integrationTest
+# Go: go test ./... -run Integration
+# Ruby: rspec spec/integration
+# Rust: cargo test --test '*'
+# PHP: ./vendor/bin/phpunit --testsuite=integration
+
+# Verificar cobertura (ejemplos por stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
 ```
 
 Checklist:

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

@@ -24,10 +24,17 @@ Medir y documentar la calidad de la implementación mediante métricas objetivas
 Para cada repositorio modificado:
 
 ```bash
-cd <repositório>
-
-# Ejecutar pruebas con cobertura
-npm run test:coverage  # ou comando equivalente
+cd <repositorio>
+
+# Ejecutar pruebas con cobertura (ejemplos por stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
+# C#: dotnet test /p:CollectCoverage=true
 
 # Capturar resultados
 ```
@@ -67,14 +74,29 @@ Analice la complejidad ciclomática de los archivos modificados:
 ### 3. Calidad del Código
 
 ```bash
-# Ejecutar linting
-npm run lint
-
-# Verificar formato
-npm run format:check
-
-# Análisis estático (si está disponible)
-npm run analyze
+# Ejecutar linting (ejemplos por stack):
+# Node.js: npm run lint / eslint .
+# Python: flake8 . / pylint src/
+# Java: mvn checkstyle:check
+# Go: golangci-lint run
+# Ruby: rubocop
+# Rust: cargo clippy
+
+# Verificar formato (ejemplos por stack):
+# Node.js: prettier --check .
+# Python: black --check .
+# Java: mvn formatter:validate
+# Go: gofmt -l .
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Análisis estático (ejemplos por stack):
+# Node.js: npm run analyze (si está configurado)
+# Python: mypy src/ / bandit -r src/
+# Java: mvn pmd:check / spotbugs:check
+# Go: go vet ./...
+# Ruby: brakeman (para Rails)
+# Rust: cargo audit
 ```
 
 Documente:

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

@@ -16,11 +16,11 @@ Si no está en un workspace, pregunte al usuario qué workspace usar o si debe c
 
 ## 2. Cargar Configuración del Proyecto
 
-Identifique el orchestrator del proyecto:
+Ya está en el orchestrator del proyecto (raíz del repositorio actual).
 
-1. **Busque el archivo `.contextrc.json`** en cualquiera de los repositorios del workspace
-2. Este archivo contiene la URL del repositorio orchestrator
-3. Si el orchestrator aún no está clonado localmente, clónelo
+1. **Verifique que está en la raíz del orchestrator**: `pwd` debe mostrar el directorio del orchestrator
+2. **Lea el archivo `context-manifest.json`** en la raíz del orchestrator
+3. **Lea el archivo `ai.properties.md`** para obtener configuraciones locales (base_path, etc.)
 
 ## 3. Cargar Manifiesto del Proyecto
 
@@ -32,7 +32,14 @@ Lea el `context-manifest.json` del orchestrator para entender:
 
 ## 4. Cargar MetaSpecs
 
-El repositorio de MetaSpecs está definido en `context-manifest.json` (generalmente con `role: "specs-provider"`).
+El repositorio de MetaSpecs es **separado** y está definido en `context-manifest.json` con `role: "metaspecs"`.
+
+**Localice el repositorio de metaspecs:**
+
+1. Lea `context-manifest.json` y encuentre el repositorio con `role: "metaspecs"`
+2. Obtenga el `id` de ese repositorio (ej: "my-project-metaspecs")
+3. Lea `ai.properties.md` para obtener el `base_path`
+4. El repositorio de metaspecs está en: `{base_path}/{metaspecs-id}/`
 
 **Lea siempre los archivos de índice primero:**
 

package/templates/commands/pt-BR/engineer/pre-pr.md

@@ -35,14 +35,31 @@ cd <repositório>
 # Verificar status
 git status
 
-# Verificar linting
-npm run lint  # ou comando equivalente
-
-# Verificar formatação
-npm run format:check  # ou comando equivalente
-
-# Verificar build
-npm run build  # ou comando equivalente
+# Verificar linting (exemplos por stack):
+# Node.js: npm run lint / yarn lint / pnpm lint
+# Python: flake8 . / pylint src/ / black --check .
+# Java: mvn checkstyle:check / gradle check
+# Go: golangci-lint run / go vet ./...
+# Ruby: rubocop
+# Rust: cargo clippy
+# PHP: ./vendor/bin/phpcs
+# C#: dotnet format --verify-no-changes
+
+# Verificar formatação (exemplos por stack):
+# Node.js: npm run format:check / prettier --check .
+# Python: black --check . / autopep8 --diff .
+# Java: mvn formatter:validate
+# Go: gofmt -l . / go fmt ./...
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Verificar build (exemplos por stack):
+# Node.js: npm run build / yarn build
+# Python: python setup.py build
+# Java: mvn compile / gradle build
+# Go: go build ./...
+# Ruby: rake build
+# Rust: cargo build
 ```
 
 Checklist:
@@ -69,14 +86,33 @@ Para cada repositório:
 ```bash
 cd <repositório>
 
-# Executar testes unitários
-npm run test:unit  # ou comando equivalente
-
-# Executar testes de integração
-npm run test:integration  # ou comando equivalente
-
-# Verificar cobertura
-npm run test:coverage  # ou comando equivalente
+# Executar testes unitários (exemplos por stack):
+# Node.js: npm run test:unit / jest / vitest
+# Python: pytest tests/unit / python -m unittest
+# Java: mvn test / gradle test
+# Go: go test ./... -short
+# Ruby: rspec spec/unit / rake test:unit
+# Rust: cargo test --lib
+# PHP: ./vendor/bin/phpunit --testsuite=unit
+# C#: dotnet test --filter Category=Unit
+
+# Executar testes de integração (exemplos por stack):
+# Node.js: npm run test:integration
+# Python: pytest tests/integration
+# Java: mvn verify / gradle integrationTest
+# Go: go test ./... -run Integration
+# Ruby: rspec spec/integration
+# Rust: cargo test --test '*'
+# PHP: ./vendor/bin/phpunit --testsuite=integration
+
+# Verificar cobertura (exemplos por stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
 ```
 
 Checklist:

package/templates/commands/pt-BR/quality/metrics.md

@@ -26,8 +26,15 @@ Para cada repositório modificado:
 ```bash
 cd <repositório>
 
-# Executar testes com cobertura
-npm run test:coverage  # ou comando equivalente
+# Executar testes com cobertura (exemplos por stack):
+# Node.js: npm run test:coverage / jest --coverage
+# Python: pytest --cov=src tests/
+# Java: mvn jacoco:report / gradle jacocoTestReport
+# Go: go test -cover ./...
+# Ruby: rspec --coverage
+# Rust: cargo tarpaulin
+# PHP: ./vendor/bin/phpunit --coverage-html coverage/
+# C#: dotnet test /p:CollectCoverage=true
 
 # Capturar resultados
 ```
@@ -67,14 +74,29 @@ Analise a complexidade ciclomática dos arquivos modificados:
 ### 3. Qualidade do Código
 
 ```bash
-# Executar linting
-npm run lint
-
-# Verificar formatação
-npm run format:check
-
-# Análise estática (se disponível)
-npm run analyze
+# Executar linting (exemplos por stack):
+# Node.js: npm run lint / eslint .
+# Python: flake8 . / pylint src/
+# Java: mvn checkstyle:check
+# Go: golangci-lint run
+# Ruby: rubocop
+# Rust: cargo clippy
+
+# Verificar formatação (exemplos por stack):
+# Node.js: prettier --check .
+# Python: black --check .
+# Java: mvn formatter:validate
+# Go: gofmt -l .
+# Ruby: rubocop --format-only
+# Rust: cargo fmt --check
+
+# Análise estática (exemplos por stack):
+# Node.js: npm run analyze (se configurado)
+# Python: mypy src/ / bandit -r src/
+# Java: mvn pmd:check / spotbugs:check
+# Go: go vet ./...
+# Ruby: brakeman (para Rails)
+# Rust: cargo audit
 ```
 
 Documente:

package/templates/commands/pt-BR/warm-up.md

@@ -16,11 +16,11 @@ Se não estiver em um workspace, pergunte ao usuário qual workspace usar ou se
 
 ## 2. Carregar Configuração do Projeto
 
-Identifique o orchestrator do projeto:
+Você já está no orchestrator do projeto (raiz do repositório atual).
 
-1. **Procure o arquivo `.contextrc.json`** em qualquer um dos repositórios do workspace
-2. Este arquivo contém a URL do repositório orchestrator
-3. Se o orchestrator ainda não estiver clonado localmente, clone-o
+1. **Verifique se está na raiz do orchestrator**: `pwd` deve mostrar o diretório do orchestrator
+2. **Leia o arquivo `context-manifest.json`** na raiz do orchestrator
+3. **Leia o arquivo `ai.properties.md`** para obter configurações locais (base_path, etc.)
 
 ## 3. Carregar Manifesto do Projeto
 
@@ -32,7 +32,14 @@ Leia o `context-manifest.json` do orchestrator para entender:
 
 ## 4. Carregar MetaSpecs
 
-O repositório de MetaSpecs está definido no `context-manifest.json` (geralmente com `role: "specs-provider"`).
+O repositório de MetaSpecs é **separado** e está definido no `context-manifest.json` com `role: "metaspecs"`.
+
+**Localize o repositório de metaspecs:**
+
+1. Leia `context-manifest.json` e encontre o repositório com `role: "metaspecs"`
+2. Obtenha o `id` desse repositório (ex: "my-project-metaspecs")
+3. Leia `ai.properties.md` para obter o `base_path`
+4. O repositório de metaspecs está em: `{base_path}/{metaspecs-id}/`
 
 **Leia sempre os arquivos de índice primeiro:**