refactor: rename prd_path to project_prd_path in agent configurations

- Updated gem-orchestrator.agent.md to use `project_prd_path` instead of `prd_path` in task definitions and delegation logic.
- Updated gem-planner.agent.md to reference `project_prd_path` and clarify PRD reading.
- Updated gem-researcher.agent.md to use `project_prd_path` and adjust PRD consumption logic.
- Applied minor wording improvements and consistency fixes across the orchestrator, planner, and researcher documentation.

Author: mubaidr

agents/gem-orchestrator.agent.md

@@ -38,7 +38,7 @@ gem-researcher, gem-planner, gem-implementer, gem-browser-tester, gem-devops, ge
     - IF task-specific (current scope only) → include in task_definition for planner
   - Skip entirely for simple complexity or if user explicitly says "skip discussion"
 - PRD Creation (after Discuss Phase):
-  - Use task_clarifications and architectural_decisions from `Discuss Phase`
+  - Use `task_clarifications` and architectural_decisions from `Discuss Phase`
   - Create docs/PRD.yaml (or update if exists) per <prd_format_guide>
   - Include: user stories, IN SCOPE, OUT OF SCOPE, acceptance criteria, NEEDS CLARIFICATION
   - PRD is the source of truth for research and planning
@@ -47,7 +47,7 @@ gem-researcher, gem-planner, gem-implementer, gem-browser-tester, gem-devops, ge
     - simple: well-known patterns, clear objective, low risk
     - medium: some unknowns, moderate scope
     - complex: unfamiliar domain, security-critical, high integration risk
-  - Pass task_clarifications and prd_path to researchers
+  - Pass `task_clarifications` and `project_prd_path` to researchers
   - Identify multiple domains/ focus areas from user_request or user_feedback
   - For each focus area, delegate to `gem-researcher` via `runSubagent` (up to 4 concurrent) per `<delegation_protocol>`
 - Phase 2: Planning
@@ -101,7 +101,7 @@ gem-researcher, gem-planner, gem-implementer, gem-browser-tester, gem-devops, ge
     "focus_area": "string (optional)",
     "complexity": "simple|medium|complex",
     "task_clarifications": "array of {question, answer} (empty if skipped)",
-    "prd_path": "string"
+    "project_prd_path": "string"
   },
 
   "gem-planner": {
@@ -110,7 +110,7 @@ gem-researcher, gem-planner, gem-implementer, gem-browser-tester, gem-devops, ge
     "objective": "string",
     "complexity": "simple|medium|complex",
     "task_clarifications": "array of {question, answer} (empty if skipped)",
-    "prd_path": "string"
+    "project_prd_path": "string"
   },
 
   "gem-implementer": {

agents/gem-planner.agent.md

@@ -31,7 +31,7 @@ gem-researcher, gem-planner, gem-implementer, gem-browser-tester, gem-devops, ge
 - Analyze: Parse user_request → objective. Find `research_findings_*.yaml` via glob.
   - Read efficiently: tldr + metadata first, detailed sections as needed
   - SELECTIVE RESEARCH CONSUMPTION: Read tldr + research_metadata.confidence + open_questions first (≈30 lines). Target-read specific sections (files_analyzed, patterns_found, related_architecture) ONLY for gaps identified in open_questions. Do NOT consume full research files - ETH Zurich shows full context hurts performance.
-  - READ PRD (`prd_path`): Read user_stories, scope (in_scope/out_of_scope), acceptance_criteria, needs_clarification. These are the source of truth — plan must satisfy all acceptance_criteria, stay within in_scope, exclude out_of_scope.
+  - READ PRD (`project_prd_path`): Read user_stories, scope (in_scope/out_of_scope), acceptance_criteria, needs_clarification. These are the source of truth — plan must satisfy all acceptance_criteria, stay within in_scope, exclude out_of_scope.
   - APPLY TASK CLARIFICATIONS: If task_clarifications is non-empty, read and lock these decisions into the DAG design. Task-specific clarifications become constraints on task descriptions and acceptance criteria. Do NOT re-question these — they are resolved.
   - initial: no `plan.yaml` → create new
   - replan: failure flag OR objective changed → rebuild DAG
@@ -70,7 +70,7 @@ gem-researcher, gem-planner, gem-implementer, gem-browser-tester, gem-devops, ge
   "objective": "string", // Extracted objective from user request or task_definition
   "complexity": "simple|medium|complex", // Required for pre-mortem logic
   "task_clarifications": "array of {question, answer} from Discuss Phase (empty if skipped)",
-  "prd_path": "string (path to docs/PRD.yaml)"
+  "project_prd_path": "string (path to docs/PRD.yaml)"
 }
 ```
 

agents/gem-researcher.agent.md

@@ -29,7 +29,7 @@ Codebase Navigation, Pattern Recognition, Dependency Mapping, Technology Stack A
   - Use complexity from input OR model-decided if not provided
   - Model considers: task nature, domain familiarity, security implications, integration complexity
   - Factor task_clarifications into research scope: look for patterns matching clarified preferences (e.g., if "use cursor pagination" is clarified, search for existing pagination patterns)
-  - Read PRD (prd_path) for scope context: focus on in_scope areas, avoid out_of_scope patterns
+  - Read PRD (`project_prd_path`) for scope context: focus on in_scope areas, avoid out_of_scope patterns
   - Proportional effort:
     - simple: 1 pass, max 20 lines output
     - medium: 2 passes, max 60 lines output
@@ -71,7 +71,7 @@ Codebase Navigation, Pattern Recognition, Dependency Mapping, Technology Stack A
   "focus_area": "string",
   "complexity": "simple|medium|complex",
   "task_clarifications": "array of {question, answer} from Discuss Phase (empty if skipped)",
-  "prd_path": "string (path to `docs/PRD.yaml`, for scope/acceptance criteria context)"
+  "project_prd_path": "string (path to `docs/PRD.yaml`, for scope/acceptance criteria context)"
 }
 ```