context-first-cli 2.3.1 → 2.3.2

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.

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

@@ -17,42 +17,9 @@ This command creates the complete specification (Product Requirements Document)
 
 ---
 
-## 📋 Project Configuration
+## Configuration
 
-**⚠️ IMPORTANT: Always read the project configuration files BEFORE running this command!**
-
-### Mandatory Files
-
-1. **`context-manifest.json`** (orchestrator root)
-   - List of project repositories
-   - Roles of each repository (metaspecs, application, etc.)
-   - URLs and dependencies between repositories
-
-2. **`ai.properties.md`** (orchestrator root)
-   - Project settings (`project_name`, `base_path`)
-   - Task management system (`task_management_system`)
-   - Credentials and specific configurations
-
-### How to Read
-
-```bash
-# 1. Read context-manifest.json
-cat context-manifest.json
-
-# 2. Read ai.properties.md
-cat ai.properties.md
-```
-
-### Essential Information
-
-After reading the files, you will have:
-- ✅ Complete list of project repositories
-- ✅ Location of the metaspecs repository
-- ✅ Base path to locate repositories
-- ✅ Configured task management system
-- ✅ Project-specific configurations
-
-**🛑 DO NOT proceed without reading these files!** They contain critical information for correct command execution.
+Read `context-manifest.json` and `ai.properties.md` from the orchestrator to get repositories, base_path, and task_management_system.
 
 ## 📋 Prerequisites
 
@@ -301,4 +268,4 @@ After PRD approval:
 /start
 ```
 
-This command will start feature development.
+This command will start feature development.

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

@@ -11,42 +11,9 @@ Measure and document the quality of the implementation through objective metrics
 - Performance
 - Compliance with standards
 
-## 📋 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 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.
+Read `context-manifest.json` and `ai.properties.md` from the orchestrator to get repositories, base_path, and task_management_system.
 
 ## 📋 Prerequisites
 
@@ -296,4 +263,4 @@ After running this command, you will have:
 - Comparison with baseline and goals
 - Identification of quality issues
 - Recommendations for actions
-- Objective basis for merge approval
+- Objective basis for merge approval

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

@@ -12,43 +12,9 @@ Create a structured record of technical and product decisions, ensuring:
 
 **IMPORTANT**: This command DOES NOT generate new decisions. It only RECORDS decisions that have already been made during the development process.
 
-## 📋 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.
 
 ## 📋 Prerequisites
 
@@ -203,4 +169,4 @@ After running this command, you will have:
 - Complete decision log in `./.sessions/<ISSUE-ID>/decisions.md`
 - Traceability of every choice made
 - Documentation for future reference
-- Basis for ADRs (if decisions are architectural)
+- Basis for ADRs (if decisions are architectural)