techdocs

# techdocs — Technical Architecture Documentation > **CodeOps Skills Version**: 3.19.0 Create and maintain a living, VitePress-compatible technical architecture documentation set in the project's `docs/` directory, capturing accumulated design knowledge across requirements and planning phases. The body branches by phrasing and arguments: | Phrasing / argument | Mode | Action | |---|---|---| | `make_techdocs`, "document the architecture", "create architecture docs" | **Create / regenerate** | Phases 1–6: comprehensive create or full regeneration | | `make_techdocs --continue` | **Resume** | Pick up an interrupted authoring session (see Session resume) | | `review_techdocs`, "review the techdocs", "health check the docs" | **Health check** | 7-dimension diagnostic report (no file changes) | | *(auto)* exec_plan phase complete | **Incremental** | Add ADRs / update changed sections only | | *(auto)* exec_plan plan complete | **Comprehensive** | Full pass over every section vs. codebase | | *(auto)* make_requirements complete | **Incremental** | New design decisions → ADRs | ## What this is (and is NOT) | In scope — TECHNICAL docs (this skill) | Out of scope — PRODUCT docs | |---|---| | Architecture, design decisions, data models, API contracts, infrastructure, security | End-user guides, tutorials, FAQ, release notes, marketing | | Developer onboarding, dev workflow, deployment procedures | Feature announcements, user-facing changelogs | Product documentation is a separate ...