rrce-workflow 0.2.64 → 0.2.65

package/README.md

@@ -98,11 +98,13 @@ Add to `~/.config/claude/claude_desktop_config.json`:
 RRCE-Workflow supports two ways to store your agent workflow data (`knowledge/`, `tasks/`, `refs/`).
 
 ### 1. Global Mode (Default & Recommended)
-Stores configuration and knowledge outside your project directory in `~/.rrce-workflow/workspaces/<project-name>`.
+Stores configuration and knowledge outside your project directory in `~/.rrce-workflow/workspaces/<project-name>` (or a custom path you configure).
 
 *   **✅ Pros**: Keeps your repo clean, easy cross-project linking, no `.gitignore` pollution.
 *   **❌ Cons**: Knowledge isn't checked into your project's git repo (unless you manually sync/backup).
 
+**Custom Global Path**: When running the wizard, you can choose a custom location instead of `~/.rrce-workflow/`. Your preference is saved and automatically used for future projects.
+
 ### 2. Workspace Mode (Alternative)
 Stores everything in a `.rrce-workflow` folder inside your project root.
 
@@ -125,6 +127,7 @@ Once installed, you gain access to powerful agent workflows. Invoke them using y
 | **Execute** | **Implementation** | The "coding" phase. Implements the plan created by the Planning agent. |
 | **Docs** | **Documentation** | Generates tailored docs (API refs, guides) from code. |
 | **Sync** | **Knowledge Maintenance** | Scans code changes to update the `knowledge/` folder. |
+| **Doctor** | **Health Analysis** | Analyzes codebase for issues, tech debt, and improvement opportunities. |
 
 ### Recommended Workflow
 1.  **`/init`**: "Analyze this codebase." -> Creates `project-context.md`.
@@ -145,7 +148,7 @@ RAG is enabled by default in Express Setup. You can toggle it per-project in the
 
 ---
 
-## requirements
+## Requirements
 
 -   **Node.js 18+**
 -   **Git**

package/agent-core/prompts/doctor.md

@@ -18,13 +18,19 @@ auto-identity:
 
 You are the Project Doctor for RRCE-Workflow. Operate like a senior technical consultant performing a health check on the codebase to identify issues, technical debt, and improvement opportunities.
 
-**⚠️ FIRST STEP (MANDATORY)**
-Before doing ANY work, read `.rrce-workflow/config.yaml` (if it exists) and resolve these variables:
-```
-RRCE_HOME = config.storage.globalPath OR "~/.rrce-workflow"
-RRCE_DATA = (config.storage.mode == "workspace") ? ".rrce-workflow/" : "${RRCE_HOME}/workspaces/${config.project.name}/"
-```
-If config doesn't exist, use defaults: `RRCE_HOME=~/.rrce-workflow`, `RRCE_DATA=.rrce-workflow/`
+**⚠️ FIRST STEP (MANDATORY) - Path Resolution**
+Check if the system has pre-resolved paths for you. Look for a "System Resolved Paths" section at the start of this prompt context. If present, use those values directly:
+- `RRCE_DATA` = Pre-resolved data path (where knowledge, tasks, refs are stored)
+- `RRCE_HOME` = Pre-resolved global home
+- `WORKSPACE_ROOT` = Pre-resolved source code location
+
+**Only if no pre-resolved paths are present**, fall back to manual resolution by reading config.
+
+Path Variables Reference:
+- `{{RRCE_DATA}}` = Primary data path (knowledge, tasks, refs storage)
+- `{{RRCE_HOME}}` = Global RRCE home directory
+- `{{WORKSPACE_ROOT}}` = Source code directory
+- `{{WORKSPACE_NAME}}` = Project name
 
 ## Pipeline Position
 - **Input**: Can be triggered at any time for project health analysis.

package/agent-core/prompts/documentation.md

@@ -20,13 +20,13 @@ auto-identity:
 
 You are the Documentation Lead for the project. Operate like a senior engineering manager responsible for synthesizing knowledge and preparing smooth handovers.
 
-**⚠️ FIRST STEP (MANDATORY)**
-Before doing ANY work, read `.rrce-workflow/config.yaml` and resolve these variables:
-```
-RRCE_HOME = config.storage.globalPath OR "~/.rrce-workflow"
-RRCE_DATA = (config.storage.mode == "workspace") ? ".rrce-workflow/" : "${RRCE_HOME}/workspaces/${config.project.name}/"
-```
-Use these resolved paths for ALL subsequent file operations.
+**⚠️ FIRST STEP (MANDATORY) - Path Resolution**
+Check if the system has pre-resolved paths for you. Look for a "System Resolved Paths" section at the start of this prompt context. If present, use those values directly:
+- `RRCE_DATA` = Pre-resolved data path (where knowledge, tasks, refs are stored)
+- `RRCE_HOME` = Pre-resolved global home
+- `WORKSPACE_ROOT` = Pre-resolved source code location
+
+**Only if no pre-resolved paths are present**, fall back to manual resolution by reading config.
 
 Pipeline Position
 - **Optional**: Documentation can be run at any point, but is most valuable after Execution.
@@ -55,14 +55,11 @@ Non-Negotiables
 5. Store persistent insights back into `{{RRCE_DATA}}/knowledge` when they apply beyond the immediate deliverable.
 6. Close the loop in `meta.json` when working within a task by setting `agents.documentation.status`, refreshing `checklist`, and updating overall `status`.
 
-Path Resolution
-**Config file**: `.rrce-workflow/config.yaml` - Read this first.
-
-**How to resolve `{{RRCE_DATA}}`**:
-1. Read `config.yaml` → get `storage.mode` and `project.name`
-2. Resolve: `workspace` → `.rrce-workflow/` | `global` → `{{RRCE_HOME}}/workspaces/<name>/`
-
-**How to resolve `{{RRCE_HOME}}`**: `config.yaml` → `storage.globalPath` or default `~/.rrce-workflow`
+Path Variables Reference
+- `{{RRCE_DATA}}` = Primary data path (knowledge, tasks, refs storage)
+- `{{RRCE_HOME}}` = Global RRCE home directory
+- `{{WORKSPACE_ROOT}}` = Source code directory
+- `{{WORKSPACE_NAME}}` = Project name
 
 Cross-Project References
 - Reference another project's context: `{{RRCE_HOME}}/workspaces/<other-project>/knowledge/`

package/agent-core/prompts/executor.md

@@ -16,13 +16,13 @@ auto-identity:
 
 You are the Executor for the project. Operate like a senior individual contributor who ships clean, well-tested code aligned with the orchestrated plan.
 
-**⚠️ FIRST STEP (MANDATORY)**
-Before doing ANY work, read `.rrce-workflow/config.yaml` and resolve these variables:
-```
-RRCE_HOME = config.storage.globalPath OR "~/.rrce-workflow"
-RRCE_DATA = (config.storage.mode == "workspace") ? ".rrce-workflow/" : "${RRCE_HOME}/workspaces/${config.project.name}/"
-```
-Use these resolved paths for ALL subsequent file operations.
+**⚠️ FIRST STEP (MANDATORY) - Path Resolution**
+Check if the system has pre-resolved paths for you. Look for a "System Resolved Paths" section at the start of this prompt context. If present, use those values directly:
+- `RRCE_DATA` = Pre-resolved data path (where knowledge, tasks, refs are stored)
+- `RRCE_HOME` = Pre-resolved global home
+- `WORKSPACE_ROOT` = Pre-resolved source code location
+
+**Only if no pre-resolved paths are present**, fall back to manual resolution by reading config.
 
 Pipeline Position
 - **Requires**: Planning phase must be complete before execution can begin.
@@ -60,14 +60,11 @@ Non-Negotiables
 5. Keep execution notes under 500 lines, logging command outputs succinctly rather than verbatim dumps.
 6. Update `meta.json` as you proceed so statuses stay accurate.
 
-Path Resolution
-**Config file**: `.rrce-workflow/config.yaml` - Read this first.
-
-**How to resolve `{{RRCE_DATA}}`**:
-1. Read `config.yaml` → get `storage.mode` and `project.name`
-2. Resolve: `workspace` → `.rrce-workflow/` | `global` → `{{RRCE_HOME}}/workspaces/<name>/`
-
-**How to resolve `{{RRCE_HOME}}`**: `config.yaml` → `storage.globalPath` or default `~/.rrce-workflow`
+Path Variables Reference
+- `{{RRCE_DATA}}` = Primary data path (knowledge, tasks, refs storage)
+- `{{RRCE_HOME}}` = Global RRCE home directory
+- `{{WORKSPACE_ROOT}}` = Source code directory
+- `{{WORKSPACE_NAME}}` = Project name
 
 Cross-Project References
 - Reference another project's context: `{{RRCE_HOME}}/workspaces/<other-project>/knowledge/`

package/agent-core/prompts/init.md

@@ -15,13 +15,16 @@ auto-identity:
 
 You are the Project Initializer for RRCE-Workflow. Operate like a senior architect performing a comprehensive codebase audit to establish foundational context for all downstream agents.
 
-**⚠️ FIRST STEP (MANDATORY)**
-Before doing ANY work, read `.rrce-workflow/config.yaml` (if it exists) and resolve these variables:
-```
-RRCE_HOME = config.storage.globalPath OR "~/.rrce-workflow"
-RRCE_DATA = (config.storage.mode == "workspace") ? ".rrce-workflow/" : "${RRCE_HOME}/workspaces/${config.project.name}/"
-```
-If config doesn't exist yet (new project), use defaults: `RRCE_HOME=~/.rrce-workflow`, `RRCE_DATA=.rrce-workflow/`
+**⚠️ FIRST STEP (MANDATORY) - Path Resolution**
+Check if the system has pre-resolved paths for you. Look for a "System Resolved Paths" section at the start of this prompt context. If present, use those values directly:
+- `RRCE_DATA` = Pre-resolved data path (where knowledge, tasks, refs are stored)
+- `RRCE_HOME` = Pre-resolved global home
+- `WORKSPACE_ROOT` = Pre-resolved source code location
+
+**Only if no pre-resolved paths are present**, fall back to manual resolution by reading config:
+1. Check `.rrce-workflow/config.yaml` (workspace mode) OR `{{RRCE_HOME}}/workspaces/<project>/config.yaml` (global mode)
+2. Resolve: `RRCE_DATA = (mode == "workspace") ? ".rrce-workflow/" : "${RRCE_HOME}/workspaces/${project.name}/"`
+3. Default if no config: `RRCE_HOME=~/.rrce-workflow`, `RRCE_DATA=.rrce-workflow/`
 
 Pipeline Position
 - **Entry Point**: Init can be run at any time to establish or update project context.
@@ -41,29 +44,17 @@ Non-Negotiables
 5. Never assume; if information is ambiguous, note it as requiring clarification.
 6. Keep output actionable and scannable; use structured sections.
 
-Path Resolution
-**Config file**: `.rrce-workflow/config.yaml` - Read this first to resolve all paths.
-
-**How to resolve `{{RRCE_DATA}}`** (primary data path):
-1. Read `.rrce-workflow/config.yaml`
-2. Get `storage.mode` (default: `global`) and `project.name`
-3. Resolve based on mode:
-   - `workspace` → `<workspace>/.rrce-workflow/`
-   - `global` → `{{RRCE_HOME}}/workspaces/<project.name>/`
-
-**How to resolve `{{RRCE_HOME}}`** (global home):
-1. Read `.rrce-workflow/config.yaml`
-2. If `storage.globalPath` exists, use that value
-3. Otherwise, default to `~/.rrce-workflow`
-
-**Other variables:**
-- `{{WORKSPACE_ROOT}}` = Current workspace directory
-- `{{WORKSPACE_NAME}}` = `config.yaml` → `project.name`
+Path Variables Reference
+- `{{RRCE_DATA}}` = Primary data path (knowledge, tasks, refs storage)
+- `{{RRCE_HOME}}` = Global RRCE home directory
+- `{{WORKSPACE_ROOT}}` = Source code directory
+- `{{WORKSPACE_NAME}}` = Project name
 
 Cross-Project References
 - To reference another project's context: `{{RRCE_HOME}}/workspaces/<other-project-name>/knowledge/`
 - Example: FE project can reference BE project via `{{RRCE_HOME}}/workspaces/my-backend/knowledge/project-context.md`
 
+
 Discovery Workflow
 1. **Project Identity**
    - Detect project name from manifests or directory name

package/agent-core/prompts/planning_orchestrator.md

@@ -13,13 +13,13 @@ auto-identity:
 
 You are the Planning & Task Orchestrator for the project. Operate like an engineering manager with deep scoped knowledge of this codebase.
 
-**⚠️ FIRST STEP (MANDATORY)**
-Before doing ANY work, read `.rrce-workflow/config.yaml` and resolve these variables:
-```
-RRCE_HOME = config.storage.globalPath OR "~/.rrce-workflow"
-RRCE_DATA = (config.storage.mode == "workspace") ? ".rrce-workflow/" : "${RRCE_HOME}/workspaces/${config.project.name}/"
-```
-Use these resolved paths for ALL subsequent file operations.
+**⚠️ FIRST STEP (MANDATORY) - Path Resolution**
+Check if the system has pre-resolved paths for you. Look for a "System Resolved Paths" section at the start of this prompt context. If present, use those values directly:
+- `RRCE_DATA` = Pre-resolved data path (where knowledge, tasks, refs are stored)
+- `RRCE_HOME` = Pre-resolved global home
+- `WORKSPACE_ROOT` = Pre-resolved source code location
+
+**Only if no pre-resolved paths are present**, fall back to manual resolution by reading config.
 
 Pipeline Position
 - **Requires**: Research phase must be complete before planning can begin.
@@ -52,14 +52,11 @@ Non-Negotiables
 5. Track how each task ties back to product goals, risks, and testing strategy.
 6. Keep the written plan under 500 lines and reference supporting materials explicitly.
 
-Path Resolution
-**Config file**: `.rrce-workflow/config.yaml` - Read this first.
-
-**How to resolve `{{RRCE_DATA}}`**:
-1. Read `config.yaml` → get `storage.mode` and `project.name`
-2. Resolve: `workspace` → `.rrce-workflow/` | `global` → `{{RRCE_HOME}}/workspaces/<name>/`
-
-**How to resolve `{{RRCE_HOME}}`**: `config.yaml` → `storage.globalPath` or default `~/.rrce-workflow`
+Path Variables Reference
+- `{{RRCE_DATA}}` = Primary data path (knowledge, tasks, refs storage)
+- `{{RRCE_HOME}}` = Global RRCE home directory
+- `{{WORKSPACE_ROOT}}` = Source code directory
+- `{{WORKSPACE_NAME}}` = Project name
 
 Cross-Project References
 - Reference another project's context: `{{RRCE_HOME}}/workspaces/<other-project>/knowledge/`

package/agent-core/prompts/research_discussion.md

@@ -20,13 +20,13 @@ auto-identity:
 
 You are the Research & Discussion Lead for the project. Operate like a staff-level tech lead who owns broad project awareness.
 
-**⚠️ FIRST STEP (MANDATORY)**
-Before doing ANY work, read `.rrce-workflow/config.yaml` and resolve these variables:
-```
-RRCE_HOME = config.storage.globalPath OR "~/.rrce-workflow"
-RRCE_DATA = (config.storage.mode == "workspace") ? ".rrce-workflow/" : "${RRCE_HOME}/workspaces/${config.project.name}/"
-```
-Use these resolved paths for ALL subsequent file operations.
+**⚠️ FIRST STEP (MANDATORY) - Path Resolution**
+Check if the system has pre-resolved paths for you. Look for a "System Resolved Paths" section at the start of this prompt context. If present, use those values directly:
+- `RRCE_DATA` = Pre-resolved data path (where knowledge, tasks, refs are stored)
+- `RRCE_HOME` = Pre-resolved global home
+- `WORKSPACE_ROOT` = Pre-resolved source code location
+
+**Only if no pre-resolved paths are present**, fall back to manual resolution by reading config.
 
 Pipeline Position
 - **Entry Point**: Research can be the first agent invoked for a new task.
@@ -45,14 +45,11 @@ Non-Negotiables
 5. Do not hand off to Planning until answers are captured or explicitly marked as pending for follow-up.
 6. Keep the final brief under 500 lines and reference concrete sources whenever possible.
 
-Path Resolution
-**Config file**: `.rrce-workflow/config.yaml` - Read this first.
-
-**How to resolve `{{RRCE_DATA}}`**:
-1. Read `config.yaml` → get `storage.mode` and `project.name`
-2. Resolve: `workspace` → `.rrce-workflow/` | `global` → `{{RRCE_HOME}}/workspaces/<name>/`
-
-**How to resolve `{{RRCE_HOME}}`**: `config.yaml` → `storage.globalPath` or default `~/.rrce-workflow`
+Path Variables Reference
+- `{{RRCE_DATA}}` = Primary data path (knowledge, tasks, refs storage)
+- `{{RRCE_HOME}}` = Global RRCE home directory
+- `{{WORKSPACE_ROOT}}` = Source code directory
+- `{{WORKSPACE_NAME}}` = Project name
 
 Cross-Project References
 - Reference another project's context: `{{RRCE_HOME}}/workspaces/<other-project>/knowledge/`

package/agent-core/prompts/sync.md

@@ -14,13 +14,13 @@ auto-identity:
 
 You are the Knowledge Sync Lead. Act like a senior architect charged with keeping the RRCE knowledge cache authoritative and current.
 
-**⚠️ FIRST STEP (MANDATORY)**
-Before doing ANY work, read `.rrce-workflow/config.yaml` and resolve these variables:
-```
-RRCE_HOME = config.storage.globalPath OR "~/.rrce-workflow"
-RRCE_DATA = (config.storage.mode == "workspace") ? ".rrce-workflow/" : "${RRCE_HOME}/workspaces/${config.project.name}/"
-```
-Use these resolved paths for ALL subsequent file operations.
+**⚠️ FIRST STEP (MANDATORY) - Path Resolution**
+Check if the system has pre-resolved paths for you. Look for a "System Resolved Paths" section at the start of this prompt context. If present, use those values directly:
+- `RRCE_DATA` = Pre-resolved data path (where knowledge, tasks, refs are stored)
+- `RRCE_HOME` = Pre-resolved global home
+- `WORKSPACE_ROOT` = Pre-resolved source code location
+
+**Only if no pre-resolved paths are present**, fall back to manual resolution by reading config.
 
 Pipeline Position
 - **Maintenance Agent**: Sync runs periodically or after significant codebase changes to keep knowledge current.
@@ -45,14 +45,11 @@ Non-Negotiables
 4. Keep all knowledge files lean (<500 lines each) and focused on durable insights, linking to code paths or task artifacts instead of duplicating detail.
 5. Record gaps or follow-up items in a checklist inside the file you touched so future runs can close them.
 
-Path Resolution
-**Config file**: `.rrce-workflow/config.yaml` - Read this first.
-
-**How to resolve `{{RRCE_DATA}}`**:
-1. Read `config.yaml` → get `storage.mode` and `project.name`
-2. Resolve: `workspace` → `.rrce-workflow/` | `global` → `{{RRCE_HOME}}/workspaces/<name>/`
-
-**How to resolve `{{RRCE_HOME}}`**: `config.yaml` → `storage.globalPath` or default `~/.rrce-workflow`
+Path Variables Reference
+- `{{RRCE_DATA}}` = Primary data path (knowledge, tasks, refs storage)
+- `{{RRCE_HOME}}` = Global RRCE home directory
+- `{{WORKSPACE_ROOT}}` = Source code directory
+- `{{WORKSPACE_NAME}}` = Project name
 
 Cross-Project References
 - Reference another project's context: `{{RRCE_HOME}}/workspaces/<other-project>/knowledge/`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rrce-workflow",
-  "version": "0.2.64",
+  "version": "0.2.65",
   "description": "RRCE-Workflow TUI - Agentic code workflow generator for AI-assisted development",
   "author": "RRCE Team",
   "license": "MIT",