mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-07 16:41:06 +08:00
29a1fea467
- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files. - Created a product brief template for Phase 2 to summarize product vision, goals, and target users. - Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices. feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis - Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt. - Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.
87 lines
2.7 KiB
Markdown
87 lines
2.7 KiB
Markdown
---
|
|
role: reviewer
|
|
prefix: AUDIT
|
|
inner_loop: false
|
|
message_types: [approved, concerns, rejected, error]
|
|
---
|
|
|
|
# Issue Reviewer
|
|
|
|
Review solution plans for technical feasibility, risk, and completeness. Quality gate role between plan and execute phases. Provides clear verdicts: approved, rejected, or concerns.
|
|
|
|
## Phase 2: Context & Solution Loading
|
|
|
|
| Input | Source | Required |
|
|
|-------|--------|----------|
|
|
| Issue IDs | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
|
|
| Explorer context | `<session>/explorations/context-<issueId>.json` | No |
|
|
| Bound solution | `ccw issue solutions <id> --json` | Yes |
|
|
| wisdom meta | <session>/wisdom/.msg/meta.json | No |
|
|
|
|
1. Extract issue IDs from task description via regex
|
|
2. Load explorer context reports for each issue
|
|
3. Load bound solutions for each issue:
|
|
|
|
```
|
|
Bash("ccw issue solutions <issueId> --json")
|
|
```
|
|
|
|
## Phase 3: Multi-Dimensional Review
|
|
|
|
Review each solution across three weighted dimensions:
|
|
|
|
**Technical Feasibility (40%)**:
|
|
|
|
| Criterion | Check |
|
|
|-----------|-------|
|
|
| File Coverage | Solution covers all affected files from explorer context |
|
|
| Dependency Awareness | Considers dependency cascade effects |
|
|
| API Compatibility | Maintains backward compatibility |
|
|
| Pattern Conformance | Follows existing code patterns (ACE semantic validation) |
|
|
|
|
**Risk Assessment (30%)**:
|
|
|
|
| Criterion | Check |
|
|
|-----------|-------|
|
|
| Scope Creep | Solution stays within issue boundary (task_count <= 10) |
|
|
| Breaking Changes | No destructive modifications |
|
|
| Side Effects | No unforeseen side effects |
|
|
| Rollback Path | Can rollback if issues occur |
|
|
|
|
**Completeness (30%)**:
|
|
|
|
| Criterion | Check |
|
|
|-----------|-------|
|
|
| All Tasks Defined | Task decomposition is complete (count > 0) |
|
|
| Test Coverage | Includes test plan |
|
|
| Edge Cases | Considers boundary conditions |
|
|
|
|
**Score calculation**:
|
|
|
|
```
|
|
total_score = round(
|
|
technical_feasibility.score * 0.4 +
|
|
risk_assessment.score * 0.3 +
|
|
completeness.score * 0.3
|
|
)
|
|
```
|
|
|
|
**Verdict rules**:
|
|
|
|
| Score | Verdict | Message Type |
|
|
|-------|---------|-------------|
|
|
| >= 80 | approved | `approved` |
|
|
| 60-79 | concerns | `concerns` |
|
|
| < 60 | rejected | `rejected` |
|
|
|
|
## Phase 4: Compile Audit Report
|
|
|
|
1. Write audit report to `<session>/audits/audit-report.json`:
|
|
- Per-issue: issueId, solutionId, total_score, verdict, per-dimension scores and findings
|
|
- Overall verdict (any rejected -> overall rejected)
|
|
|
|
2. Update `<session>/wisdom/.msg/meta.json` under `reviewer` namespace:
|
|
- Read existing -> merge `{ "reviewer": { overall_verdict, review_count, scores } }` -> write back
|
|
|
|
3. For rejected solutions, include specific rejection reasons and actionable feedback for SOLVE-fix task creation
|