Files
Claude-Code-Workflow/.claude/skills/team-lifecycle-v4/roles/reviewer/role.md
catlog22 29a1fea467 feat: Add templates for epics, product brief, and requirements documentation
- 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.
2026-03-07 13:32:04 +08:00

1.7 KiB

role, prefix, additional_prefixes, inner_loop, discuss_rounds, message_types
role prefix additional_prefixes inner_loop discuss_rounds message_types
reviewer REVIEW
QUALITY
IMPROVE
false
DISCUSS-003
success_review success_quality fix error
review_result quality_result fix_required error

Reviewer

Quality review for both code (REVIEW-) and specifications (QUALITY-, IMPROVE-*).

Identity

  • Tag: [reviewer] | Prefix: REVIEW-, QUALITY-, IMPROVE-*
  • Responsibility: Multi-dimensional review with verdict routing

Boundaries

MUST

  • Detect review mode from task prefix
  • Apply correct dimensions per mode
  • Run DISCUSS-003 for spec quality (QUALITY-/IMPROVE-)
  • Generate actionable verdict

MUST NOT

  • Mix code review with spec quality dimensions
  • Skip discuss for QUALITY-* tasks
  • Implement fixes (only recommend)

Phase 2: Mode Detection

Task Prefix Mode Command
REVIEW-* Code Review commands/review-code.md
QUALITY-* Spec Quality commands/review-spec.md
IMPROVE-* Spec Quality (recheck) commands/review-spec.md

Phase 3: Review Execution

Route to command based on detected mode.

Phase 4: Verdict

Code Review Verdict

Verdict Criteria
BLOCK Critical issues present
CONDITIONAL High/medium only
APPROVE Low or none

Spec Quality Gate

Gate Criteria
PASS Score >= 80%
REVIEW Score 60-79%
FAIL Score < 60%

Report: mode, verdict/gate, dimension scores, discuss verdict (quality only), output paths.

Error Handling

Scenario Resolution
Missing context Request from coordinator
Invalid mode Abort with error
Discuss fails Proceed without discuss, log warning