Use this skill when running or interpreting VCSDD adversarial reviews. Provides calibration guidance for the Adversary agent, finding severity classification, and anti-leniency enforcement patterns.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
The Adversary MUST:
routeToPhase for actionable routing| Severity | Definition | Examples |
|---|---|---|
| critical | Pipeline cannot continue | Missing spec requirement entirely, security vulnerability |
| high | Significant defect requiring rework | Wrong return type, missing error handling, untested edge case |
| medium | Defect that reduces quality | Misleading name, unnecessary abstraction, dead code |
| low | Improvement opportunity | Style inconsistency, minor duplication |
Watch for these patterns and reject them:
| Category | Meaning | Route To |
|---|---|---|
| spec_ambiguity | Requirement or contract wording is ambiguous | 1a |
| spec_gap | Behavior exists but spec/contract does not cover it | 1a |
| requirement_mismatch | Spec is clear, but tests or implementation do not satisfy it | 2b |
| missing_edge_case | Edge case absent from spec or tests | 1a or 2a |
| test_coverage | Required behavior has no meaningful test | 2a |
| test_quality | Tautological or over-mocked test, or implementation-detail assertion | 2a |
| implementation_bug | Logic defect | 2b |
| error_handling | Incorrect or missing error path | 2b |
| security_surface | Validation/auth/injection issue | 2b |
| code_structure | Cohesion/abstraction/organization issue | 2c |
| naming | Misleading or imprecise names | 2c |
| duplication | Repeated logic that should be unified | 2c |
| proof_gap | Missing proof harness or unverifiable claim | 5 |
| invariant_violation | Proof/testing evidence contradicts required invariant | 5 |
| purity_boundary | Supposedly pure logic still depends on effects | 2c or 5 |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Run Phase 3 (adversarial review) for the active VCSDD feature. Spawns a fresh vcsdd-adversary agent with zero Builder context to review implementation against spec. Produces binary PASS/FAIL verdict per dimension.
日本語の概要は準備中です。原文の説明を表示しています。
Create a git commit for the current VCSDD phase. Auto-generates a conventional commit message from state.json including phase, sprint, gate verdict, and affected bead IDs. Tags with vcsdd/<feature>/phase-<id>.
日本語の概要は準備中です。原文の説明を表示しています。
Run the strict-mode sprint contract review after Phase 2c. Spawns a fresh vcsdd-adversary instance to review `contracts/sprint-N.md` and writes a PASS/FAIL verdict under `reviews/contracts/sprint-N/output/`.
日本語の概要は準備中です。原文の説明を表示しています。
Run Phase 6 (convergence check) for the active VCSDD feature. Validates four-dimensional convergence: finding diminishment, finding specificity, criteria coverage, and duplicate detection.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill during Phase 6 convergence checks. Provides four-dimensional convergence analysis, hallucination detection, and duplicate finding identification.
日本語の概要は準備中です。原文の説明を表示しています。
Architect escalation approval — extend iteration limit for a phase that has hit its cap. Records the approval decision in state and allows the blocked transition to proceed.
日本語の概要は準備中です。原文の説明を表示しています。