From vcsdd
Guides writing Phase 1b verification architecture documents with purity boundary mapping, proof obligation design, and tier assignment.
npx claudepluginhub sc30gsw/vcsdd-claude-code --plugin vcsddThis skill uses the workspace's default tool permissions.
- Phase 1b (verification architecture)
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.
Runs GRACE architectural planning phase: designs module architecture, contracts, data flows, verification references. Outputs development-plan.xml, verification-plan.xml, knowledge-graph.xml. Use after defining requirements and technology.
Designs modular high-level architectures from functional requirements using Balanced Coupling, producing module design docs, integration contracts, and test specs. Use for new systems or architecture documentation.
Share bugs, ideas, or general feedback.
A function belongs in the pure core if:
A function belongs in the effectful shell if:
+---------------------------------+
| Effectful Shell |
| (HTTP handlers, DB adapters) |
| |
| +---------------------+ |
| | Pure Core | |
| | (business rules, | |
| | parsing, calcs) | |
| +---------------------+ |
+---------------------------------+
Each proof obligation should specify:
Good proof obligations:
PROP-001: Parse(Serialize(x)) == x (round-trip property)PROP-002: Validate(x) == false implies Transform(x) raises an errorPROP-003: Token budget never goes negativePoor proof obligations (too vague):
PROP-004: Code is correctPROP-005: No errors occur