Organize technical documentation into Diátaxis quadrants with consistent structure and style.
npx skills add https://github.com/kouko/monkey-skills --skill docs-team
Please help me install this Agent Skill. Skill: docs-team Source: https://github.com/kouko/monkey-skills/tree/main/domain-teams/skills/docs-team Command: npx skills add https://github.com/kouko/monkey-skills --skill docs-team
Documentation often drifts across projects, quadrants, and teams. The Docs Team skill establishes a Diátaxis-aligned, style-consistent approach to creating tutorials, how-to guides, references, explanations, READMEs, ADRs, and API docs, ensuring clear ownership and governance.
Write a frontmatter-guided doc task by declaring the mode and owner, then route the request through the doc-writing router.
High-intent search queries and answers about installing and using this skill.
The Diátaxis framework structures technical documentation into four quadrants: tutorials, how-to guides, references, and explanations. Separating content by user intent reduces mode mixing and ensures each doc type maintains a consistent structure and style.
Enforcing docs-as-code governance requires applying frontmatter metadata, style conformance checks, and freshness tracking across READMEs and API references. Treating documentation with the same rigor as source code pipelines ensures clear ownership and maintainability.
Writing a consistent Architecture Decision Record requires enforcing a standardized ADR structure with frontmatter metadata. Applying docs-as-code principles ensures architecture decisions remain clear, governed, and maintainable across cross-team projects.
Yes, the Diátaxis quadrant discipline explicitly separates API reference standards from tutorial content. This prevents mode mixing by keeping strict reference documentation distinct from learning-oriented tutorials, ensuring both maintain their specific structural rules.
Documentation drifts across projects when there is no consistent structural alignment or governance. Without enforcing frontmatter metadata, style conformance, and Diátaxis quadrant discipline, different teams naturally diverge in how they write and maintain their docs.
Yes, you can run a codebase and documentation health audit to check style conformance and freshness. This process validates frontmatter metadata, verifies API reference standards, and ensures all content correctly aligns with its intended Diátaxis quadrant.
labs21-devRoute ambiguous sales requests to the narrowest applicable child skill.
lagz0neAudit C3 architecture documentation against the actual codebase.
fgrehmAutomate pre-publish checks for blog posts with Python scripts and WebSearch integrations.
zircoteClassify documentation into Diátaxis quadrants and generate gap analysis reports.
