doc

Govern steering and project documents with frontmatter-driven templates and drift detection.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/saitoco/wholework --skill doc-saitoco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc
Source: https://github.com/saitoco/wholework/tree/main/skills/doc
Command: npx skills add https://github.com/saitoco/wholework --skill doc-saitoco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and stabilizes steering and project documentation across repositories, ensuring consistency, traceability, and auditable change history.

Core Features & Use Cases

  • Manage Steering Documents and Project Documents from a single, frontmatter-driven workflow.
  • Drift detection, normalization, and auto-generation workflows for init, sync, and translate commands.
  • Support for templates, translation, and scripted updates to align documentation with code.

Quick Start

Run the /doc init wizard to start steering document creation and set the documentation lifecycle in motion.

Frequently Asked Questions about doc

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

FAQPage Schema
How do I detect and fix documentation drift across a repository?▼

Documentation drift is detected by applying frontmatter rules to compare steering and project documents against their templates. The Skill identifies inconsistencies and triggers auto-generated drafts to normalize and update the affected files.

What's the best way to centralize and trace project documentation changes?▼

Centralizing project documentation requires a frontmatter-driven workflow that manages steering documents from a single source. This approach ensures consistency, traceability, and an auditable change history across repositories.

How do I initialize and sync steering documents using frontmatter templates?▼

Initializing and syncing steering documents starts with the init wizard to set the documentation lifecycle. The workflow uses frontmatter-driven templates to apply validation rules and generate consistent project documents.

Can I translate project documentation while maintaining frontmatter rules?▼

Translating project documentation supports frontmatter rules to maintain structure across languages. The workflow normalizes translated content and validates it against steering document templates to ensure consistency.

Do I need frontmatter in my templates to govern documentation workflows?▼

Frontmatter-driven templates are required to govern documentation workflows. The Skill relies on frontmatter rules to initialize, sync, translate, and drift-detect steering and project documents for consistent updates.

Why does documentation drift happen in multi-repository projects?▼

Documentation drift happens when steering and project documents fall out of sync with code changes. Without frontmatter-driven drift detection and validation, repositories lack automated workflows to normalize and auto-update affected drafts.