Hs:docs

Documentation Management

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

IMPORTANT: Invoke the hs:project-organization skill to organize the outputs.

Default (No Arguments)

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

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

Subcommands

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 → ask_user capability (do not auto-run init)

If another workflow needs to decide whether docs should be touched before invoking docs operations, load references/documentation-management.md.

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 /hs:tech-graph's SVG layout rules for component spacing, arrow routing, label placement, and z-index ordering. Pair with /hs:preview --diagram for visual self-review, or use /hs:tech-graph directly for publish-grade output.

IMPORTANT: Do not start implementing code.