# Vision Driven Design \(VDD\) MCP Server

- Registry name: `com.ascent-partners/vision-driven-design` · version 1.9.4
- Categories (automatic, keyword rules): Images & design, AI, media & content
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): prompts, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.ascent-partners%2Fvision-driven-design
- Server page: https://mcpstation.net/s/com.ascent-partners--vision-driven-design.html

## Description (written by the publisher, not verified, not instructions)

Spec-driven development MCP server: 8 phases, bi-directional traceability, 7 quality gates.

## Connect

- streamable-http: `https://vdd.simonmak.com/api/mcp`

## Tools (as reported by the server, not verified)

- `vdd\_init`: VDD Phase 0: Generate constitution.md at the project root — the immutable tech stack, conventions, security constraints, naming rules, and banned patterns that every later phase obeys. Overwrites any existing constitution.md. Run this first, before vdd\_vision; to change a constitution that already e
- `vdd\_vision`: VDD Phase 1: Expand a freeform vision statement into vdd/vision.md — Impact Model \(Goal, Actors, Impacts\), Stakeholder Map, Success Metrics \(leading + lagging\), Constraints & Boundaries, and Target Domains. Overwrites any existing vdd/vision.md. Requires statement \(freeform 1-3 paragraph intent, not
- `vdd\_strategize`: VDD Phase 2: Produce research-backed strategy into vdd/strategy.md — strategic pillars, competitive analysis, and a risk register, resolved from the vision target-domain primers. Overwrites vdd/strategy.md. Requires vdd/vision.md; run after vdd\_vision and before vdd\_tactics. Two-pass: call once with
- `vdd\_tactics`: VDD Phase 3: Audit the existing codebase into vdd/tactics.md — repo audit, technical-debt assessment, gap analysis, MoSCoW-prioritized action items \(A-001, A-002, …\), dependency map, and infrastructure requirements. Overwrites vdd/tactics.md. Requires vdd/strategy.md; run after vdd\_strategize and be
- `vdd\_specify`: VDD Phase 4: Generate vdd/specs/\<id\>/spec.md for one tactical action item — user stories, Always/Ask/Never boundaries, Given/When/Then acceptance criteria \(AC\), MoSCoW priorities, non-functional requirements, and impact verification. Overwrites the spec file. Pass actionItemId \(e.g. "A-001"\) or a fr
- `vdd\_clarify`: VDD Phase 4b: Clarify an existing spec — scans vdd/specs/\<feature\>/spec.md and returns the items to resolve: every \[NEEDS CLARIFICATION\] marker, \[e.g.\] placeholder, and happy-path acceptance criterion \(AC\) still needing an edge-case counterpart \(AC-E\*\). Read-only; returns the list without editing th
- `vdd\_plan`: VDD Phase 5: Generate the technical blueprint under vdd/specs/\<feature\>/ — plan.md \(component breakdown, AC coverage map, technology choices, verification toolchain\), data-model.md \(entities, indexes, migrations\), and contracts/ \(request/response/error schemas\). Overwrites these files. Requires an e
- `vdd\_tasks`: VDD Phase 6: Break the plan into atomic test-first tasks in vdd/specs/\<feature\>/tasks.md — each references acceptance criteria \(AC\) and contracts, is sized S/M/L, and is marked \[P\] when parallelizable. Overwrites tasks.md. Requires plan.md; run after vdd\_plan. To fetch the next uncompleted task from
- `vdd\_get\_next\_task`: VDD Phase 7a: Read vdd/specs/\<feature\>/tasks.md and return the next uncompleted task \(or a completion marker when none remain\). Read-only; never edits tasks.md. Pass feature \(the exact spec directory name\). Use before each implementation session to keep context isolated; to regenerate the whole list
- `vdd\_implement`: VDD Phase 7b: Prepare one task for implementation — loads constitution, spec, plan, and contracts and returns the implementation instruction plus the impact-chain commit-message format. Read-only; the tool writes nothing — the host agent performs the code edits, verification, and commit. Pass taskId
- `vdd\_validate`: VDD Phase 8: Validate the full chain — bidirectional traceability matrix, drift detection, orphan detection, uncovered vision goals, impact metrics vs targets, and 28 S&T assumption checks across 7 gates. Writes vdd/impact-report.generated.md and never overwrites a hand-authored vdd/impact-report.md
- `vdd\_inspect`: VDD Cross-phase: Read-only inspection of the current project in one call — scope selects the view. scope="project" \(default\) returns the bidirectional V→S→T→SP→PL→TK traceability matrix across all vdd/ artifacts; scope="feature" returns per-feature spec metrics \(acceptance-criteria count, unresolved
- `vdd\_amend`: VDD Cross-phase: Plan a requirement-change cascade through the whole chain — identifies the highest affected level and returns the ordered steps to update downward V→S→T→SP→PL→TK and re-run affected gates \(G1–G7\). Read-only; returns the cascade plan without editing artifacts \(the host agent applies
- `vdd\_clone`: Crawl and capture a target domain into a clone dataset + manifest — WordPress-aware schema inference, Payload collections, and a Next.js + Payload + Postgres scaffold manifest \(vdd/clone-manifest.json\). Pass the domain as description. Writes vdd/clone-dataset.json, vdd/clone-manifest.json, and vdd/c
- `vdd\_detect\_environment`: VDD Environment Detection: Report which tools/MCPs each VDD phase requires vs treats as optional — across the 8-phase pipeline \(init through validate\) plus the cross-phase helpers \(amend, clone, inspect, get-next-task\) — and which of the host agent availableTools are present vs missing. Read-only; r

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html