Verified Coherence Spec-Driven Development plugin for Claude Code
npx claudepluginhub sc30gsw/vcsdd-claude-codeVerified Coherence Spec-Driven Development — adversarial quality gates for AI-assisted development
Claude Code marketplace entries for the plugin-safe Antigravity Awesome Skills library and its compatible editorial bundles.
Production-ready workflow orchestration with 79 focused plugins, 184 specialized agents, and 150 skills - optimized for granular installation and minimal token usage
Agent skills for building and maintaining promptfoo evaluations
Share bugs, ideas, or general feedback.
Languages: 日本語
A Claude Code plugin that brings Verified Coherence Spec-Driven Development (VCSDD) methodology to any project. It enforces spec-first, test-first, adversarial review, and formal verification as sequential quality gates.
AI-assisted development has a structural problem: there are no quality gates. Language models produce code that passes surface-level review but routinely harbors spec mismatches, untested edge cases, and structural debt. This is "AI slop" -- code that looks correct but conceals hidden deficiencies.
VCSDD is a methodology that fuses four disciplines into a single workflow:
These are joined by an adversarial review gate: a fresh-context agent running on a more capable model that reviews all artifacts with zero tolerance and produces binary verdicts. The adversary is structurally isolated from the builder -- it reads only from disk and cannot be influenced by the builder's conversational context.
The result is a systematic process for eliminating the gap between "looks correct" and "is correct."
6-phase pipeline Spec Crystallization -> Test-First Implementation -> Adversarial Review -> Feedback Integration -> Formal Hardening -> Convergence. Each phase has explicit prerequisites and produces file artifacts that serve as the handoff to the next phase.
Two operating modes
strict -- full VCSDD ceremony for high-assurance work: sprint contracts, multiple adversary passes, proof obligations, all 6 phases enforcedlean -- all 6 phases remain in place, but approvals, sprint contracts, and proof obligations are lighter for product work and faster iterationThese modes are plugin-specific extensions, not a claim that canonical VCSDD defines two ceremonies. Canonical VCSDD assumes the human Architect signs off on the Phase 1c spec gate; this plugin keeps that as a hard requirement in strict mode and relaxes it in lean mode for faster product iteration.
Fresh-context adversary agent
The adversary (vcsdd-adversary) runs on the Opus model and is always spawned as a new agent instance with zero conversational history from the builder. It reads review artifacts from disk, produces findings, and terminates. It cannot say "overall looks good" -- it must cite concrete evidence for every verdict.
Binary PASS/FAIL verdicts across 5 operational dimensions
These are stable machine-readable buckets for the plugin, not a claim that the original article names these exact five dimensions. In methodology terms they compress the broader Phase 3 concerns: spec fidelity, test quality including edge cases, code quality, security surface, and spec gaps / verification readiness.
Chainlink bead traceability system
Every requirement, test, implementation block, adversary finding, and formal proof is assigned a bead identifier and linked in a directed graph. Any line of code can be traced back to its originating requirement. The full chain is preserved in an append-only history.jsonl audit log.
Completion is blocked if any persisted adversary finding lacks a matching adversary-finding bead.
Gate enforcement via Claude Code hooks
The vcsdd-gate-check.js hook runs on PreToolUse for Write/Edit/MultiEdit and for Bash when the command targets phase-restricted paths. It blocks direct writes, shell redirects, in-place edits, and common path-based mutation commands such as cp into restricted areas. Gate strictness is controlled by the VCSDD_HOOK_PROFILE environment variable.