sc30gsw/vcsdd-feedback
skills/vcsdd-feedback/SKILL.md
Run Phase 4 (feedback routing) after an adversarial review FAIL. Routes adversary findings to the earliest affected phase, checks iteration limits, and escalates to human if limits are exceeded.
$ install --global
skillsauthnpx skillsauth add sc30gsw/vcsdd-claude-code vcsdd-feedbackInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 7:35 PM10.9s1 file scanned
SKILL.md
- name:
- vcsdd-feedback
- description:
- Run Phase 4 (feedback routing) after an adversarial review FAIL. Routes adversary findings to the earliest affected phase, checks iteration limits, and escalates to human if limits are exceeded.
What
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.
When
Run after /vcsdd-adversary returns a FAIL verdict. Normally starts from phase 3; if routing was already started, phase 4 is also valid.
How
- Read latest verdict:
reviews/sprint-N/output/verdict.json - Read all findings:
reviews/sprint-N/output/findings/FIND-NNN.json - Check iteration limits: use mode-aware limits before re-entering adversarial review
strict: phase3max5lean: phase3max3
- Group findings by routeToPhase:
1a: [FIND-001, FIND-003] <- spec ambiguity 2a: [FIND-002] <- missing test 2b: [FIND-004, FIND-005] <- implementation bug - Route to EARLIEST affected phase (route to 1a before 1b before 2a before 2b before 2c before 5)
- runtime validates the current sprint's persisted findings and rejects any target that skips an earlier routed phase
- Create adversary-finding beads for each finding
- completion will later fail if any persisted finding lacks a matching
adversary-findingbead
- completion will later fail if any persisted finding lacks a matching
- Advance through explicit feedback routing:
- if current phase is
3, transition3 -> 4 - from phase
4, transition to the selected target phase - use
routeFeedback(featureName, targetPhase, reason)fromscripts/lib/vcsdd-state.jsinstead of hand-rollingtransitionPhase()calls routeFeedback()only proceeds when the latest sprint verdict isFAIL
- if current phase is
- Display routing summary: "Routing 5 findings. 2 -> Phase 1a, 3 -> Phase 2b"
- Next action: prompt user to run appropriate command for the target phase
Feedback Routing Table
dimension 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 |
Examples
/vcsdd-feedback
/vcsdd-feedback --show-routing # display full routing table before applying
Related Skills
sc30gsw/vcsdd-verification-architecture
documentation
VerifiedTrustedCommunity
Use this skill when writing Phase 1b verification architecture documents. Provides purity boundary mapping, proof obligation design, and tier assignment guidance.
20SKILL.mdUpdated Apr 16, 2026
sc30gsw/vcsdd-traceability
data-ai
VerifiedTrustedCommunity
Use this skill when creating or querying VCSDD Chainlink bead traceability. Provides bead creation patterns, chain traversal, and completeness validation.
20SKILL.mdUpdated Apr 16, 2026
sc30gsw/vcsdd-trace
data-ai
VerifiedTrustedCommunity
Display the full traceability chain for a VCSDD bead. Traverses the Chainlink graph from the given bead ID and shows all connected artifacts with status.
20SKILL.mdUpdated Apr 16, 2026
sc30gsw/vcsdd-tdd
development
VerifiedTrustedCommunity
Run Phase 2a (test generation, Red phase) for the active VCSDD feature. Invokes vcsdd-builder to generate failing tests for all spec requirements. Records red phase evidence.
20SKILL.mdUpdated Apr 16, 2026