Vision Driven Design (VDD) MCP Server changelog

https://vdd.simonmak.com/llms.txt

+ ## MCP prompts (21)+ - Project flow: `start_vdd_project`, `implement_next_task`, `change_requirement`+ - Per phase: `init`, `vision`, `strategize`, `tactics`, `specify`, `clarify`, `plan`, `tasks`, `get-next-task`, `implement`, `validate`+ - Cross-phase: `inspect`, `trace`, `analyze`, `amend`, `detect-environment`, `clone`, `e2e`+ - Clients surface these as `/vdd:<name>`. Published npm `1.9.5` predates them: `npx -y @simonmak-ascent/mcp` serves only the three project-flow prompts, while the hosted endpoint and the repository serve all 21.

• + init
• + vision
• + strategize
• + tactics
• + specify
• + clarify
• + plan
• + tasks
• + get-next-task
• + implement
• + validate
• + inspect
• + trace
• + analyze
• + amend
• + detect-environment
• + clone
• + e2e

https://vdd.simonmak.com/llms.txt

− - Official MCP Registry name: `io.github.simonmak-ascent/vision-driven-design`+ - Official MCP Registry name: `com.ascent-partners/vision-driven-design`

file

published → removed

https://raw.githubusercontent.com/simonmak-ascent/vision-driven-design/HEAD/AGENTS.md

− # AGENTS.md — Vision Driven Design Skill− This is an **OpenCode AI skill repository** — primarily static documentation with a thin MCP API layer.− ## Directory Map− ```− SKILL.md                 ← Entry point loaded by OpenCode.− README.md                ← GitHub landing page.− constitution.md          ← Project constitution (dogfooded).− index.html               ← GitHub Pages landing page at simonmak-ascent.github.io/vision-driven-design.− api/                     ← Vercel MCP endpoint (deployed at vdd.simonmak.com).−   mcp.js                 ← Streamable HTTP MCP endpoint — POST handles JSON-RPC 2.0 (initialize, tools/list, tools/call); GET serves the browser docs page. 15 tools.−   _vdd-rpc.js            ← Shared JSON-RPC core + browser docs page (underscore = not a Vercel route).− vercel.json              ← Vercel deploy config (Framework: Other).− Dockerfile               ← Self-host build — Streamable HTTP MCP server. (Glama generates its own; it ignores this file.)− glama.json               ← Glama registry file — `maintainers` only (the sole field Glama's schema consumes).− server.json              ← Official MCP Registry manifest (`io.github.simonmak-ascent/vision-driven-design`).− package.json             ← Root workspace + Vercel runtime config.− pnpm-workspace.yaml      ← Monorepo workspace config.− packages/                ← TypeScript monorepo.−   vdd-engine/            ← Shared core: 18 phase functions (incl. e2e) + Zod types.−   vdd-mcp/               ← MCP server: 15 tools, stdio + Streamable HTTP transports.−   vdd-cli/               ← CLI binary: 17 subcommands (incl. e2e), --json mode.− domain-primers/           ← 7 domain research patterns (loaded during Phase 2).−   webapp.md, data-storage.md, etl.md, infrastructure.md  ← Conditional (per vision targets).−   human-factors.md, verification-toolchain.md             ← Unconditional (always loaded).−   safety-critical.md                                      ← FMEA/FTA, DO-178C/IEC 62304.− references/               ← 10 authoritative reference docs.−   INDEX.md                ← Navigation map.−   workflow-phases.md      ← Phase order (authoritative).−   artifact-templates.md   ← 11 artifact templates (authoritative).−   prompt-patterns.md      ← AI prompts (authoritative).−   quality-gates.md        ← 7 gates + 108 checks (authoritative).−   ai-agent-patterns.md    ← Agent orchestration (authoritative).−   anti-patterns.md        ← 24 failure modes (authoritative).−   traceability-matrix.md  ← RTM format + CI/CD.−   quick-reference.md      ← Derived cheat sheet.−   compliance-evidence.md  ← DO-178C/IEC 62304/CMMI/ISO 29148 evidence maps.− scripts/                  ← 4 installer/helper scripts.− ```− ## File Roles — Authoritative Sources− Each concept has one canonical source. Update the source, then propagate.

https://vdd.simonmak.com/llms.txt

+ - Hosted mode is stateless with no filesystem: artifact phases return `persisted:false` + `writeTargets` for the agent to write, and filesystem-dependent tools (tactics/clarify/get-next-task/inspect/validate/implement) return a `delegation` envelope — re-call the same tool with `artifactFiles` (and `codebaseAudit` for tactics) for the real result, or use the local stdio server.