Vision Driven Design
MCP server by Simon Mak · mcp
Vision Driven Design (VDD): an 8-phase, spec-driven development methodology with bi-directional traceability. Start with vdd_init, then vdd_vision (pass a freeform statement). Before each implementation session call vdd_get_next_task. Read-only tools that write nothing are vdd_inspect, vdd_detect_environment, vdd_get_next_task, vdd_clarify, vdd_implement, and vdd_amend; other write tools overwrite their target artifacts unless their description says otherwise (vdd_validate writes only a new vdd/impact-report.generated.md without clobbering a hand-authored report). For a guided run, use the prompts start_vdd_project, init, vision, strategize, tactics, specify, clarify, plan, tasks, get-next-task, implement, validate, inspect, trace, analyze, amend, detect-environment, clone, e2e, implement_next_task or change_requirement.
Endpoint: https://vdd.simonmak.com/api/mcp
Verification: observed. Source: crawl.
Capabilities (36)
- vdd_init
- vdd_vision
- vdd_strategize
- vdd_tactics
- vdd_specify
- vdd_clarify
- vdd_plan
- vdd_tasks
- vdd_get_next_task
- vdd_implement
- vdd_validate
- vdd_inspect
- vdd_amend
- vdd_clone
- vdd_detect_environment
- start_vdd_project
- implement_next_task
- change_requirement
- init
- vision
- strategize
- tactics
- specify
- clarify
- plan