vscode-mcp-hook

Maintain the architecture documentation set so it stays a living map of the repo. Use when a feature has just merged, when the user asks to refresh or audit the architecture doc, when a folder is added/moved/renamed, or when a tasks file has a non-empty "Pending arch updates" section. Do NOT use to write new architecture from scratch — for that, draft a spec/plan first.

Spec-driven development workflow. Use whenever the user wants to add, change, or remove behavior — i.e. anything that would normally start with "implement…", "add a feature for…", "change the way X works", "fix the behavior of…". Walks the spec → plan → tasks → implement → arch-update loop, reading and writing files under docs/specs, docs/plans, docs/tasks. Do NOT use for pure refactors with no behavior change, dependency bumps, or typo fixes.

Add, modify, or remove MCP tools in the vscode-mcp-hook extension following the harness engineering pattern. Use when the user asks to add a new MCP tool, remove an existing one, or modify a tool's schema, handler, or documentation.