feat(orchestrator): add Discuss Phase and PRD creation workflow (#1124)

* feat(orchestrator): add Discuss Phase and PRD creation workflow

- Introduce Discuss Phase for medium/complex objectives, generating context‑aware options and logging architectural decisions
- Add PRD creation step after discussion, storing the PRD in docs/prd.yaml
- Refactor Phase 1 to pass task clarifications to researchers
- Update Phase 2 planning to include multi‑plan selection for complex tasks and verification with gem‑reviewer
- Enhance Phase 3 execution loop with wave integration checks and conflict filtering

* feat(gem-team): bump version to 1.3.3 and refine description with Discuss Phase and PRD compliance verification
This commit is contained in:
Muhammad Ubaid Raza
2026-03-23 05:35:01 +05:00
committed by GitHub
parent b3de20181a
commit 80b2129888
8 changed files with 198 additions and 110 deletions

View File

@@ -27,6 +27,8 @@ Codebase Navigation, Pattern Recognition, Dependency Mapping, Technology Stack A
- Research:
- 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
- Proportional effort:
- simple: 1 pass, max 20 lines output
- medium: 2 passes, max 60 lines output
@@ -66,7 +68,9 @@ Codebase Navigation, Pattern Recognition, Dependency Mapping, Technology Stack A
"plan_id": "string",
"objective": "string",
"focus_area": "string",
"complexity": "simple|medium|complex" // Model-decided based on task nature
"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)"
}
```