techdocs

Generate and maintain technical architecture documentation from requirements and codebase.

4|Updated Jun 22, 2026

Search Tags:#technical documentation #architecture documentation #ADRs #design intent #codebase alignment

Ready to run

npx skills add https://github.com/blendsdk/claude-codeops --skill techdocs-blendsdk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: techdocs
Source: https://github.com/blendsdk/claude-codeops/tree/main/skills/techdocs
Command: npx skills add https://github.com/blendsdk/claude-codeops --skill techdocs-blendsdk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the creation and maintenance of technical architecture documentation, ensuring that design intent remains aligned with code changes and keeping developers informed.

Core Features & Use Cases

Automated Documentation Creation: Generates technical architecture documentation from requirements, plans, and codebase.
Health Checks: Provides a comprehensive review of documentation, including checks for staleness, completeness, and accuracy.
Incremental Updates: Automatically updates documentation as new features are added or existing ones are modified, preserving design intent.

Quick Start

Use the techdocs skill to document the architecture of your project.

Frequently Asked Questions about techdocs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep technical architecture documentation aligned with codebase changes?▼

Technical architecture documentation automation generates, maintains, and reviews docs by analyzing project-specific information, codebase context, and design decisions to ensure completeness, accuracy, and codebase alignment throughout development.

What is the best way to automate ADRs and architecture documentation generation?▼

The best way to automate ADRs and architecture documentation is using tools that generate and incrementally update technical docs from project requirements, plans, and codebase context while preserving design intent.

How do I perform a health check for staleness and completeness on technical documentation?▼

Perform documentation health checks by reviewing technical architecture docs for staleness, completeness, and accuracy, cross-referencing project-specific information and codebase context against recorded design decisions to identify gaps.

Do I need to provide design decision documentation to automate architecture documentation updates?▼

Yes, automating architecture documentation requires project-specific information, codebase context, and design decision documentation to accurately generate, maintain, and review technical docs while preserving design intent.

Can I incrementally update architecture documentation as new features are added without losing design intent?▼

Yes, incremental documentation updates automatically modify technical architecture docs as new features are added or existing ones are changed, preserving original design intent and maintaining codebase alignment.