Vision Driven Design (VDD) MCP Server
com.ascent-partners/vision-driven-design
Tools
Exactly what the server advertised in the scan completed . Effects and capabilities are classified by Squatch from each tool's metadata. Squatch never runs tools.
- Effect: Read 13
- Effect: Execute 2
Showing 15 of 15 tools
| Details | ||
|---|---|---|
| vdd_clone Crawl and capture a target domain into a clone dataset + manifest — WordPress-aware schema inference, Payload collections, and a Next.js + … | Effect: Execute | |
| vdd_vision VDD Phase 1: Expand a freeform vision statement into vdd/vision.md — Impact Model (Goal, Actors, Impacts), Stakeholder Map, Success Metrics… | Effect: Execute | |
| vdd_amend VDD Cross-phase: Plan a requirement-change cascade through the whole chain — identifies the highest affected level and returns the ordered … | Effect: Read | |
| vdd_clarify VDD Phase 4b: Clarify an existing spec — scans vdd/specs/<feature>/spec.md and returns the items to resolve: every [NEEDS CLARIFICATION] ma… | Effect: Read | |
| vdd_detect_environment VDD Environment Detection: Report which tools/MCPs each VDD phase requires vs treats as optional — across the 8-phase pipeline (init throug… | Effect: Read | |
| 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; … | Effect: Read | |
| vdd_implement VDD Phase 7b: Prepare one task for implementation — loads constitution, spec, plan, and contracts and returns the implementation instructio… | Effect: Read | |
| vdd_init VDD Phase 0: Generate constitution.md at the project root — the immutable tech stack, conventions, security constraints, naming rules, and … | Effect: Read | |
| vdd_inspect VDD Cross-phase: Read-only inspection of the current project in one call — scope selects the view. scope="project" (default) returns the bi… | Effect: Read | |
| vdd_plan VDD Phase 5: Generate the technical blueprint under vdd/specs/<feature>/ — plan.md (component breakdown, AC coverage map, technology choice… | Effect: Read | |
| 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 acce… | Effect: Read | |
| vdd_strategize VDD Phase 2: Produce research-backed strategy into vdd/strategy.md — strategic pillars, competitive analysis, and a risk register, resolved… | Effect: Read | |
| vdd_tactics VDD Phase 3: Audit the existing codebase into vdd/tactics.md — repo audit, technical-debt assessment, gap analysis, MoSCoW-prioritized acti… | Effect: Read | |
| 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 con… | Effect: Read | |
| vdd_validate VDD Phase 8: Validate the full chain — bidirectional traceability matrix, drift detection, orphan detection, uncovered vision goals, impact… | Effect: Read |