document-expert

Audits and updates API docs, READMEs, and architecture documents for consistency.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill document-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-expert
Source: https://github.com/Prathmesh2000/cursor_agent-orchestrator/tree/main/agent-system/skills/document-expert
Command: npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill document-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documenters and engineers often struggle to keep API documentation, READMEs, and architecture notes aligned with evolving code, leading to confusion and maintenance overhead. This skill provides a structured review and generation workflow to audit, update, and harmonize technical documentation across API endpoints, READMEs, and architecture ADRs.

Core Features & Use Cases

  • Review API docs for accuracy, completeness, and illustrative examples.
  • Generate and maintain README, architecture docs, and ADRs with clear rationale and decisions.
  • Enforce documentation templates and quality gates, ensuring versioning and traceability across artifacts.

Quick Start

Run the document-expert skill after feature delivery to audit and generate API docs, READMEs, and architecture decisions.

Frequently Asked Questions about document-expert

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

FAQPage Schema
How do I review API documentation for accuracy and completeness?

To review API documentation, the skill audits API endpoints to identify gaps in accuracy, completeness, and illustrative examples, then proposes corrections to ensure consistency across the resulting artifacts.

What is the best way to maintain architecture decisions and ADRs?

Maintaining architecture decisions and ADRs involves generating structured templates that ensure changes are traceable, versioning is noted, and clear rationale is provided for each architectural choice.

How do I enforce documentation templates and quality gates?

You enforce documentation templates and quality gates by applying structured review workflows that check API docs, READMEs, and architecture notes for versioning compliance and traceability across artifacts.

Can I use this to generate READMEs after feature delivery?

Yes, you can generate and maintain README sections after feature delivery by running a structured audit that ensures accuracy, completeness, and consistency across the resulting technical artifacts.

Does the review workflow handle security and QA documentation?

Yes, the review workflow ensures changes are traceable in ADRs and explicitly covers security and QA documentation requirements to guarantee completeness across all related technical artifacts.