docs-management

Standardize technical documentation creation, review, and publishing with templates and validation.

Updated Apr 20, 2026

Search Tags:#architecture #templates #documentation #validation #adr #runbooks #c4

Ready to run

npx skills add https://github.com/Anders-planck/opencode-config --skill docs-management-anders-planck

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-management
Source: https://github.com/Anders-planck/opencode-config/tree/main/skills/docs-management
Command: npx skills add https://github.com/Anders-planck/opencode-config --skill docs-management-anders-planck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes technical documentation creation, review, and publishing across architecture, ADRs, runbooks, and API docs, ensuring consistency and quality at scale.

Core Features & Use Cases

Enforces a default project structure for docs (docs/ architecture/ adr/ runbooks/ api) and a disciplined naming convention.
Provides templates and guidance for architecture diagrams (C4), ADRs, runbooks, and API documentation, with a clear review and publishing workflow.
Supports a rigorous quality checklist, audience clarity, and traceable ownership for every document.

Quick Start

Create a new documentation package under docs/ following the standard structure and templates, then validate and publish.

Frequently Asked Questions about docs-management

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

FAQPage Schema

How do I standardize technical documentation structure for architecture and runbooks?▼

Standardize technical documentation by enforcing a default docs/ directory structure with dedicated folders for architecture, ADRs, runbooks, and API docs, ensuring consistent layout and quality across projects.

What is an ADR template and when do I need it for architecture decisions?▼

An ADR (Architecture Decision Record) template captures technical decisions, constraints, and consequences. You need it when documenting significant architecture choices to maintain traceable ownership and historical context.

Does this documentation workflow support C4 diagrams and API docs validation?▼

Yes, the workflow supports C4 architecture diagrams and API docs by providing specific templates and enforcing a rigorous quality checklist with validation steps before publishing.

What's the best way to manage a documentation review and publishing workflow?▼

The best way to manage documentation publishing is a structured workflow that moves documents from drafting through quality checklist validation to final publish, ensuring audience clarity and traceable ownership.

Can I apply a consistent naming convention across ADRs, runbooks, and API documentation?▼

Yes, you can enforce a disciplined naming convention across ADRs, runbooks, and API documentation by utilizing the provided templates and standard project structure within the docs/ directory.