documentation-architect

Design scalable documentation ecosystems with ownership, lifecycle, and cross-linking standards.

Updated May 9, 2026
One-click install
npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill documentation-architect-gustavogutierrez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-architect
Source: https://github.com/GustavoGutierrez/engineering-skills/tree/main/skills/documentation-architect
Command: npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill documentation-architect-gustavogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of documentation fragmentation and poor discoverability by designing a scalable documentation ecosystem with clear structure, ownership, lifecycle rules, and cross-linking.

Core Features & Use Cases

  • Documentation ecosystem architecture: Plan an audience-first information architecture covering onboarding, architecture, operations, ADRs, runbooks, and reference docs.
  • Governance and lifecycle design: Define doc ownership, update triggers, review cadence, and staleness/archiving behavior.
  • Framework-aligned structuring: Integrate documentation patterns for arc42, C4, ADRs, and docs-as-code so the system stays coherent over time.

Quick Start

Use the documentation-architect skill to design your target documentation structure and workflows for onboarding, architecture decisions, and operations.

Frequently Asked Questions about documentation-architect

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

FAQPage Schema
How do I structure a documentation ecosystem for onboarding and architecture overviews?

Structure a documentation ecosystem by defining audience-first entry points, categorizing documents as living, historical, or generated, and establishing cross-linking standards to keep onboarding and architecture overviews navigable and interconnected.

What is docs-as-code governance and how does it keep documentation current?

Docs-as-code governance keeps documentation current by defining explicit document ownership, update triggers, review cadence, and staleness rules to maintain an interconnected, scalable information architecture over time.

How do I organize Architecture Decision Records and runbooks to resolve documentation fragmentation?

Organize ADRs and runbooks to resolve documentation fragmentation by applying an audience-first information architecture that separates living, historical, and generated reference documents with explicit ownership and maintenance workflows.

Can I use documentation architecture patterns with arc42 and C4 framework structuring?

Yes, documentation architecture integrates with framework-aligned structuring patterns like arc42, C4, and ADRs to ensure the documentation system remains coherent and navigable across architecture and operations categories.

What's the best way to design document lifecycle and maintenance workflows for a knowledge management system?

Design document lifecycle workflows by defining explicit update triggers, review cadence, and staleness or archiving behavior, ensuring living, historical, and generated documents remain current within the knowledge management ecosystem.

When should I design a systemic documentation structure instead of writing a single draft?

Design a systemic documentation structure instead of a single draft when facing documentation fragmentation, discoverability gaps, or the need to coordinate onboarding, ADR governance, and runbooks across multiple document categories.