doc

Guides documentation work through a five-phase audit, plan, draft, review, and verify lifecycle.

10|2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/nrdxp/predicate --skill doc-nrdxp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc
Source: https://github.com/nrdxp/predicate/tree/main/skills/doc
Command: npx skills add https://github.com/nrdxp/predicate --skill doc-nrdxp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large documentation efforts often drift: documents get written without a declared audience or type, existing docs are duplicated or contradicted, and documentation debt goes untracked. This Skill imposes a structured lifecycle so every document is purposeful, accurate, and maintainable. ## Core Features & Use Cases - Five-Phase Lifecycle: Moves work through AUDIT, PLAN, DRAFT, REVIEW, and VERIFY states with explicit transition rules and mandatory human approval gates. - Divio Quadrant Classification: Every deliverable must declare its type (Tutorial, How-To, Reference, or Explanation) and audience before drafting begins. - Documentation Debt Tracking: Audits catalogue existing docs as current, stale, misleading, orphaned, or missing, and record debt items with severity even when out of scope. - Use Case: When restructuring a project's docs, run the workflow to audit all existing pages, produce an approved plan of creates/rewrites/deletes, draft each document, self-review against writing standards, and get human sign-off before finishing. ## Quick Start Ask the agent to run the doc workflow to audit the project's documentation and produce a plan for fixing the documentation debt.

Frequently Asked Questions about doc

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

FAQPage Schema
How do I run a structured documentation audit on my project?

Invoke the doc workflow and start in the AUDIT phase. It catalogues each existing document with its Divio quadrant and currency status (current, stale, misleading, orphaned, or missing), then records documentation debt items with severity before any writing begins.

What is the Divio documentation quadrant system?

The Divio system classifies documents into four types: Tutorial, How-To, Reference, and Explanation. This workflow requires every deliverable to declare exactly one quadrant before drafting, since blending types within a single document fails both audiences.

When should I use the doc workflow versus editing docs directly?

Use the workflow for deliberate documentation work such as new guides, restructures, audits, or debt remediation. For quick inline updates triggered by a code change, apply the underlying documentation writing rules directly without the full lifecycle.

Does the doc workflow require human approval?

Yes, it has mandatory halt points. A human must approve the documentation plan before drafting begins, confirm the final output during VERIFY, and approve a halt if the audit finds no work is needed.

What are the limitations of a documentation lifecycle workflow?

It is not suited for incidental text like commit messages, code comments, or chat responses, and plans, sketches, and ADRs have their own dedicated workflows. The multi-phase process also adds overhead that is unnecessary for single small edits.