context-first-cli 2.3.1 → 2.3.4

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

@@ -1,123 +1,59 @@
 # Aquecimento - Carregamento de Contexto
 
-Este comando prepara o ambiente carregando o contexto completo do projeto e do workspace atual.
+Prepara o ambiente carregando o contexto otimizado do projeto.
 
-## 1. Identificar Workspace Atual
+## 1. Carregar Configuração
 
-Verifique se você está dentro de um workspace criado pelo `context-cli`:
+Leia os arquivos do orchestrator:
+- **`context-manifest.json`** - Repositórios e roles
+- **`ai.properties.md`** - base_path, task_management_system
 
-```bash
-# Verificar se está em um diretório de workspace
-pwd
-# O workspace geralmente está em ~/workspaces/<ISSUE-ID>/
-```
-
-Se não estiver em um workspace, pergunte ao usuário qual workspace usar ou se deve criar um novo com `feature:start`.
-
-## 📋 Configuração do Projeto
+## 2. Carregar Contexto Compacto (OTIMIZADO)
 
-**⚠️ IMPORTANTE: Sempre leia os arquivos de configuração do projeto ANTES de executar este comando!**
+**IMPORTANTE**: Use carregamento PROGRESSIVO para economizar janela de contexto.
 
-### Arquivos Obrigatórios
+### Obrigatório (warm-up)
 
-1. **`context-manifest.json`** (raiz do orchestrator)
-   - Lista de repositórios do projeto
-   - Roles de cada repositório (metaspecs, application, etc.)
-   - URLs e dependências entre repositórios
+Localize metaspecs via `context-manifest.json` (role: "specs-provider"):
 
-2. **`ai.properties.md`** (raiz do orchestrator)
-   - Configurações do projeto (`project_name`, `base_path`)
-   - Sistema de gerenciamento de tarefas (`task_management_system`)
-   - Credenciais e configurações específicas
-
-### Como Ler
-
-```bash
-# 1. Ler context-manifest.json
-cat context-manifest.json
-
-# 2. Ler ai.properties.md
-cat ai.properties.md
+```
+{base_path}/{metaspecs-id}/specs/_meta/WARM_UP_CONTEXT.md  (~100 linhas)
 ```
 
-### Informações Essenciais
-
-Após ler os arquivos, você terá:
-- ✅ Lista completa de repositórios do projeto
-- ✅ Localização do repositório de metaspecs
-- ✅ Base path para localizar repositórios
-- ✅ Sistema de task management configurado
-- ✅ Configurações específicas do projeto
-
-**🛑 NÃO prossiga sem ler estes arquivos!** Eles contêm informações críticas para a execução correta do comando.
-
-
-## 2. Carregar Configuração do Projeto
-
-Você já está no orchestrator do projeto (raiz do repositório atual).
-
-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
-
-Leia o `context-manifest.json` do orchestrator para entender:
-- Lista completa de repositórios do ecossistema
-- URL do repositório de MetaSpecs
-- Dependências entre repositórios
-- Roles de cada repositório (application, library, service, specs-provider)
-
-## 4. Carregar MetaSpecs
-
-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}/`
+Este arquivo contém TODOS os essenciais:
+- Stack tecnológica
+- Hierarquia de contexto
+- 5 regras críticas
+- Padrões de código mínimos
+- Tabela de carregamento sob demanda
 
-**Leia sempre os arquivos de índice primeiro:**
+### Sob Demanda (NÃO carregar durante warm-up)
 
-1. **`README.md`** - Visão geral do projeto e estrutura de documentação
-2. **`index.md`** (na raiz ou em subpastas) - Índice de especificações disponíveis
+| Necessidade | Documento |
+|-------------|-----------|
+| Gerar código | `CLAUDE.meta.md` |
+| Arquitetura | `ARCHITECTURE.md` |
+| Feature específica | `features/{FEATURE}.md` |
+| Anti-patterns completos | `ANTI_PATTERNS.md` |
 
-**Use os índices como referência** para navegar até as especificações específicas que você precisa. Não assuma que arquivos específicos existem - sempre consulte os índices primeiro.
+## 3. Verificar Repositórios
 
-## 5. Carregar Sessão Atual (se existir)
+Para cada repositório no `context-manifest.json`:
+- Verificar existência em `{base_path}/{repo-id}/`
+- **NÃO** ler README.md agora (sob demanda)
 
-Verifique se existe uma sessão salva para este workspace:
+## 4. Verificar Sessão (se existir)
 
 ```bash
-# Procurar por sessão no orchestrator
 ls -la .sessions/<ISSUE-ID>/ 2>/dev/null
 ```
 
-Se existir, leia os arquivos de sessão para recuperar o contexto da última execução.
-
-## 6. Contexto dos Repositórios
-
-Para cada repositório presente no workspace, leia:
-- `README.md` - Propósito e visão geral do repositório
-- Arquivo de configuração principal (`package.json`, `pom.xml`, `requirements.txt`, etc.)
-
-## 7. Navegação Inteligente
-
-- **Código**: Use ferramentas de busca (glob, grep) para localizar arquivos relevantes
-- **Documentação**: Use os índices dos MetaSpecs como referência
-- **Aguarde Instruções**: NÃO leia outros arquivos agora. Aguarde o próximo comando.
-
-## 8. Princípio Jidoka (Parar ao Detectar Problemas)
+## 5. Princípio Jidoka
 
-Se detectar desalinhamento, conflitos ou problemas:
-1. 🛑 **PARE** imediatamente
-2. 📝 **DOCUMENTE** o problema encontrado
-3. 💬 **ALERTE** o usuário antes de prosseguir
+Se problemas detectados: **PARE**, documente, alerte o usuário.
 
 ---
 
-**Argumentos fornecidos**: #$ARGUMENTS
+**Argumentos**: #$ARGUMENTS
 
 **Status**: Contexto carregado. Aguardando próximo comando.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "context-first-cli",
-  "version": "2.3.1",
+  "version": "2.3.4",
   "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/plan.md

@@ -8,43 +8,9 @@ This command creates the detailed technical plan for the feature implementation.
 - Initial analysis done via `/start`
 - `context.md` and `architecture.md` files created and approved
 
-## 📋 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 the correct execution of the command.
+## Configuration
 
+Read `context-manifest.json` and `ai.properties.md` from the orchestrator to get repositories, base_path, and task_management_system.
 
 ## 📍 IMPORTANT: Understand the Structure
 
@@ -332,4 +298,4 @@ After plan approval:
 /work
 ```
 
-This command will start executing the first work unit of the plan.
+This command will start executing the first work unit of the plan.

package/templates/commands/en/engineer/pr.md

@@ -10,43 +10,9 @@ Before creating PRs, make sure that:
 - All tests are passing
 - Documentation is up to date
 
-## 📋 Project Configuration
-
-**⚠️ IMPORTANT: Always read the project configuration files BEFORE running this command!**
-
-### Required Files
-
-1. **`context-manifest.json`** (root of the orchestrator)
-   - List of project repositories
-   - Roles of each repository (metaspecs, application, etc.)
-   - URLs and dependencies between repositories
-
-2. **`ai.properties.md`** (root of the orchestrator)
-   - 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
-- ✅ Specific project configurations
-
-**🛑 DO NOT proceed without reading these files!** They contain critical information for the correct execution of the command.
+## Configuration
 
+Read `context-manifest.json` and `ai.properties.md` from the orchestrator to get repositories, base_path, and task_management_system.
 
 ## 🛑 CRITICAL: WHERE TO WORK
 
@@ -120,7 +86,7 @@ gh pr create --title "[ISSUE-ID] Feature Title" \
 ## 🔗 Relationships
 
 - **Issue**: <ISSUE-ID>
-- **Related PRs**: 
+- **Related PRs**:
   - <repo-1>#<PR-number>
   - <repo-2>#<PR-number>
 
@@ -225,4 +191,4 @@ Notify the team about the PRs:
 1. Await PR reviews
 2. Respond to comments and make adjustments
 3. After approval, merge in the recommended order
-4. Run `context-cli feature:end <ISSUE-ID>` to clean the workspace
+4. Run `context-cli feature:end <ISSUE-ID>` to clean the workspace

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

@@ -1,4 +1,4 @@
-# Preparation for Pull Request
+# Pull Request Preparation
 
 This command validates that everything is ready to create Pull Requests.
 
@@ -8,43 +8,9 @@ This command validates that everything is ready to create Pull Requests.
 - All commits made
 - Clean and organized workspace
 
-## 📋 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.
+## Configuration
 
+Read `context-manifest.json` and `ai.properties.md` from the orchestrator to get repositories, base_path, and task_management_system.
 
 ## 🎯 Objective
 
@@ -356,4 +322,4 @@ If all validations passed:
 /pr
 ```
 
-This command will create Pull Requests for all modified repositories.
+This command will create Pull Requests for all modified repositories.

package/templates/commands/en/engineer/start.md

@@ -1,4 +1,4 @@
-# Start of Development
+# Start Development
 
 This command initiates the development of a feature in the current workspace.
 
@@ -26,42 +26,9 @@ This command initiates the development of a feature in the current workspace.
 - ❌ NEVER checkout main repositories
 - ❌ NEVER modify code in this command (use `/work` later)
 
-## 📋 Project Configuration
+## 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 among 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.
+Read `context-manifest.json` and `ai.properties.md` from the orchestrator to get repositories, base_path, and task_management_system.
 
 ## 📚 Load MetaSpecs
 
@@ -315,4 +282,4 @@ This command will create the detailed technical implementation plan.
 
 - ✅ They can be READ by subsequent commands (`/plan`, `/work`)
 - ❌ They MUST NOT be MODIFIED by any command
-- ❌ If changes are needed, discuss with the user and create new files or update the issue in the task manager
+- ❌ If changes are needed, discuss with the user and create new files or update the issue in the task manager

package/templates/commands/en/engineer/work.md

@@ -12,43 +12,9 @@ Before executing, make sure that:
   - `architecture.md` (immutable)
   - `plan.md` (mutable)
 
-## 📋 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.
+## Configuration
 
+Read `context-manifest.json` and `ai.properties.md` from the orchestrator to get repositories, base_path, and task_management_system.
 
 ## 📍 IMPORTANT: Understand the Structure
 
@@ -95,7 +61,7 @@ After reading the files, you will have:
 **ABSOLUTE RULE**:
 - 🛑 **EVERY code file** (`.ts`, `.js`, `.py`, `.java`, etc.) **MUST be inside** `<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/`
 - 🛑 **NEVER create code** directly in `<orchestrator>/.sessions/` or `<orchestrator>/.sessions/<ISSUE-ID>/`
-- ✅ **Only valid place**: Inside the repository’s worktree
+- ✅ **Only valid place**: Inside the repository's worktree
 
 ## ⚠️ IMPORTANT: Immutable Files
 
@@ -287,4 +253,4 @@ If you encounter problems during implementation:
 - Work in small, incremental units
 - Commit frequently (atomic commits)
 - Document important decisions in the session
-- Keep repositories synchronized with each other
+- Keep repositories synchronized with each other

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

@@ -12,42 +12,9 @@ This command validates requirements, decisions, or implementations against the p
 - ❌ **DO NOT modify code**
 - ❌ **DO NOT modify `context.md` or `architecture.md`**
 
-## 📋 Project Configuration
+## Configuration
 
-**⚠️ IMPORTANT: Always read the project configuration files BEFORE running this command!**
-
-### Required Files
-
-1. **`context-manifest.json`** (root of the orchestrator)
-   - List of project repositories
-   - Roles of each repository (metaspecs, application, etc.)
-   - URLs and dependencies between repositories
-
-2. **`ai.properties.md`** (root of the orchestrator)
-   - Project settings (`project_name`, `base_path`)
-   - 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
-- ✅ Specific project configurations
-
-**🛑 DO NOT proceed without reading these files!** They contain critical information for the correct execution of the command.
+Read `context-manifest.json` and `ai.properties.md` from the orchestrator to get repositories, base_path, and task_management_system.
 
 ## 🎯 Objective
 
@@ -267,4 +234,4 @@ If critical conflicts are found:
 After validation:
 - If ✅: Proceed to the next phase
 - If ⚠️: Document reservations and proceed with approval
-- If ❌: Fix conflicts before proceeding
+- If ❌: Fix conflicts before proceeding

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

@@ -18,59 +18,11 @@ You are a product specialist responsible for collecting and documenting new idea
 
 ---
 
-## 📋 Project Setup
+## Configuration
 
-**⚠️ IMPORTANT: Always read the project configuration files BEFORE running this command!**
+Read `context-manifest.json` and `ai.properties.md` from the orchestrator to get repositories, base_path, and task_management_system.
 
-### 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 the correct execution of the command.
-
-## Project Context
-
-Before starting, load the context by consulting:
-
-1. **Automatically locate MetaSpecs**:
-   - Read `context-manifest.json` from the orchestrator
-   - Find the repository with `"role": "metaspecs"`
-   - Read `ai.properties.md` to get the `base_path`
-   - The metaspecs are located at: `{base_path}/{metaspecs-repo-id}/`
-   - Read the `index.md` files as reference
-
-2. **Project structure**:
-   - `context-manifest.json` - List of repositories and their roles
-   - `README.md` of involved repositories
-
-## Your Goal
+## Objective
 
 Understand the user's request and capture it as an issue in the task manager (via MCP).
 
@@ -134,7 +86,7 @@ Just ensure the idea is **adequately understood**.
    - Example split:
      ```
      Original Issue: "Complete payment system"
-     
+
      Suggested Split:
      - FIN-101: Payment gateway integration (backend)
      - FIN-102: Checkout interface (frontend)
@@ -155,22 +107,22 @@ Just ensure the idea is **adequately understood**.
 5. **Issue Saving**
 
    **PRIORITY 1: Use MCP (Model Context Protocol)**
-   
+
    Check if MCP is configured for the task manager:
    - Read `ai.properties.md` from the orchestrator to identify the `task_management_system`
    - If `task_management_system=jira`: Use Jira MCP to create the issue
    - If `task_management_system=linear`: Use Linear MCP to create the issue
    - If `task_management_system=github`: Use GitHub MCP to create the issue
    - If `task_management_system=azure`: Use Azure Boards MCP to create the issue
-   
+
    **When using MCP:**
    - Create the issue directly in the task manager
    - Obtain the created issue ID (e.g., FIN-123, LIN-456)
    - Inform the user: "✅ Issue [ID] created in [task manager]"
    - **DO NOT create a .md file**
-   
+
    **FALLBACK: Create .md file only if MCP fails**
-   
+
    If MCP is not available or fails:
    - Create a file in `./.sessions/<ISSUE-ID>/collect.md`
    - Use manual ID format: `LOCAL-001`, `LOCAL-002`, etc.
@@ -215,4 +167,4 @@ After approval and saving the issue:
 /refine [ISSUE-ID]
 ```
 
-This command will transform the collected issue into refined and validated requirements.
+This command will transform the collected issue into refined and validated requirements.

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

@@ -17,43 +17,9 @@ You are a product expert responsible for helping to refine requirements for the
 
 ---
 
-## 📋 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.
+## Configuration
 
+Read `context-manifest.json` and `ai.properties.md` from the orchestrator to get repositories, base_path, and task_management_system.
 
 ## Objective
 
@@ -125,7 +91,7 @@ Once you have gathered sufficient information and validated against metaspecs, p
 - Example split:
   ```
   Original Issue: "Multi-channel notification system"
-  
+
   Suggested Split:
   - FIN-201: Queue and worker infrastructure (backend)
   - FIN-202: Email notifications (backend + templates)
@@ -262,4 +228,4 @@ Once the user approves, save the requirements:
 
 **Example**: `/spec FIN-3`
 
-This command will create a PRD (Product Requirements Document) complete 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.