From vcsdd
Routes adversarial review findings in VCS-DD pipeline to earliest affected phase after FAIL verdict, checks iteration limits per mode, creates feedback beads, and escalates if exceeded.
npx claudepluginhub sc30gsw/vcsdd-claude-code --plugin vcsddThis skill uses the workspace's default tool permissions.
Runs the feedback integration loop (Phase 4). Reads adversary findings from the latest verdict, routes each to the appropriate phase, explicitly enters Phase `4`, and then transitions the pipeline back for rework.
Routes VCSDD adversary findings from verdict.json to earliest affected phases per category/severity table, enforces iteration limits, and triggers escalations to markdown files.
Provides manual feedback in Gran Maestro workflow Phase 4 via /mst:feedback or 'feedback' trigger. Structures input into failure class, evidence, and next actions for routing and agent re-execution.
Verifies phase builds match plans with automated checks against must-haves and interactive UAT walkthroughs. For PBR workflows; supports --auto-fix, --teams, model overrides.
Share bugs, ideas, or general feedback.
Runs the feedback integration loop (Phase 4). Reads adversary findings from the latest verdict, routes each to the appropriate phase, explicitly enters Phase 4, and then transitions the pipeline back for rework.
Run after /vcsdd-adversary returns a FAIL verdict. Normally starts from phase 3; if routing was already started, phase 4 is also valid.
reviews/sprint-N/output/verdict.jsonreviews/sprint-N/output/findings/FIND-NNN.jsonstrict: phase 3 max 5lean: phase 3 max 31a: [FIND-001, FIND-003] <- spec ambiguity
2a: [FIND-002] <- missing test
2b: [FIND-004, FIND-005] <- implementation bug
adversary-finding bead3, transition 3 -> 44, transition to the selected target phaserouteFeedback(featureName, targetPhase, reason) from scripts/lib/vcsdd-state.js instead of hand-rolling transitionPhase() callsrouteFeedback() only proceeds when the latest sprint verdict is FAILdimension controls grading. category controls routing. The routeToPhase field on each finding is authoritative.
| Category | Typical Severity | Route To |
|---|---|---|
spec_ambiguity | any | Phase 1a |
spec_gap | any | Phase 1a |
verification_tool_mismatch | any | Phase 1b |
requirement_mismatch | any | Phase 2b |
missing_edge_case | critical | Phase 1a |
missing_edge_case | high/medium/low | Phase 2a |
test_coverage | any | Phase 2a |
test_quality | any | Phase 2a |
implementation_bug | any | Phase 2b |
error_handling | any | Phase 2b |
security_surface | any | Phase 2b |
code_structure | any | Phase 2c |
naming | any | Phase 2c |
duplication | any | Phase 2c |
proof_gap | any | Phase 5 |
invariant_violation | any | Phase 5 |
purity_boundary | any | Phase 1b by default; Phase 2c or Phase 5 only when the architecture itself remains valid |
/vcsdd-feedback
/vcsdd-feedback --show-routing # display full routing table before applying