docs

Generate developer and user docs from pipeline artifacts for GitHub Pages.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/ryanismert/claude-plugin-build --skill docs-ryanismert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/ryanismert/claude-plugin-build/tree/main/skills/docs
Command: npx skills add https://github.com/ryanismert/claude-plugin-build --skill docs-ryanismert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generates comprehensive project documentation by scanning pipeline artifacts (PRD, design doc, implementation report) and the codebase, producing developer docs in docs/ and user docs in public-docs/ for GitHub Pages.

Core Features & Use Cases

  • Artifact discovery and planning: identifies PRD/design/implementation artifacts to model documentation needs.
  • Parallel doc generation: coordinates specialized doc-writer agents to produce developer and user documentation.
  • Accuracy verification: validates generated docs against the codebase and design artifacts to ensure factual correctness.
  • Review-before-commit workflow: presents results for user review before committing to the repository.

Quick Start

Run the documentation build after artifacts are ready to generate both developer and user docs.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I automatically generate project documentation from PRD and design artifacts?

You can automatically generate project documentation by running a build that scans pipeline artifacts like PRDs and design docs alongside the codebase, coordinating parallel doc-writer agents to produce developer and user docs.

How does automated documentation verification work against a codebase?

Automated documentation verification validates generated docs against the codebase and design artifacts to ensure factual correctness, confirming the documentation matches the actual implementation before commit.

Can I generate user docs for GitHub Pages from implementation reports?

Yes, you can generate user docs for GitHub Pages from implementation reports. The pipeline places user-facing documentation in the public-docs directory specifically for GitHub Pages deployment.

What is the best way to structure developer docs and user docs from pipeline artifacts?

The best way to structure developer and user docs is to separate them into distinct directories, placing developer documentation in docs/ and user documentation in public-docs/ for GitHub Pages deployment.

Do I need a review-before-commit workflow for automated documentation generation?

A review-before-commit workflow for automated documentation generation presents the generated developer and user docs for your approval before committing any changes to the repository, ensuring you maintain quality control.