메뉴
Analyze codebase and manage project documentation. Use for doc initialization, updates, summaries, codebase analysis.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Brainstorm solutions with trade-off analysis and brutal honesty. Use for ideation, architecture decisions, technical debates, feature exploration, feasibility assessment, design discussions.
Implement features, plans, and fixes with structured workflow. Use for feature development, plan execution, code implementation pipelines.
Fix bugs with single-agent reasoning loop. Demonstrates Pattern 1: Single Agent Architecture.
Git operations with conventional commits. Use for staging, committing, pushing, PRs, merges. Auto-splits commits by type/scope. Security scans for secrets.
Assess, route, fix, and verify in a loop until tests pass. Demonstrates Pattern 5: Conditional + Loop.
Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.
| 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"} |
Analyze codebase and manage project documentation through scouting, analysis, and structured doc generation.
IMPORTANT: Invoke "/vdt:project-organization" skill to organize the outputs.
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?".
| 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 |
Parse $ARGUMENTS first word:
init → Load references/init-workflow.mdupdate → Load references/update-workflow.mdsummarize → Load references/summarize-workflow.mdinit)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.