SkillAgentSearch skills...

document-specialist-skill

Claude Code Skill. AI-powered software documentation automation. Professional software documentation specialist. Featuring Progressive Disclosure Architecture. Supports: Design, Requirements, SRS, PRD, API, and architecture docs.

Install / Use

npx skills add SpillwaveSolutions/document-specialist-skill

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Category

Automation

Supported Platforms

Claude Code

Our assessment of document-specialist-skill

document-specialist-skill scores 87/100 on our quality scale, 1639th of 2,863 Automation skills we index.

Its SKILL.md is 18 KB long, well organised into 64 sections with 22 code examples: a thorough specification that gives an agent plenty to work with.

It has 53 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
7/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so document-specialist-skill is actively maintained.
  • Our last check on 2026-10-18 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

document-specialist-skill compared with similar skills

All 4 of these similar skills score higher than document-specialist-skill; compare them before choosing.

SkillScoreStarsUpdatedFormat
document-specialist-skill (this skill)by SpillwaveSolutions8753todaySKILL.md
taste-skillby Leonxlnx100110.6ktodayCLAUDE.md
Agent-Reachby Panniantong100109.2ktodayCLAUDE.md
headroomby headroomlabs-ai10078.9ktodayCLAUDE.md
Scraplingby D4Vinci10097.9ktodayMCP Server

Frequently asked questions

How do I install document-specialist-skill?
Run npx skills add SpillwaveSolutions/document-specialist-skill. The install tabs above show the steps for each supported agent.
Which AI agents does document-specialist-skill work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is document-specialist-skill safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is document-specialist-skill still maintained?
The repository was last updated today, so document-specialist-skill is actively maintained.

Documentation Specialist Skill

Version: 3.3.0 Status: Production Ready (PDA-Compliant) Author: Created with Claude Code Last Updated: 2026-08-29

Transform Claude Code into an expert software documentation specialist with Progressive Disclosure Architecture (PDA) for maximum efficiency.


Installation

One-Click Install via Skilz Marketplace

Install this skill instantly from the Skilz Marketplace:

skilz install SpillwaveSolutions_document-specialist-skill/documentation-specialist

Claude Code plugin

claude plugin marketplace add SpillwaveSolutions/document-specialist-skill
claude plugin install document-specialist

Grok Build plugin

Grok Build loads .claude-plugin/ zero-config. Optional pin:

.grok-plugin/plugin.json
.grok-plugin/marketplace.json

Codex plugin

.codex-plugin/plugin.json with "skills": "./skills/". Enable from the Codex plugin UI, or copy the repo into ~/.codex/plugins/.

Cursor plugin

.cursor-plugin/plugin.json. Optional: point .cursor/rules at SKILL.md.

Universal (Agent Plugins 1.0)

Root plugin.json follows https://agent-plugins.org/schemas/1.0.0/plugin.schema.json. Hosts that only speak Agent Plugins 1.0 load skills/documentation-specialist/SKILL.md.

See docs/HOSTS.md for the four-host matrix.

Manual Installation

Clone directly into your Claude Code skills directory:

# Navigate to your skills directory
cd ~/.claude/skills

# Clone the repository
git clone https://github.com/SpillwaveSolutions/document-specialist-skill.git

Verify Installation

After installation, verify the skill is available:

# List installed skills
ls ~/.claude/skills/document-specialist-skill

# Or ask Claude Code
# "List my installed skills"

Overview

Two Primary Capabilities

  1. Greenfield Documentation: Create professional documentation from templates for new projects
  2. Brownfield Documentation: Reverse-engineer documentation from existing codebases

PDA Architecture (54% Token Reduction)

This skill uses Progressive Disclosure Architecture to minimize token consumption while maintaining full functionality:

  • Core (Auto-loaded): SKILL.md (~2,500 tokens) - Routing, execution logic, and quick start
  • On-demand: Workflow guides, templates, mappings (~10,000 tokens, loaded selectively)

Typical Token Load: 2,500 tokens (just SKILL.md) to 5,000 tokens (with workflow) = 44-72% reduction vs v1.0


Key Features

1. Template-Based Creation (Greenfield)

Create professional documentation from scratch using industry-standard templates:

| Document Type | Standard | Status | Use Case | |---------------|----------|--------|----------| | SRS (Software Requirements Specification) | IEEE 830 | Complete | Formal requirements, compliance, contracts | | PRD (Product Requirements Document) | Agile/Modern | Complete | Feature planning, sprint planning | | SDD (Software Design Document) | arc42 | Complete | Technical design, architecture. Default file is DESIGN_DOC.md | | OpenAPI 3.0 | OpenAPI Spec | Complete | REST API documentation | | Architecture (C4 short) | C4 | Complete | Context, containers, sequence, deployment. Default file is docs/architecture.md | | User Guides | - | Template | End-user documentation | | Deployment Docs | - | Template | DevOps, infrastructure |

2. Code-to-Docs Reverse Engineering (Brownfield)

Automatically generate documentation from existing code:

Backend Frameworks:

  • Spring Boot (Fully mapped) - Controllers to OpenAPI, Entities to ER diagrams, Services to SDD
  • FastAPI, Express.js, Django, Flask (Planned)

Infrastructure:

  • Pulumi (Fully mapped) - Resources to deployment docs, architecture diagrams
  • Terraform, AWS CDK (Planned)

Frontend:

  • React, Next.js, Vue.js (Planned)

Data and CLI:

  • Python ETL, Apache Airflow, CLIs (Planned)

3. Documentation Audit and Quality Control

  • Automated quality checklists (SRS, PRD, SDD, OpenAPI, User Docs)
  • Gap analysis and completeness scoring
  • Best practices validation (IEEE, OpenAPI, WCAG)
  • Improvement recommendations with examples
  • Automated fixes for common issues

4. Multi-Format Output

  • Markdown (Primary format, Git-friendly)
  • DOCX (Microsoft Word via docx skill)
  • PDF (Professional documents via pdf skill)
  • Diagrams (Mermaid, PlantUML via skills)

5. Visual Documentation

Mermaid Diagrams (via design-doc-mermaid skill, default):

  • C4 Model: Context, Container, Component
  • Flowcharts, sequence, class, ER, state

PlantUML Diagrams (via plantuml skill, leftover types only):

  • Salt wireframes / UI mocks
  • Use case, timing, ArchiMate, nwdiag, WBS
  • Always PNG or SVG. GitHub wiki does not render PlantUML source.

Quick Start

Example 1: Create a Requirements Document

Create a Software Requirements Specification for a payment processing system

Generates: IEEE-compliant SRS with functional requirements, NFRs, acceptance criteria

Example 2: Document Existing Spring Boot App

Document my Spring Boot application at ~/projects/ecommerce-api

Generates: SDD (arc42), OpenAPI spec, C4 diagram, ER diagram, Component diagram

Example 3: Audit API Documentation

Audit my OpenAPI specification at docs/api/openapi.yaml

Generates: Audit report with quality score, gap analysis, recommendations

Example 4: Convert to Multiple Formats

Convert docs/requirements/billing-srs.md to Word format

Generates: Professionally styled DOCX with TOC, styles, formatting

Example 5: Generate Architecture Diagrams

Create a C4 container diagram for my e-commerce microservices platform

Generates: C4 container diagram showing services, databases, external systems


Directory Structure (PDA v3.0)

documentation-specialist/
|-- SKILL.md                           # Core routing logic + quick start
|-- plugin.json                        # Agent Plugins 1.0 (universal)
|-- DESIGN_DOC.md                      # arc42 SDD of this skill
|-- README.md                          # This file
|-- USER_GUIDE.md                      # Comprehensive user guide
|-- .claude-plugin/                    # Claude Code plugin + marketplace
|-- .grok-plugin/                      # Grok Build plugin
|-- .codex-plugin/                     # Codex plugin
|-- .cursor-plugin/                    # Cursor plugin
|
|-- references/
|   |-- workflows/                     # On-demand workflow guides
|   |   |-- design-workflow.md        # arc42 DESIGN_DOC.md and C4 architecture.md
|   |   |-- greenfield-workflow.md     # Template-based creation (1,500 tokens)
|   |   |-- brownfield-workflow.md     # Code-to-docs extraction (1,500 tokens)
|   |   |-- audit-workflow.md          # Documentation review (1,000 tokens)
|   |   |-- convert-workflow.md        # Format conversion (750 tokens)
|   |   |-- diagram-workflow.md        # Diagram generation (1,000 tokens)
|   |   |-- user-docs-workflow.md      # User documentation
|   |   |-- tutorial-workflow.md       # Tutorial creation
|   |   |-- runbook-workflow.md        # Operational runbooks
|   |   +-- TOC.md                     # Navigation index
|   |
|   |-- templates/                     # Document templates
|   |   +-- markdown/
|   |       |-- DESIGN_DOC.md         # arc42 SDD (default output name)
|   |       |-- architecture.md        # C4-first short architecture
|   |       |-- requirements-srs.md    # IEEE SRS (600+ lines)
|   |       |-- requirements-prd.md    # Agile PRD (500+ lines)
|   |       |-- api-openapi.yaml       # OpenAPI 3.0 (800+ lines)
|   |       |-- user-manual.md         # User manual template
|   |       |-- howto-guide.md         # How-to guide template
|   |       |-- getting-started.md     # Getting started template
|   |       |-- developer-tutorial.md  # Developer tutorial
|   |       +-- runbook.md             # Runbook template
|   |
|   |-- mappings/                      # Code-to-docs mappings
|   |   +-- backend/
|   |       |-- spring-boot-mapping.yaml  # Complete
|   |       +-- fastapi-mapping.yaml      # Complete
|   |
|   |-- reference/                     # Reference guides
|   |   |-- comprehensive-guide.md     # Navigation to all 27 guides
|   |   +-- 01-philosophy.md           # Docs-as-code principles
|   |
|   +-- examples/                      # Example documentation
|       |-- TOC.md                     # Navigation to all examples
|       |-- greenfield/                # Template-based examples
|       +-- brownfield/                # Code-to-docs examples

How It Works (PDA Flow)

User Request Flow

Example: "Create an SRS for a billing system"

  1. Auto-Load: SKILL.md classifies intent as CREATE_NEW (2,500 tokens)
  2. Selective Load:
    • workflows/greenfield-workflow.md (1,500 tokens)
    • templates/markdown/requirements-srs.md (500 tokens)
  3. Execute: Generate customized SRS
  4. Total Tokens: 4,500 (vs 9,000 in v1.0) = 50% reduction

Intent Classification

The skill automatically classifies your request into one of nine intents:

| Intent | Trigger Keywords | Workflow Loaded | Typical Tokens | |--------|-----------------|----------------|----------------| | DESIGN | "DESIGN_DOC.md", "SDD", "arc42", "architecture document" | design-workflow.md | ~4,200 | | CREATE_NEW | "create", "generate", "write" + doc type | greenfield-workflow.md | ~4,000 | | CODE_TO_DOCS | "document", "extract", path reference | brownfield-workflow.md | ~5,000 | | AUDIT | "audit", "review", "check", "improve" | audit-workflow.md | ~4,000 | | CONVERT | "convert", "transform", "to Word/PDF" | convert-workflow.md | ~3,500 | | DIAGRAM | "diagram", "C4", "sequence", "visualize" | diagram-workflow.md | ~4,200 | | USER_DOCS | "user manual", "how-to", "getting started" | user-docs-workflow.md | ~3,500 | | TUTORIAL | "tutorial", "API guide", "CLI docs" | tutorial-workflow.md | ~3,500 | | RUNBOOK | "runbook", "procedure", "incident" | runbook-workflow.md | ~3,500 |


Integration with Other Skills

This skill seamlessly integrates with other Claude Code skills:

| Skill | Purpose | Auto-Invoked? | Use Case | |-------|---------|---------------|----------| | docx | Word document creation/conversion | Yes when requested | MD to DOCX conversion, professional styling | | pdf | PDF generation | Yes when requested | MD/DOCX to PDF, documentation packages | | design-doc-mermaid | Default diagrams (GitHub-safe) | Yes for C4, sequence, class, ER, state, flowchart | Fenced mermaid in Markdown. Confluence also needs PNG/SVG | | plantuml | Leftover UML + wireframes | Yes for wireframes, use case, timing, ArchiMate | Always PNG or SVG. GitHub wiki does not render PlantUML source |

Auto-invocation: The skill automatically calls these skills when needed, you do not need to invoke them manually.


Documentation Philosophy

This skill follows Docs-as-Code principles:

  1. Living Documentation: Update docs in the same commit as code changes
  2. Minimum Viable Documentation: Small, fresh, accurate docs over large stale docs
  3. The Bonsai Tree Principle: Alive but frequently trimmed
  4. Audience-Specific: Different docs for stakeholders, developers, users
  5. Git-Friendly: Markdown primary format, version controlled with code

Use Cases

Use Case 1: Starting a New Project (Greenfield)

Scenario: Building a new SaaS product, need documentation from day one.

Commands:

1. Create a PRD for a team collaboration platform with real-time messaging
2. Create an SRS for the billing module (high-risk, compliance-critical)
3. Generate an arc42 architecture document 

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars53
CategoryAutomation
Updated8h ago
Forks15

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium