📚 Documentation Verification Skill

Orchestrate specialized agents to verify and update the docs/ directory.

Updated Feb 23, 2026

Search Tags:#automation #developer tools #documentation #agent #code sync #skill

Ready to run

npx skills add https://github.com/ITZAN44/clientpro-crm --skill documentation-verification-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: 📚 Documentation Verification Skill
Source: https://github.com/ITZAN44/clientpro-crm/tree/main/.opencode/skills/docs-verification
Command: npx skills add https://github.com/ITZAN44/clientpro-crm --skill documentation-verification-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your project's documentation stays up-to-date with code changes, preventing outdated information and saving developers time on manual updates.

Core Features & Use Cases

Automated Verification: Systematically checks documentation folders (docs/) for necessary updates.
Agent Delegation: Distributes tasks to specialized agents for context, decisions, guides, roadmap, and session reporting.
Selective Updates: Only modifies documentation when changes are significant, errors are critical, or information is obsolete.
Use Case: After completing a development sprint, invoke this skill to automatically update OVERVIEW.md, create new ADRs if architectural decisions were made, and ensure the roadmap reflects completed sub-phases.

Quick Start

Run the /verify-docs command to ensure all project documentation is synchronized with recent code changes.

Frequently Asked Questions about 📚 Documentation Verification Skill

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

FAQPage Schema

How do I keep documentation in sync with code changes automatically?▼

To keep documentation in sync with code changes, you can run the /verify-docs command to systematically verify and update your `docs/` directory based on recent development progress.

What is the best way to update architectural decision records after a sprint?▼

The best way to update architectural decision records after a sprint is to use an agent delegation system that automatically verifies code changes and creates new ADRs to ensure documentation accuracy and relevance.

How does automated documentation verification work for development progress?▼

Automated documentation verification works by delegating tasks to specialized agents for context, decisions, guides, roadmap, and session reporting, selectively modifying documentation only when changes are significant or information is obsolete.

Do I need specialized agents to automate documentation updates?▼

Yes, you need specialized agents for context, decisions, guides, roadmap, and session reporting to function, as the system delegates these specific tasks to ensure documentation accuracy and relevance.

When should I not use automated documentation synchronization?▼

You should not use automated documentation synchronization when code changes are minor, as the system selectively modifies documentation only when changes are significant, errors are critical, or information is obsolete.