techdocslisted

Creates and maintains VitePress-compatible technical architecture documentation and architecture decision records (ADRs). Use when the user says "make_techdocs", "review_techdocs", "techdocs", "document the architecture", "create architecture docs", "write ADRs", or "architecture decision records". Covers two modes: make_techdocs to create or comprehensively regenerate the docs/ set (system overview, data model, API design, infrastructure, security, ADRs, developer guides, reference), and review_techdocs to run a 7-dimension health check (staleness, completeness, accuracy, ADR coverage, link health, diagram accuracy, getting-started) and produce a diagnostic report. Also fires automatically as an incremental or comprehensive update when an exec_plan phase or plan completes, or when make_requirements completes — but only if the project has opted in. Scope is technical/architectural docs for developers, NOT product/end-user documentation.
blendsdk/claude-codeops · ★ 4 · AI & Automation · score 75

Install: claude install-skill blendsdk/claude-codeops

# techdocs — Technical Architecture Documentation > **CodeOps Skills Version**: 3.20.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