Context
VSDD Factory (drbothen/vsdd-factory) is a Claude Code plugin implementing Verified Spec-Driven Development — a methodology fusing SDD + TDD + VDD into a 7-phase AI-orchestrated pipeline.
Surveyed in kos session-014. This is not a simple sideshow pack candidate (it requires the Claude Code plugin system) but its spec formats and templates are content that sideshow could distribute.
System profile
- Repo: https://github.com/drbothen/vsdd-factory
- Version: 0.10.2
- Type: Claude Code plugin (marketplace-installable)
- Size: 435 files — 43 agents, 91 skills, 47 commands, 108 templates, 15 workflows, 10 hooks
- State directory:
.factory/ in target project (on factory-artifacts orphan branch)
- Fingerprint:
.factory/STATE.md with document_type: pipeline-state frontmatter
What makes this interesting for sideshow
-
4-level spec hierarchy with machine-parseable YAML frontmatter (document_type, level, traces_to, inputs, input-hash, lifecycle_status). Templates define these formats.
-
108 templates defining output formats for every artifact type — behavioral contracts, verification properties, domain specs, stories, architecture sections, convergence reports. These templates are content, distributable independently of the plugin.
-
Traceability chain is explicit: L1 → L2 → L3 → L4 → Story → AC → Test → Implementation → Proof. Declared in frontmatter, not implicit.
-
Lifecycle status (active/deprecated/retired/removed) with cycle version tracking — a deprecation model more formal than most systems.
Sideshow integration considerations
- Currently requires Claude Code plugin infrastructure (hooks.json, SKILL.md, agent definitions) — not just commands
- Commands delegate to skills which reference templates via
${CLAUDE_PLUGIN_ROOT} — path resolution needed
- If sideshow evolves to handle full plugins, VSDD would be a strong candidate
- In the interim, the templates and spec format definitions could be extracted as a standalone content pack
kos bridge profile notes
.factory/ directory is the fingerprint.factory/specs/ contains all knowledge artifacts with parseable frontmattertraces_to and inputs fields could auto-generate kos edgeslifecycle_status maps to kos confidence tier transitions- Orphan branch strategy means scanner may need branch-aware detection
Refs: kos finding-042 (SDD survey), sideshow#9 (umbrella survey), sideshow#14 (bridge profile format)
Context
VSDD Factory (drbothen/vsdd-factory) is a Claude Code plugin implementing Verified Spec-Driven Development — a methodology fusing SDD + TDD + VDD into a 7-phase AI-orchestrated pipeline.
Surveyed in kos session-014. This is not a simple sideshow pack candidate (it requires the Claude Code plugin system) but its spec formats and templates are content that sideshow could distribute.
System profile
.factory/in target project (onfactory-artifactsorphan branch).factory/STATE.mdwithdocument_type: pipeline-statefrontmatterWhat makes this interesting for sideshow
4-level spec hierarchy with machine-parseable YAML frontmatter (document_type, level, traces_to, inputs, input-hash, lifecycle_status). Templates define these formats.
108 templates defining output formats for every artifact type — behavioral contracts, verification properties, domain specs, stories, architecture sections, convergence reports. These templates are content, distributable independently of the plugin.
Traceability chain is explicit: L1 → L2 → L3 → L4 → Story → AC → Test → Implementation → Proof. Declared in frontmatter, not implicit.
Lifecycle status (active/deprecated/retired/removed) with cycle version tracking — a deprecation model more formal than most systems.
Sideshow integration considerations
${CLAUDE_PLUGIN_ROOT}— path resolution neededkos bridge profile notes
.factory/directory is the fingerprint.factory/specs/contains all knowledge artifacts with parseable frontmattertraces_toandinputsfields could auto-generate kos edgeslifecycle_statusmaps to kos confidence tier transitionsRefs: kos finding-042 (SDD survey), sideshow#9 (umbrella survey), sideshow#14 (bridge profile format)