context-first-cli 2.1.5 → 2.2.0

package/dist/templates/commands/pt-BR/products/spec.md

@@ -17,6 +17,44 @@ Este comando cria a especificação completa (Product Requirements Document) da
 
 ---
 
+## 📋 Configuração do Projeto
+
+**⚠️ IMPORTANTE: Sempre leia os arquivos de configuração do projeto ANTES de executar este comando!**
+
+### Arquivos Obrigatórios
+
+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
+
+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
+```
+
+### 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.
+
+
 ## 📋 Pré-requisitos
 
 - Issue refinada via `/refine`

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

@@ -11,6 +11,44 @@ Medir e documentar a qualidade da implementação através de métricas objetiva
 - Performance
 - Conformidade com padrões
 
+## 📋 Configuração do Projeto
+
+**⚠️ IMPORTANTE: Sempre leia os arquivos de configuração do projeto ANTES de executar este comando!**
+
+### Arquivos Obrigatórios
+
+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
+
+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
+```
+
+### 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.
+
+
 ## 📋 Pré-requisitos
 
 - Implementação concluída (após `/work`)

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

@@ -12,6 +12,44 @@ Criar registro estruturado de decisões técnicas e de produto, garantindo:
 
 **IMPORTANTE**: Este comando NÃO gera decisões novas. Ele apenas REGISTRA decisões que já foram tomadas no processo de desenvolvimento.
 
+## 📋 Configuração do Projeto
+
+**⚠️ IMPORTANTE: Sempre leia os arquivos de configuração do projeto ANTES de executar este comando!**
+
+### Arquivos Obrigatórios
+
+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
+
+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
+```
+
+### 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.
+
+
 ## 📋 Pré-requisitos
 
 - Executou pelo menos um dos comandos que geram decisões:

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

@@ -14,6 +14,44 @@ pwd
 
 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
+
+**⚠️ IMPORTANTE: Sempre leia os arquivos de configuração do projeto ANTES de executar este comando!**
+
+### Arquivos Obrigatórios
+
+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
+
+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
+```
+
+### 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).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "context-first-cli",
-  "version": "2.1.5",
+  "version": "2.2.0",
   "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

@@ -1,12 +1,50 @@
 # Technical Planning
 
-This command creates the detailed technical plan for feature implementation.
+This command creates the detailed technical plan for the feature implementation.
 
 ## 📋 Prerequisites
 
 - PRD created via `/spec`
 - Initial analysis done via `/start`
-- Files `context.md` and `architecture.md` created and approved
+- `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.
+
 
 ## 📍 IMPORTANT: Understand the Structure
 
@@ -46,17 +84,17 @@ This command creates the detailed technical plan for feature implementation.
 **Automatically locate MetaSpecs**:
 1. Read `context-manifest.json` from the orchestrator
 2. Find the repository with `"role": "metaspecs"`
-3. Read `ai.properties.md` to obtain the `base_path`
-4. The metaspecs are located at: `{base_path}/{metaspecs-repo-id}/`
+3. Read `ai.properties.md` to get the `base_path`
+4. The metaspecs are at: `{base_path}/{metaspecs-repo-id}/`
 5. Read the relevant `index.md` files to ensure compliance with:
    - System architecture
-   - Design and code standards
+   - Design and code patterns
    - Folder and file structure
    - Naming conventions
 
-## 🎯 Objective
+## 🎯 Goal
 
-Create a detailed technical plan that will guide the implementation, breaking the work into smaller, sequential units.
+Create a detailed technical plan that will guide the implementation, dividing the work into smaller, sequential units.
 
 ## 📝 Plan Structure
 
@@ -113,13 +151,13 @@ Create a detailed technical plan that will guide the implementation, breaking th
 
 ### 4. Implementation Plan
 
-Break down the work into small, sequential units:
+Divide the work into small, sequential units:
 
 ```markdown
 ## Implementation Plan
 
 ### Phase 1: [Phase Name]
-**Objective**: [What will be achieved in this phase]
+**Goal**: [What will be achieved in this phase]
 **Repositories**: [affected repos]
 
 #### Task 1.1: [Description]
@@ -265,7 +303,7 @@ src/
 
 ## 📄 Saving the Plan
 
-Save in `./.sessions/<ISSUE-ID>/plan.md`
+Save it in `./.sessions/<ISSUE-ID>/plan.md`
 
 ## 🔍 Review
 

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

@@ -10,32 +10,93 @@ 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.
+
+
+## 🛑 CRITICAL: WHERE TO WORK
+
+**⚠️ ATTENTION: If you need to make last-minute adjustments, ALL CODE MUST BE CREATED INSIDE THE WORKTREE!**
+
+**✅ CORRECT** - Work inside the worktree:
+```
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/src/file.ts  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/README.md  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/CHANGELOG.md  ✅
+```
+
+**❌ WRONG** - NEVER create code outside the worktree:
+```
+<orchestrator>/.sessions/file.ts  ❌
+<orchestrator>/.sessions/<ISSUE-ID>/file.ts  ❌
+{base_path}/<repo-name>/file.ts  ❌ (main repository!)
+```
+
+**ABSOLUTE RULE**:
+- 🛑 **Any code adjustment** (docs, changelog, fixes) **MUST be in** `<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/`
+- 🛑 **NEVER modify** the main repository at `{base_path}/<repo-name>/`
+- ✅ **Work ONLY** inside the worktree of the specific repository
+
 ## 🎯 PR Creation Process
 
 ### 1. Identify Modified Repositories
 
 For each repository in the workspace, check:
 ```bash
-cd <repositório>
+cd <repository>
 git status
-git log origin/main..HEAD  # View unpushed commits
+git log origin/main..HEAD  # See unpushed commits
 ```
 
 ### 2. Push Branches
 
 For each modified repository:
 ```bash
-cd <repositório>
+cd <repository>
 git push origin <branch-name>
 ```
 
 ### 3. Create Pull Requests
 
-For each repository, create a PR using GitHub CLI or the web interface:
+For each repository, create a PR using GitHub CLI or web interface:
 
 **Using GitHub CLI**:
 ```bash
-cd <repositório>
+cd <repository>
 gh pr create --title "[ISSUE-ID] Feature Title" \
   --body "$(cat ../.sessions/<ISSUE-ID>/pr-description.md)" \
   --base main
@@ -50,7 +111,7 @@ gh pr create --title "[ISSUE-ID] Feature Title" \
 
 ## 📝 Changes
 
-### Repository: <nome-do-repo>
+### Repository: <repo-name>
 
 - [Change 1]
 - [Change 2]
@@ -91,15 +152,15 @@ gh pr create --title "[ISSUE-ID] Feature Title" \
 ### 4. Link PRs
 
 If there are multiple PRs (one per repository):
-- Add cross-links between the PRs
+- Add cross-links between PRs
 - Document the recommended merge order
 - Indicate dependencies between PRs
 
 ### 5. Update Issue in Task Manager
 
-If the task manager is configured:
+If task manager is configured:
 - Move the issue to "In Review" or "PR Open"
-- Add PR links in the issue
+- Add PR links to the issue
 - Add a comment summarizing the changes
 
 ### 6. Session Documentation
@@ -140,13 +201,13 @@ Before requesting review:
 - [ ] PRs linked to each other
 - [ ] Issue updated in task manager
 - [ ] Tests passing in CI/CD
-- [ ] Session documentation complete
+- [ ] Complete session documentation
 
 ## 📢 Communication
 
 Notify the team about the PRs:
 - Mention relevant reviewers
-- Highlight critical changes or breaking changes
+- Highlight critical or breaking changes
 - Indicate urgency if applicable
 
 ---
@@ -161,7 +222,7 @@ Notify the team about the PRs:
 
 ## 🎯 Next Steps
 
-1. Await PR review
+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

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

@@ -4,13 +4,74 @@ This command validates that everything is ready to create Pull Requests.
 
 ## 📋 Prerequisites
 
-- Complete implementation (all `/plan` tasks executed)
+- Complete implementation (all tasks from `/plan` executed)
 - 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.
+
+
 ## 🎯 Objective
 
-Ensure that the implementation is complete, tested, and ready for review before creating the PRs.
+Ensure that the implementation is complete, tested, and ready for review before creating PRs.
+
+## 🛑 CRITICAL: WHERE TO WORK
+
+**⚠️ ATTENTION: ALL CODE (tests, fixes, adjustments) MUST BE CREATED INSIDE THE WORKTREE!**
+
+**✅ CORRECT** - Work inside the worktree:
+```
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/src/file.ts  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/tests/test.ts  ✅
+<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/.eslintrc.js  ✅
+```
+
+**❌ WRONG** - NEVER create code outside the worktree:
+```
+<orchestrator>/.sessions/test.ts  ❌
+<orchestrator>/.sessions/<ISSUE-ID>/test.ts  ❌
+{base_path}/<repo-name>/test.ts  ❌ (main repository!)
+```
+
+**ABSOLUTE RULE**:
+- 🛑 **ALL code** (tests, fixes, configurations) **MUST be in** `<orchestrator>/.sessions/<ISSUE-ID>/<repo-name>/`
+- 🛑 **NEVER modify** the main repository in `{base_path}/<repo-name>/`
+- ✅ **Work ONLY** inside the worktree of the specific repository
 
 ## ✅ Validation Checklist
 
@@ -22,7 +83,7 @@ Ensure that the implementation is complete, tested, and ready for review before
 - [ ] All plan tasks have been executed
 - [ ] All functional requirements from the PRD have been implemented
 - [ ] All acceptance criteria have been met
-- [ ] No functionality is left half-done
+- [ ] No functionality is half-done
 ```
 
 ### 2. Code Quality
@@ -234,16 +295,16 @@ Create `./.sessions/<ISSUE-ID>/pr-description.md`:
 3. [Expected result]
 
 ## 🔍 Notes for Reviewers
-- [Attention point 1]
-- [Attention point 2]
+- [Point of attention 1]
+- [Point of attention 2]
 ```
 
 ## 🚨 Issues Found
 
 If any validation fails:
 1. 🛑 **STOP** the PR creation process
-2. 📝 **DOCUMENT** the issue
-3. 🔧 **FIX** the issue
+2. 📝 **DOCUMENT** the problem
+3. 🔧 **FIX** the problem
 4. 🔄 **RUN** `/pre-pr` again
 
 ## 📊 Validation Report
@@ -295,4 +356,4 @@ If all validations passed:
 /pr
 ```
 
-This command will create the Pull Requests for all modified repositories.
+This command will create Pull Requests for all modified repositories.