context-first-cli 2.2.0 → 2.3.0

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

@@ -6,17 +6,54 @@ This command creates the complete specification (Product Requirements Document)
 
 **This command is ONLY for requirements documentation:**
 - ✅ Create PRD (Product Requirements Document)
-- ✅ Update issue in task manager via MCP
+- ✅ Update issue in the task manager via MCP
 - ✅ **READ** files from main repositories (read-only)
 - ❌ **DO NOT implement code**
 - ❌ **DO NOT edit code files**
 - ❌ **DO NOT checkout branches in main repositories**
-- ❌ **DO NOT commit**
+- ❌ **DO NOT make commits**
 
 **Next step**: `/start` to begin development.
 
 ---
 
+## 📋 Project 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.
+
 ## 📋 Prerequisites
 
 - Issue refined via `/refine`
@@ -29,7 +66,7 @@ This command creates the complete specification (Product Requirements Document)
 2. Find the repository with `"role": "metaspecs"`
 3. Read `ai.properties.md` to get the `base_path`
 4. The metaspecs are located at: `{base_path}/{metaspecs-repo-id}/`
-5. Read the relevant `index.md` files to ensure compliance with:
+5. Read relevant `index.md` files to ensure compliance with:
    - System architecture
    - Design patterns
    - Technical constraints
@@ -133,7 +170,7 @@ Create a complete PRD that will serve as the single source of truth for implemen
 - **External**: [external APIs, if any]
 
 ### Data Model
-[Describe changes to the data model, if any]
+[Describe changes to data model, if any]
 ```
 
 ### 6. Acceptance Criteria
@@ -162,7 +199,7 @@ Create a complete PRD that will serve as the single source of truth for implemen
 ```markdown
 ## Out of Scope
 
-Features that WILL NOT be implemented in this version:
+Features that will NOT be implemented in this version:
 - [Item 1]
 - [Item 2]
 

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

@@ -11,6 +11,43 @@ Measure and document the quality of the implementation through objective metrics
 - Performance
 - Compliance with standards
 
+## 📋 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.
+
 ## 📋 Prerequisites
 
 - Implementation completed (after `/work`)
@@ -57,14 +94,14 @@ Document:
 
 ### 2. Code Complexity
 
-Analyze the cyclomatic complexity of the modified files:
+Analyze the cyclomatic complexity of modified files:
 
 ```markdown
 ## Code Complexity
 
 ### Files with High Complexity
-- **arquivo1.ts**: Complexity 15 (recommended: < 10)
-- **arquivo2.ts**: Complexity 12
+- **file1.ts**: Complexity 15 (recommended: < 10)
+- **file2.ts**: Complexity 12
 
 ### Recommendations
 - [Refactoring suggestion 1]
@@ -163,12 +200,12 @@ Identify technical debt introduced or resolved:
 ```markdown
 ## Technical Debt
 
-### Introduced Debt
+### Debt Introduced
 - **Item 1**: [Description and justification]
   - Severity: High / Medium / Low
   - Resolution plan: [when and how to resolve]
 
-### Resolved Debt
+### Debt Resolved
 - **Item 1**: [What was resolved]
   - Impact: [improvement achieved]
 ```
@@ -185,7 +222,7 @@ Create `./.sessions/<ISSUE-ID>/metrics.md`:
 
 ## Executive Summary
 
-- **Test Coverage**: X% (target: Y%)
+- **Test Coverage**: X% (goal: Y%)
 - **Code Quality**: ✅ / ⚠️ / ❌
 - **Performance**: ✅ / ⚠️ / ❌
 - **Technical Debt**: Low / Medium / High
@@ -210,7 +247,7 @@ Create `./.sessions/<ISSUE-ID>/metrics.md`:
 
 ## Approval for Merge
 
-- [ ] Test coverage >= target
+- [ ] Test coverage >= goal
 - [ ] No critical quality issues
 - [ ] Performance within requirements
 - [ ] Technical debt documented and approved
@@ -229,18 +266,18 @@ If the project has goals defined in metaspecs, validate:
 - **Performance**: < 100ms
 
 ### Status
-- Coverage: ✅ 85% (target: 80%)
-- Complexity: ⚠️ 12 (target: 10) - Justified
-- Performance: ✅ 85ms (target: 100ms)
+- Coverage: ✅ 85% (goal: 80%)
+- Complexity: ⚠️ 12 (goal: 10) - Justified
+- Performance: ✅ 85ms (goal: 100ms)
 ```
 
 ## 🚨 Alerts
 
 If any metric is out of acceptable range:
-1. 🛑 **DOCUMENT** the problem
+1. 🛑 **DOCUMENT** the issue
 2. 💬 **ALERT** the user
 3. 🔧 **PROPOSE** corrective actions
-4. ⏸️ **CONSIDER** blocking the merge until resolved
+4. ⏸️ **CONSIDER** blocking the merge until resolution
 
 ---
 
@@ -252,11 +289,11 @@ If any metric is out of acceptable range:
 
 ---
 
-## 🎯 Result
+## 🎯 Outcome
 
 After running this command, you will have:
 - Complete metrics report
 - Comparison with baseline and goals
 - Identification of quality issues
-- Recommended actions
+- Recommendations for actions
 - Objective basis for merge approval

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

@@ -10,11 +10,49 @@ Create a structured record of technical and product decisions, ensuring:
 - **Audit**: Complete history of choices for future review
 - **Learning**: Documentation of trade-offs and alternatives considered
 
-**IMPORTANT**: This command does NOT generate new decisions. It only RECORDS decisions that have already been made during the development process.
+**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.
+
 
 ## 📋 Prerequisites
 
-- You have run at least one of the commands that generate decisions:
+- Have executed at least one of the commands that generate decisions:
   - `/spec` - generates PRD with product decisions
   - `/plan` - generates plan.md with technical decisions
   - `/work` - implementation generates decisions during development
@@ -47,9 +85,9 @@ Analyze the session files (`./.sessions/<ISSUE-ID>/`) to identify decisions:
 - Read `./.sessions/<ISSUE-ID>/work.md`
 - Identify decisions in:
   - Refactorings performed
-  - Changes in approach
-  - Optimizations applied
-  - Handling of edge cases
+  - Approach changes
+  - Applied optimizations
+  - Edge case handling
 
 ### 2. Document Each Decision
 
@@ -145,7 +183,7 @@ For critical decisions, document the impact:
 
 Periodically review the decisions made:
 - Do they still make sense?
-- Were the trade-offs proven correct?
+- Have the trade-offs proven correct?
 - Are there learnings to document?
 - Does any decision need to be reversed?
 

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

@@ -1,34 +1,71 @@
 # Warm-up - Context Loading
 
-This command prepares the environment by loading the complete context of the project and current workspace.
+This command prepares the environment by loading the full context of the current project and workspace.
 
 ## 1. Identify Current Workspace
 
 Check if you are inside a workspace created by `context-cli`:
 
 ```bash
-# Check if you're in a workspace directory
+# Check if you are in a workspace directory
 pwd
-# The workspace is usually at ~/workspaces/<ISSUE-ID>/
+# The workspace is usually located at ~/workspaces/<ISSUE-ID>/
 ```
 
-If you're not in a workspace, ask the user which workspace to use or if you should create a new one with `feature:start`.
+If you are not in a workspace, ask the user which workspace to use or if a new one should be created with `feature:start`.
+
+## 📋 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
+- ✅ Project-specific configurations
+
+**🛑 DO NOT proceed without reading these files!** They contain critical information for the correct execution of the command.
 
 ## 2. Load Project Configuration
 
-You are already in the project's orchestrator (current repository root).
+You are already in the project orchestrator (root of the current repository).
 
-1. **Verify you're at the orchestrator root**: `pwd` should show the orchestrator directory
+1. **Verify you are 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. **Read the `ai.properties.md` file** to obtain local configurations (base_path, etc.)
 
 ## 3. Load Project Manifest
 
 Read the `context-manifest.json` from the orchestrator to understand:
 - Complete list of ecosystem repositories
-- MetaSpecs repository URL
+- URL of the MetaSpecs repository
 - Dependencies between repositories
-- Role of each repository (application, library, service, specs-provider)
+- Roles of each repository (application, library, service, specs-provider)
 
 ## 4. Load MetaSpecs
 
@@ -37,32 +74,32 @@ The MetaSpecs repository is **separate** and defined in `context-manifest.json`
 **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")
+2. Obtain 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}/`
+4. The metaspecs repository is located at: `{base_path}/{metaspecs-id}/`
 
 **Always read the index files first:**
 
 1. **`README.md`** - Project overview and documentation structure
 2. **`index.md`** (in root or subfolders) - Index of available specifications
 
-**Use the indexes as reference** to navigate to the specific specifications you need. Don't assume specific files exist - always consult the indexes first.
+**Use the indexes as a reference** to navigate to the specific specifications you need. Do not assume specific files exist — always consult the indexes first.
 
-## 5. Load Current Session (if exists)
+## 5. Load Current Session (if any)
 
-Check if there's a saved session for this workspace:
+Check if there is a saved session for this workspace:
 
 ```bash
-# Look for session in orchestrator
+# Look for session in the orchestrator
 ls -la .sessions/<ISSUE-ID>/ 2>/dev/null
 ```
 
-If it exists, read the session files to recover the context from the last execution.
+If it exists, read the session files to recover the context of the last execution.
 
 ## 6. Repository Context
 
 For each repository present in the workspace, read:
-- `README.md` - Repository purpose and overview
+- `README.md` - Purpose and overview of the repository
 - Main configuration file (`package.json`, `pom.xml`, `requirements.txt`, etc.)
 
 ## 7. Smart Navigation
@@ -71,7 +108,7 @@ For each repository present in the workspace, read:
 - **Documentation**: Use MetaSpecs indexes as reference
 - **Wait for Instructions**: DO NOT read other files now. Wait for the next command.
 
-## 8. Jidoka Principle (Stop When Detecting Problems)
+## 8. Jidoka Principle (Stop Upon Detecting Problems)
 
 If you detect misalignment, conflicts, or problems:
 1. 🛑 **STOP** immediately
@@ -82,4 +119,4 @@ If you detect misalignment, conflicts, or problems:
 
 **Provided arguments**: #$ARGUMENTS
 
-**Status**: Context loaded. Waiting for next command.
+**Status**: Context loaded. Awaiting next command.