context-first-cli 2.1.6 → 2.2.1

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:
 

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

@@ -12,6 +12,43 @@ This command validates requirements, decisions, or implementations against the p
 - ❌ **DO NOT modify code**
 - ❌ **DO NOT modify `context.md` or `architecture.md`**
 
+## 📋 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
+   - 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.
+
 ## 🎯 Objective
 
 Ensure alignment with:
@@ -34,7 +71,7 @@ Run this command:
 1. Read `context-manifest.json` from the orchestrator
 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}/
+4. The metaspecs are located at: `{base_path}/{metaspecs-repo-id}/`
 
 ## 🔍 Validation Process
 
@@ -48,7 +85,7 @@ ls -la {base_path}/{metaspecs-repo-id}/
 
 ### 2. Business Validation
 
-If there are business metaspecs (`MetaSpecs repository (business section)`):
+If business metaspecs exist (`MetaSpecs repository (business section)`):
 
 ```markdown
 ## Business Validation
@@ -56,25 +93,25 @@ If there are business metaspecs (`MetaSpecs repository (business section)`):
 ### Product Strategy
 - **File**: `MetaSpecs repository (business section)PRODUCT_STRATEGY.md`
 - **Validation**: [Is this feature aligned with the strategy?]
-- **Status**: ✅ Aligned / ⚠️ Partially / ❌ Not aligned
+- **Status**: ✅ Aligned / ⚠️ Partial / ❌ Misaligned
 - **Notes**: [Observations]
 
 ### Personas
 - **File**: `MetaSpecs repository (business section)CUSTOMER_PERSONAS.md`
 - **Validation**: [Does it meet the correct persona?]
-- **Status**: ✅ Aligned / ⚠️ Partially / ❌ Not aligned
+- **Status**: ✅ Aligned / ⚠️ Partial / ❌ Misaligned
 - **Notes**: [Observations]
 
 ### Metrics
 - **File**: `MetaSpecs repository (business section)PRODUCT_METRICS.md`
 - **Validation**: [Is the success metric documented?]
-- **Status**: ✅ Aligned / ⚠️ Partially / ❌ Not aligned
+- **Status**: ✅ Aligned / ⚠️ Partial / ❌ Misaligned
 - **Notes**: [Observations]
 ```
 
 ### 3. Technical Validation
 
-If there are technical metaspecs (`MetaSpecs repository (technical section)`):
+If technical metaspecs exist (`MetaSpecs repository (technical section)`):
 
 ```markdown
 ## Technical Validation
@@ -128,14 +165,14 @@ If there are technical metaspecs (`MetaSpecs repository (technical section)`):
 
 ### 5. Conflict Identification
 
-If there are conflicts or misalignments:
+If conflicts or misalignments exist:
 
 ```markdown
 ## Identified Conflicts
 
 ### Conflict 1: [Description]
 - **Severity**: Critical / High / Medium / Low
-- **Metaspec**: [File being violated]
+- **Metaspec**: [Violated file]
 - **Description**: [Conflict details]
 - **Recommendation**: [How to resolve]
 
@@ -151,7 +188,7 @@ If there are justified deviations:
 ## Justified Exceptions
 
 ### Exception 1: [Description]
-- **Metaspec**: [File being deviated]
+- **Metaspec**: [Deviated file]
 - **Deviation**: [What is different]
 - **Justification**: [Why it is necessary]
 - **Approval**: [Who approved]
@@ -166,7 +203,7 @@ If there are justified deviations:
 - Use the appropriate MCP to add the report to the issue:
   - Add as a comment on the issue
   - Update labels/tags according to the result (e.g., "validated", "needs-adjustment", "blocked")
-  - If there are critical conflicts, update the issue status
+  - If critical conflicts exist, update the issue status
 - Inform the user: "✅ Validation report added to issue [ID]"
 
 **FALLBACK: Create .md file only if MCP fails**
@@ -212,7 +249,7 @@ If critical conflicts are found:
 2. 📝 **DOCUMENT** all conflicts
 3. 💬 **ALERT** the user and stakeholders
 4. **Via MCP**: Update issue status to "Blocked" or "Requires Adjustments"
-5. 🔄 **ADJUST** the plan/implementation as needed
+5. 🔄 **ADJUST** plan/implementation as needed
 6. ✅ **REVALIDATE** after adjustments
 
 ---

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

@@ -18,20 +18,57 @@ You are a product specialist responsible for collecting and documenting new idea
 
 ---
 
+## 📋 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.
+
 ## Project Context
 
 Before starting, load the context by consulting:
 
-1. **Automatically Locate MetaSpecs**:
+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 at: `{base_path}/{metaspecs-repo-id}/`
+   - The metaspecs are located at: `{base_path}/{metaspecs-repo-id}/`
    - Read the `index.md` files as reference
 
-2. **Project Structure**:
+2. **Project structure**:
    - `context-manifest.json` - List of repositories and their roles
-   - `README.md` of the involved repositories
+   - `README.md` of involved repositories
 
 ## Your Goal
 
@@ -87,14 +124,14 @@ Just ensure the idea is **adequately understood**.
    - Suggested priority
 
 3. **Complexity Assessment and Suggestion to Split**
-   
+
    Before finalizing, assess the issue complexity:
-   
+
    **If the implementation seems large** (> 5 days estimated effort):
    - 🚨 **Suggest splitting into multiple smaller issues**
-   - Explain the rationale for splitting (e.g., "This feature involves 3 distinct areas: authentication, processing, and notification")
+   - Explain the rationale for the split (e.g., "This feature involves 3 distinct areas: authentication, processing, and notification")
    - Propose a **logical** split (by functionality, repository, layer, etc.)
-   - Example of splitting:
+   - Example split:
      ```
      Original Issue: "Complete payment system"
      
@@ -104,7 +141,7 @@ Just ensure the idea is **adequately understood**.
      - FIN-103: Confirmation webhook and notifications (backend + jobs)
      ```
    - **Important**: The final decision is the user's - they can accept the split or keep it as a single issue
-   
+
    **If the user accepts the split**:
    - Create each issue separately using the same process
    - Add cross-references between related issues
@@ -112,10 +149,10 @@ Just ensure the idea is **adequately understood**.
 
 4. **User Approval**
    - Present the draft (or drafts, if split)
-   - Make adjustments based on feedback
+   - Make adjustments according to feedback
    - Obtain final approval
 
-5. **Saving the Issue**
+5. **Issue Saving**
 
    **PRIORITY 1: Use MCP (Model Context Protocol)**
    
@@ -134,8 +171,8 @@ Just ensure the idea is **adequately understood**.
    
    **FALLBACK: Create .md file only if MCP fails**
    
-   If MCP is unavailable or fails:
-   - Create a file at `./.sessions/<ISSUE-ID>/collect.md`
+   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.
    - Include date, type, and full content
    - Inform the user: "⚠️ Issue saved locally in .sessions/ (task manager not available)"
@@ -157,7 +194,7 @@ Just ensure the idea is **adequately understood**.
 
 **For Improvements**:
 - What is working but can be improved?
-- What metric do we want to impact?
+- Which metric do we want to impact?
 - Is it a technical or business optimization?
 
 ---

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

@@ -1,6 +1,6 @@
 # Requirements Refinement
 
-You are a product expert tasked with helping to refine requirements for the project.
+You are a product expert responsible for helping to refine requirements for the project.
 
 ## ⚠️ IMPORTANT: This Command DOES NOT Implement Code
 
@@ -17,6 +17,44 @@ You are a product expert tasked with helping to refine requirements for the proj
 
 ---
 
+## 📋 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.
+
+
 ## Objective
 
 Transform an initial requirement into a refined and validated specification, ready to become a complete PRD.
@@ -26,7 +64,7 @@ Transform an initial requirement into a refined and validated specification, rea
 ### 1. Clarification Phase
 
 Read the initial requirement and ask questions to achieve full clarity about:
-- **Objective**: Why build this?
+- **Goal**: Why build this?
 - **Business Value**: Which metric/persona does it impact?
 - **Scope**: What is included and what is NOT included?
 - **Interactions**: Which existing features/components are affected?
@@ -35,7 +73,7 @@ Keep asking questions until you have complete understanding.
 
 ### 2. Validation Against Metaspecs
 
-**IMPORTANT**: First read `ai.properties.md` to obtain the `base_path`. The indexes should ALREADY be in context (you ran `/warm-up`). Consult the indexes and read ONLY the relevant documents to validate the requirement.
+**IMPORTANT**: First read `ai.properties.md` to get the `base_path`. The indexes should ALREADY be in context (you ran `/warm-up`). Consult the indexes and read ONLY relevant documents to validate the requirement.
 
 **Validation Process**:
 
@@ -61,50 +99,50 @@ Keep asking questions until you have complete understanding.
    - ✅ Follows existing business rules
    - ⚠️ Identify conflicts or violations
 
-**If you identify violations**: 🛑 **STOP** and ask the user for clarification before proceeding (Jidoka Principle).
+**If violations are identified**: 🛑 **STOP** and ask the user for clarification before proceeding (Jidoka Principle).
 
 ### 3. Summary and Approval Phase
 
 Once you have gathered sufficient information and validated against metaspecs, present a structured summary with:
 - **Feature**: Feature name
-- **Objective**: Why build it (1-2 sentences)
+- **Goal**: Why build it (1-2 sentences)
 - **Business Value**: Metric, persona, roadmap phase (consult metaspecs)
-- **Scope**: What it INCLUDES and what it DOES NOT INCLUDE
+- **Scope**: What IS included and what IS NOT included
 - **Affected Components**: List based on current architecture (consult technical metaspecs)
 - **Validation against Metaspecs**: ✅ Approved / ⚠️ Attention needed
 - **Effort Estimate**: Small (< 1 day) / Medium (1-3 days) / Large (3-5 days) / Very Large (> 5 days)
 
-**Complexity Assessment and Suggestion to Break Down**:
+**Complexity Assessment and Suggestion to Split**:
 
-**If the implementation seems large** (> 5 days estimated effort):
-- 🚨 **Suggest breaking into multiple smaller issues**
-- Explain the rationale for the breakdown (e.g., "This feature involves 3 distinct areas that can be implemented independently")
-- Propose a **logical** breakdown based on:
+**If implementation seems large** (> 5 days estimated effort):
+- 🚨 **Suggest splitting into multiple smaller issues**
+- Explain the rationale for splitting (e.g., "This feature involves 3 distinct areas that can be implemented independently")
+- Propose a **logical** split based on:
   - Independent functionalities
   - Different repositories
   - Application layers (backend, frontend, infra)
   - Implementation phases (MVP, improvements, optimizations)
-- Example breakdown:
+- Example split:
   ```
   Original Issue: "Multi-channel notification system"
   
-  Suggested Breakdown:
+  Suggested Split:
   - FIN-201: Queue and worker infrastructure (backend)
   - FIN-202: Email notifications (backend + templates)
   - FIN-203: Push notifications (backend + mobile)
   - FIN-204: Notification preferences (frontend + backend)
   ```
-- **Important**: The final decision is the user's - they may accept the breakdown or keep it as a single issue
+- **Important**: Final decision is the user's - they may accept the split or keep it as a single issue
 
-**If the user accepts the breakdown**:
+**If the user accepts the split**:
 - Document each issue separately
 - Add cross-references between related issues
 - Suggest implementation order if dependencies exist
-- Each broken-down issue must go through the same refinement process
+- Each split issue must go through the same refinement process
 
-Request user approval and incorporate feedback if necessary.
+Request user approval and incorporate feedback if needed.
 
-**Tip**: You may search the codebase or internet before finalizing, if needed.
+**Tip**: You may search the codebase or internet before finalizing, if necessary.
 
 ### 4. Saving the Refined Requirements
 
@@ -131,23 +169,23 @@ Once the user approves, save the requirements:
    - **ALWAYS overwrite** the existing body (do not append)
 
 **Note**:
-- The local backup is ALWAYS saved and complete
+- Local backup is ALWAYS saved and complete
 - If API error occurs, manually verify if the issue was updated in the task manager
 
 **Output Template**:
 
-**IMPORTANT**: The standard template for refined requirements may be documented in the metaspecs repository. Check `{base_path}/{metaspecs-id}/specs/refined/` or similar.
+**IMPORTANT**: The standard template for refined requirements may be documented in the metaspecs repository. Consult `{base_path}/{metaspecs-id}/specs/refined/` or similar.
 
 **FULL Template** (for local backup `.sessions/<ISSUE-ID>/refined.md`):
 - **Metadata**: Issue, ID, Task Manager, Project, Date, Sprint, Priority
 - **🎯 WHY**: Reasons, business value, metric, persona, strategic alignment
 - **📦 WHAT**: Detailed features, affected components, integrations, full negative scope
-- **🔧 HOW**: Stack, coding standards, file structure, dependencies, implementation order, failure modes, performance/cost/UX considerations
+- **🔧 HOW**: Stack, coding patterns, file structure, dependencies, implementation order, failure modes, performance/cost/UX considerations
 - **✅ Validation against Metaspecs**: Consulted documents (business and technical), verified ADRs, validation result
 - **📊 Success Metrics**: Technical, product/UX, acceptance criteria
 - **🔄 Product Impact**: Alignment with objectives, enablers, mitigated risks
 - **⚠️ Known Limitations**: MVP limitations
-- **📝 Implementation Checklist**: Tasks by area (backend, frontend, testing, security, etc.)
+- **📝 Implementation Checklist**: Tasks by area (backend, frontend, tests, security, etc.)
 
 **Task Manager Template**:
 ```markdown
@@ -155,7 +193,7 @@ Once the user approves, save the requirements:
 
 **Sprint X** | **Y days** | **Priority**
 
-## Objective
+## Goal
 [1-2 paragraphs: what it is and why]
 
 ## Scope
@@ -176,12 +214,12 @@ Once the user approves, save the requirements:
 ❌ [item 1] ❌ [item 2] ❌ [item 3]
 
 ## Stack
-[Tech stack summary by area]
+[Tech stack summarized by area]
 
 ## Structure
 [SUMMARIZED file tree - main modules only]
 
-## Failure Modes (To Avoid)
+## Failure Modes (Avoid)
 🔴 [critical 1] 🔴 [critical 2]
 🟡 [medium 1] 🟡 [medium 2]
 
@@ -224,4 +262,4 @@ Once the user approves, save the requirements:
 
 **Example**: `/spec FIN-3`
 
-This command will create a complete PRD (Product Requirements Document) 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/dist/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]