mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-05 16:13:08 +08:00
bbdd1840de
- Introduced `document-standards.md` to define YAML frontmatter schema, naming conventions, and content structure for spec-generator outputs. - Created `quality-gates.md` outlining per-phase quality gate criteria and scoring dimensions for spec-generator outputs. - Added templates for architecture documents, epics and stories, product briefs, and requirements PRD to streamline documentation in respective phases.
85 lines
3.0 KiB
Markdown
85 lines
3.0 KiB
Markdown
---
|
|
prefix: SOLVE
|
|
inner_loop: false
|
|
additional_prefixes: [SOLVE-fix]
|
|
additional_members: []
|
|
message_types:
|
|
success: solution_ready
|
|
multi: multi_solution
|
|
error: error
|
|
---
|
|
|
|
# Issue Planner
|
|
|
|
Design solutions and decompose into implementation tasks. Uses CLI tools for ACE exploration and solution generation. For revision tasks (SOLVE-fix), design alternative approaches addressing reviewer feedback.
|
|
|
|
## Phase 2: Context Loading
|
|
|
|
| Input | Source | Required |
|
|
|-------|--------|----------|
|
|
| Issue ID | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
|
|
| Explorer context | `<session>/explorations/context-<issueId>.json` | No |
|
|
| Review feedback | Task description (for SOLVE-fix tasks) | No |
|
|
| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
|
|
|
|
1. Extract issue ID from task description via regex: `(?:GH-\d+|ISS-\d{8}-\d{6})`
|
|
2. If no issue ID found -> report error, STOP
|
|
3. Load explorer context report (if available):
|
|
|
|
```
|
|
Read("<session>/explorations/context-<issueId>.json")
|
|
```
|
|
|
|
4. Check if this is a revision task (SOLVE-fix-N):
|
|
- If yes, extract reviewer feedback from task description
|
|
- Design alternative approach addressing reviewer concerns
|
|
5. Load wisdom files for accumulated codebase knowledge
|
|
|
|
## Phase 3: Solution Generation via CLI
|
|
|
|
**CLI invocation**:
|
|
|
|
```
|
|
Bash("ccw cli -p \"
|
|
PURPOSE: Design solution for issue <issueId> and decompose into implementation tasks; success = solution bound to issue with task breakdown
|
|
|
|
TASK: • Load issue details from ccw issue status • Analyze explorer context • Design solution approach • Break down into implementation tasks • Generate solution JSON • Bind solution to issue
|
|
|
|
MODE: analysis
|
|
|
|
CONTEXT: @**/* | Memory: Issue <issueId> - <issue.title> (Priority: <issue.priority>)
|
|
Explorer findings: <explorerContext.key_findings>
|
|
Relevant files: <explorerContext.relevant_files>
|
|
Complexity: <explorerContext.complexity_assessment>
|
|
|
|
EXPECTED: Solution JSON with: issue_id, solution_id, approach, tasks (ordered list with descriptions), estimated_files, dependencies
|
|
Write to: <session>/solutions/solution-<issueId>.json
|
|
Then bind: ccw issue bind <issueId> <solution_id>
|
|
|
|
CONSTRAINTS: Follow existing patterns | Minimal changes | Address reviewer feedback if SOLVE-fix task
|
|
\" --tool gemini --mode analysis", { run_in_background: true })
|
|
```
|
|
|
|
**Expected CLI output**: Solution file path and binding confirmation
|
|
|
|
**Parse result**:
|
|
|
|
```
|
|
Read("<session>/solutions/solution-<issueId>.json")
|
|
```
|
|
|
|
## Phase 4: Solution Selection & Reporting
|
|
|
|
**Outcome routing**:
|
|
|
|
| Condition | Message Type | Action |
|
|
|-----------|-------------|--------|
|
|
| Single solution auto-bound | `solution_ready` | Report to coordinator |
|
|
| Multiple solutions pending | `multi_solution` | Report for user selection |
|
|
| No solution generated | `error` | Report failure to coordinator |
|
|
|
|
Write solution summary to `<session>/solutions/solution-<issueId>.json`.
|
|
|
|
Update `<session>/wisdom/.msg/meta.json` under `planner` namespace:
|
|
- Read existing -> merge `{ "planner": { issue_id, solution_id, task_count, is_revision } }` -> write back
|