Skill

vcsdd-spec

Generates EARS-format behavioral specifications (Phase 1a) and verification architecture with purity boundaries and proof obligations (Phase 1b) for active VCSDD features. Run after /vcsdd-init.

documentation

code-quality

npx claudepluginhub sc30gsw/vcsdd-claude-code --plugin vcsdd

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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.

SKILL.md

Similar Skills

vcsdd-spec-crystallization

Generates EARS-format requirements, purity boundary analysis, edge case enumeration, and spec validation checklists for VCSDD Phase 1a behavioral specifications.

vcsdd

sdd-requirements

Generates EARS-formatted requirements documents for Spec-Driven Development (SDD) workflows. Use for new feature specifications, requirements docs, or acceptance criteria via /sdd-requirements <feature-name>.

sdd-mcp

sdd

Creates, reviews, and manages specification documents for Spec-Driven Development. Provides decision trees, checklists, and 7-phase workflow for formal features requiring stakeholder approval.

1 file5 tools

universal-dev-standards

Stats

Stars16

Forks0

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

What

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, or 1b
Invoke vcsdd-builder agent for Phase 1a:
- Write specs/behavioral-spec.md with EARS requirements
- Cover all functional requirements, edge cases, and non-functional constraints
- Identify purity boundary candidates
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
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