sc30gsw/vcsdd-spec
skills/vcsdd-spec/SKILL.md
Run Phase 1a (behavioral specification) and Phase 1b (verification architecture) for the active VCSDD feature. Invokes vcsdd-builder to write EARS-format requirements and purity boundary analysis.
$ install --global
skillsauthnpx skillsauth add sc30gsw/vcsdd-claude-code vcsdd-specInstall 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:36 PM15.0s1 file scanned
SKILL.md
- name:
- vcsdd-spec
- description:
- Run Phase 1a (behavioral specification) and Phase 1b (verification architecture) for the active VCSDD feature. Invokes vcsdd-builder to write EARS-format requirements and purity boundary analysis.
What
Runs the spec crystallization phases (1a and 1b) for the active feature. Phase 1a produces the behavioral specification using EARS format. Phase 1b produces the verification architecture with purity boundary map and proof obligations.
When
Run immediately after /vcsdd-init. Requires active feature at phase init or 1a.
How
- Check active feature: read
.vcsdd/index.json.activeFeature(mirrored to.vcsdd/active-feature.txt) - Check current phase: must be
init,1a, or1b - Invoke vcsdd-builder agent for Phase 1a:
- Write
specs/behavioral-spec.mdwith EARS requirements - Cover all functional requirements, edge cases, and non-functional constraints
- Identify purity boundary candidates
- Write
- Transition to 1a:
transitionPhase(feature, '1a') - Run Phase 1b for all modes:
- Write
specs/verification-architecture.md - Define proof obligations (PROP-XXX) per requirement
- Assign verification tiers (0-3)
- Map purity boundary explicitly
- Write
- Transition to 1b:
transitionPhase(feature, '1b') - Create traceability beads for each REQ-XXX and PROP-XXX
Lean Mode Behavior
Lean mode still completes both Phase 1a and Phase 1b. The difference is that lean mode typically records fewer required: true proof obligations and does not require strict-mode human approval at the spec gate.
Examples
/vcsdd-spec
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