vdt-docs

name	vdt:docs
description	Analyze codebase and manage project documentation. Use for doc initialization, updates, summaries, codebase analysis.
user-invocable	true
when_to_use	Invoke to create, refresh, or audit project documentation.
category	utilities
keywords	["documentation","init","update","summarize"]
argument-hint	init|update|summarize
metadata	{"author":"vdt-demo","version":"1.2.0"}

Documentation Management

Analyze codebase and manage project documentation through scouting, analysis, and structured doc generation.

IMPORTANT: Invoke "/vdt:project-organization" skill to organize the outputs.

Default (No Arguments)

If invoked without arguments, use AskUserQuestion to present available documentation operations:

Operation	Description
init	Analyze codebase & create initial docs
update	Analyze changes & update docs
summarize	Quick codebase summary

Present as options via AskUserQuestion with header "Documentation Operation", question "What would you like to do?".

Subcommands

Subcommand	Reference	Purpose
/vdt:docs init	references/init-workflow.md	Analyze codebase and create initial documentation
/vdt:docs update	references/update-workflow.md	Analyze codebase and update existing documentation
/vdt:docs summarize	references/summarize-workflow.md	Quick analysis and update of codebase summary

Routing

Parse $ARGUMENTS first word:

• init → Load references/init-workflow.md
• update → Load references/update-workflow.md
• summarize → Load references/summarize-workflow.md
• empty/unclear → AskUserQuestion (do not auto-run init)

Shared Context

Documentation lives in ./docs directory:

./docs
├── project-overview-pdr.md
├── code-standards.md
├── codebase-summary.md
├── design-guidelines.md
├── deployment-guide.md
├── system-architecture.md
└── project-roadmap.md

Use docs/ directory as the source of truth for documentation.

When authoring or refreshing diagrams in system-architecture.md, apply the universal SVG layout rules from /vdt:tech-graph's references/svg-layout-best-practices.md (component spacing, arrow routing, label placement, z-index ordering). Pair with /vdt:preview --diagram for visual self-review, or use /vdt:tech-graph directly for publish-grade output.

IMPORTANT: Do not start implementing code.