skills.rest
ddunnock
ddunnockCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

documentation-architect

Structure Diátaxis-based documentation with source-grounded tutorials, how-tos, references, and explanations.

10|5|Updated Jan 2, 2026
Search Tags:#automation#documentation#source-grounded#guardrails#Diátaxis#documentation-architecture
One-click install
npx skills add https://github.com/ddunnock/claude-plugins --skill documentation-architect-ddunnock
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: documentation-architect
Source: https://github.com/ddunnock/claude-plugins/tree/main/skills/documentation-architect
Command: npx skills add https://github.com/ddunnock/claude-plugins --skill documentation-architect-ddunnock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation teams struggle to convert scattered inputs—specs, ADRs, RFCs, and existing docs—into a coherent, Diátaxis-aligned package that is easy to navigate and maintain.

This Skill provides a repeatable workflow that maps content to Tutorials, How-To, Reference, and Explanation quadrants, while enforcing source grounding across all claims.

It also orchestrates guardrails, memory tracking, and cascade analysis to ensure quality, traceability, and safe progression across release cycles.

Core Features & Use Cases

  • Diátaxis-driven organization: Create complete quadrant coverage (Tutorials, How-To, Reference, Explanation) with clear navigation paths.
  • Source-grounded content: Attach citations to every claim and maintain a central source registry.
  • Lifecycle workflow: Support the end-to-end process (init, inventory, plan, generate, sync, analyze, readme) with idempotent, auditable steps.
  • Guardrails and governance: Enforce phase gates, document review loops, change logging, cascade analysis, and memory persistence.
  • Speckit integration readiness: Seamlessly align with speckit-generated artifacts for development-to-doc workflows.

Quick Start

Use the Documentation Architect to scaffold a Diátaxis-aligned documentation set and keep it synchronized with code and decisions.

  • Run /docs.init to scaffold the docs structure.
  • Run /docs.inventory to register sources.
  • Run /docs.plan to design the WBS.
  • Run /docs.generate to produce initial docs.
  • Run /docs.sync to align docs with code reality.
  • Run /docs.analyze to run a quality audit.
  • Run /docs.readme to manage README/CHANGELOG.

Frequently Asked Questions about documentation-architect

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

FAQPage Schema
How do I convert scattered specs and ADRs into Diátaxis documentation?▼

To convert scattered specs and ADRs into Diátaxis documentation, you can map content into Tutorials, How-To, Reference, and Explanation quadrants. This skill provides a repeatable workflow to structure inputs into a coherent, Diátaxis-aligned package with clear navigation paths.

What is the best way to enforce source grounding across all documentation claims?▼

The best way to enforce source grounding is by attaching citations to every claim and maintaining a central source registry. This documentation architecture enforces source grounding across all claims to ensure traceability and quality across release cycles.

How do I scaffold a Diátaxis documentation set and keep it synchronized with code?▼

You scaffold and synchronize Diátaxis documentation by running a lifecycle workflow: init to scaffold, inventory to register sources, generate to produce docs, and sync to align docs with code reality. This ensures idempotent, auditable progression.

Can I integrate speckit-generated artifacts into my documentation workflow?▼

Yes, you can integrate speckit-generated artifacts into your documentation workflow. This skill provides seamless speckit integration readiness, enabling development-to-doc workflows that align generated artifacts with your Diátaxis documentation structure.

Does Diátaxis documentation architecture support quality audits and cascade analysis?▼

Diátaxis documentation architecture supports quality audits and cascade analysis through enforced guardrails and governance. It orchestrates phase gates, document review loops, change logging, and memory persistence to ensure safe progression across release cycles.

What are the limitations of using a Diátaxis framework for complex product domains?▼

Diátaxis requires strict categorization into Tutorials, How-To, Reference, and Explanation, which can be limiting for overlapping content. However, this architecture supports seamless navigation between quadrants across complex product domains to maintain structure.

Related Skills

Explore More Content & Communication Skills→
qte77qte77
2

generating-tech-spec

Generate MADR/ADR, RFC, and design documents from input topics.

Community
Advanced
0xHoneyJar0xHoneyJar
1

autonomous

Automate Loa workflow governance with guardrails, audits, and trajectory logging.

Official
Advanced
zircotezircote
3

diataxis

Classify documentation into Diátaxis quadrants and generate gap analysis reports.

Community
Advanced
tradecatlabstradecatlabs
199

master-buddhaghosa

Answer Theravāda doctrinal questions with Pali canonical citations and doctrinal boundaries.

Community
Advanced