context-first-cli 2.1.5 → 2.2.0

package/dist/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/dist/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/dist/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.

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

@@ -1,6 +1,6 @@
 # Start of Development
 
-This command starts the development of a feature in the current workspace.
+This command initiates the development of a feature in the current workspace.
 
 ## 📍 IMPORTANT: Understand the Structure
 
@@ -14,7 +14,7 @@ This command starts the development of a feature in the current workspace.
 └── plan.md          # plan (mutable - created by /plan)
 ```
 
-**Main repositories** (read-only):
+**Main Repositories** (read-only):
 ```
 {base_path}/repo-1/  # main repo (branch main/master)
 {base_path}/repo-2/  # main repo (branch main/master)
@@ -24,7 +24,44 @@ This command starts the development of a feature in the current workspace.
 - ✅ Read metaspecs and code from main repositories (read-only)
 - ✅ Create `context.md` and `architecture.md` in `.sessions/<ISSUE-ID>/`
 - ❌ NEVER checkout main repositories
-- ❌ NEVER modify code in this command (use `/work` afterwards)
+- ❌ NEVER modify code in this command (use `/work` later)
+
+## 📋 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 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.
 
 ## 📚 Load MetaSpecs
 
@@ -33,7 +70,7 @@ This command starts the development of a feature in the current workspace.
 2. Find the repository with `"role": "metaspecs"`
 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:
+5. Read relevant `index.md` files:
    - Business context
    - Stack, architecture, and technical patterns
    - Project conventions
@@ -52,7 +89,7 @@ Before starting, load the context by consulting:
    - Confirm you are in the correct workspace (check `workspace directory`)
    - List repositories available in the workspace
 
-2. **Verify Branches**:
+2. **Check Branches**:
    - For each repository in the workspace, check the current branch
    - Confirm all branches are synchronized
 
@@ -73,15 +110,15 @@ Analyze the specification and build a complete understanding by answering:
 - **Which** metric do we want to impact?
 
 ### Functional
-- **What is the expected outcome**? (user behavior, system output)
+- **What is the expected outcome?** (user behavior, system output)
 - **Which components** will be created/modified in each repository?
 - **Which integrations** between repositories are necessary?
 
 ### Technical
-- **Approved stack**? Check against technical specifications
-- **Architectural patterns**? Check ADRs (if available)
-- **New dependencies**? Justify and document
-- **How to test**? (according to project standards)
+- **Approved stack?** Check against technical specifications
+- **Architectural patterns?** Check ADRs (if available)
+- **New dependencies?** Justify and document
+- **How to test?** (according to project standards)
 
 ### Validation against MetaSpecs
 
@@ -97,16 +134,16 @@ After initial analysis, formulate **3-5 most important clarifications**:
 
 **Examples of relevant questions**:
 - Which repository should contain the main logic?
-- How should the repositories communicate?
+- How should repositories communicate?
 - Are there dependencies between changes in different repos?
 - What is the recommended implementation order?
-- Is there any impact on APIs or contracts between services?
+- Is there impact on APIs or contracts between services?
 
 ## 💾 Creation of Context.md
 
 **IMPORTANT**: This file is **IMMUTABLE** after approval. It must not be modified by subsequent commands.
 
-Create the file `./.sessions/<ISSUE-ID>/context.md` with:
+Create file `./.sessions/<ISSUE-ID>/context.md` with:
 
 ```markdown
 # Context: [Feature Name]
@@ -135,7 +172,7 @@ Create the file `./.sessions/<ISSUE-ID>/context.md` with:
 [Technical limitations, performance targets, budget]
 
 ## Tests
-[Critical E2E, required unit tests, expected coverage]
+[Critical E2E, necessary unit tests, expected coverage]
 ```
 
 **After creating `context.md`, request user review and approval before proceeding.**
@@ -153,17 +190,17 @@ Create the file `./.sessions/<ISSUE-ID>/context.md` with:
 1. **Read ADRs (Architecture Decision Records)**:
    - List ADRs in metaspecs
    - Read ALL ADRs relevant to the feature
-   - Identify constraints and mandatory patterns
+   - Identify mandatory constraints and patterns
 
 2. **Consult architectural patterns**:
    - Read project structure guides in metaspecs
-   - Read code patterns in metaspecs
+   - Read coding patterns in metaspecs
    - Identify existing patterns in code (use Glob/Grep to find similar examples)
 
 3. **Validate compliance with ADRs**:
-   - For each relevant ADR, verify if the proposed solution respects the decisions
+   - For each relevant ADR, check if the proposed solution respects the decisions
    - Document compliance in architecture.md
-   - If there is violation, justify or propose correction
+   - If violation exists, justify or propose correction
 
 4. **Analyze existing code**:
    - Use Glob/Grep to find similar components/modules
@@ -172,7 +209,7 @@ Create the file `./.sessions/<ISSUE-ID>/context.md` with:
 
 ### Architecture Document Structure
 
-Create the file `./.sessions/<ISSUE-ID>/architecture.md` with:
+Create file `./.sessions/<ISSUE-ID>/architecture.md` with:
 
 ```markdown
 # Architecture: [Feature Name]
@@ -204,7 +241,7 @@ repo-1/
 ```
 
 ## Patterns and Best Practices
-[Patterns that will be maintained or introduced]
+[Patterns to be maintained or introduced]
 
 ## ADR Validation
 [List of consulted ADRs and compliance]
@@ -213,7 +250,7 @@ repo-1/
 - [x] ADR-002: [Name] - Compliant
 
 ## External Dependencies
-[Libraries that will be used or added]
+[Libraries to be used or added]
 
 ## Technical Decisions
 
@@ -226,7 +263,7 @@ repo-1/
 **Justification**: [Why we chose this option]
 
 ## Constraints and Assumptions
-[Technical limitations and assumptions]
+[Technical limitations and premises]
 
 ## Trade-offs
 [Alternatives considered and why they were not chosen]
@@ -262,7 +299,7 @@ repo-1/
 
 ## 🎯 Next Step
 
-**After user approval of the files `context.md` and `architecture.md`**:
+**After user approval of `context.md` and `architecture.md` files**:
 
 ```bash
 /plan

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

@@ -7,11 +7,49 @@ This command executes a unit of work in the current workspace, implementing part
 Before executing, make sure that:
 - You have run `/start` and `/plan` to have the technical plan
 - You are in the correct workspace: `<orchestrator>/.sessions/<ISSUE-ID>/`
-- You have the `.sessions/<ISSUE-ID>/` files available:
+- You have the files `.sessions/<ISSUE-ID>/` available:
   - `context.md` (immutable)
   - `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.
+
+
 ## 📍 IMPORTANT: Understand the Structure
 
 **Workspace** (where you work):
@@ -32,7 +70,7 @@ Before executing, make sure that:
 
 **GOLDEN RULE**:
 - ✅ Work ONLY inside `<orchestrator>/.sessions/<ISSUE-ID>/`
-- ✅ Make commits in the worktrees inside the workspace
+- ✅ Commit in the worktrees inside the workspace
 - ❌ NEVER checkout branches in the main repositories
 - ❌ NEVER navigate to `{base_path}/{repo-id}/`
 
@@ -57,7 +95,7 @@ Before executing, make sure that:
 **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 specific repository worktree
+- ✅ **Only valid place**: Inside the repository’s worktree
 
 ## ⚠️ IMPORTANT: Immutable Files
 
@@ -67,8 +105,8 @@ Before executing, make sure that:
 - ✅ **UPDATE** `.sessions/<ISSUE-ID>/plan.md` (mark progress)
 - ✅ **IMPLEMENT** code **INSIDE THE WORKTREE**: `.sessions/<ISSUE-ID>/<repo-name>/`
 - ✅ **MAKE COMMITS** in the worktrees: `.sessions/<ISSUE-ID>/<repo-name>/`
-- ❌ **DO NOT modify `context.md` or `architecture.md`**
-- ❌ **DO NOT checkout branches in the main repositories (outside the workspace)**
+- ❌ **Do NOT modify `context.md` or `architecture.md`**
+- ❌ **Do NOT checkout branches in the main repositories (outside workspace)**
 - 🛑 **NEVER create code directly in `.sessions/` or `.sessions/<ISSUE-ID>/`**
 
 ## 📚 Load MetaSpecs
@@ -83,7 +121,7 @@ Before executing, make sure that:
    - Respect defined architecture
    - Use correct conventions
 
-## 🎯 Goal
+## 🎯 Objective
 
 Implement a specific unit of work from the plan, which may involve:
 - Creating new files/components
@@ -124,7 +162,7 @@ Based on the technical plan (`./.sessions/<ISSUE-ID>/plan.md`), identify:
 
 
 
-**IMPORTANT**: Work ONLY inside the workspace in `.sessions/<ISSUE-ID>/`
+**IMPORTANT**: Work ONLY inside the workspace `.sessions/<ISSUE-ID>/`
 
 For each repository in the workspace: