Files
Claude-Code-Workflow/.claude/skills/team-roadmap-dev/role-specs/verifier.md
catlog22 26bda9c634 feat: Add coordinator commands and role specifications for UI design team
- Implemented the 'monitor' command for coordinator role to handle monitoring events, task completion, and pipeline management.
- Created role specifications for the coordinator, detailing responsibilities, command execution protocols, and session management.
- Added role specifications for the analyst, discussant, explorer, and synthesizer in the ultra-analyze skill, defining their context loading, analysis, and synthesis processes.
2026-03-03 23:35:41 +08:00

2.0 KiB

prefix, inner_loop, subagents, message_types
prefix inner_loop subagents message_types
VERIFY true
success failure error
verify_passed gaps_found error

Verifier

Goal-backward verification per phase. Reads convergence criteria from IMPL-*.json task files and checks against actual codebase state. Read-only — never modifies code. Produces verification.md with pass/fail and structured gap lists.

Phase 2: Context Loading

Input Source Required
Task JSONs /phase-{N}/.task/IMPL-*.json Yes
Summaries /phase-{N}/summary-*.md Yes
Wisdom /wisdom/ No
  1. Glob IMPL-*.json files, extract convergence criteria from each task
  2. Glob summary-*.md files, parse frontmatter (task, affects, provides)
  3. If no task JSONs or summaries found → error to coordinator

Phase 3: Goal-Backward Verification

For each task's convergence criteria, execute appropriate check:

Criteria Type Method
File existence test -f <path>
Command execution Run command, check exit code
Pattern match Grep for pattern in specified files
Semantic check Optional: Gemini CLI (--mode analysis --rule analysis-review-code-quality)

Per task scoring:

Result Condition
pass All criteria met
partial Some criteria met
fail No criteria met or critical check failed

Collect all gaps from partial/failed tasks with structured format:

  • task ID, criteria type, expected value, actual value

Phase 4: Compile Results

  1. Aggregate per-task results: count passed, partial, failed
  2. Determine overall status:
    • passed if gaps.length === 0
    • gaps_found otherwise
  3. Write <session>/phase-{N}/verification.md:
---
phase: <N>
status: passed | gaps_found
tasks_checked: <count>
tasks_passed: <count>
gaps:
  - task: "<task-id>"
    type: "<criteria-type>"
    item: "<description>"
    expected: "<expected>"
    actual: "<actual>"
---
  1. Update .msg/meta.json with verification summary