From vcsdd
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.
npx claudepluginhub sc30gsw/vcsdd-claude-code --plugin vcsddThis skill uses the workspace's default tool permissions.
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.
Generates EARS-format requirements, purity boundary analysis, edge case enumeration, and spec validation checklists for VCSDD Phase 1a behavioral specifications.
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>.
Creates, reviews, and manages specification documents for Spec-Driven Development. Provides decision trees, checklists, and 7-phase workflow for formal features requiring stakeholder approval.
Share bugs, ideas, or general feedback.
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.
Run immediately after /vcsdd-init. Requires active feature at phase init or 1a.
.vcsdd/index.json.activeFeature (mirrored to .vcsdd/active-feature.txt)init, 1a, or 1bspecs/behavioral-spec.md with EARS requirementstransitionPhase(feature, '1a')specs/verification-architecture.mdtransitionPhase(feature, '1b')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.
/vcsdd-spec