documentation

Name: documentation
Availability: InStock
Author: shakhovskiya-create

Generate and maintain technical documentation from code and architectural decisions.

Updated May 5, 2026

Search Tags:#documentation #onboarding #readme #runbooks #api-docs #architecture-diagrams #docs-generation

Ready to run

npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill documentation-shakhovskiya-create

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/solo-sdlc/skills/documentation
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill documentation-shakhovskiya-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating and maintaining consistent, high-quality documentation across READMEs, API docs, runbooks, and architecture diagrams is time-consuming and error-prone.

Core Features & Use Cases

Unified documentation blueprint: guides for README, API specs, ADRs, architecture diagrams, and getting-started guides.
Documentation automation: auto-generates standard docs from code, tests, and architectural decisions, ensuring consistency across releases.
Use Case: When shipping a major feature, generate a complete docs package including README, API surface, runbook, and architecture diagram.

Quick Start

Ask me to generate a complete documentation package for a feature, including README, API docs, ADRs, runbooks, and getting-started guides.

Frequently Asked Questions about documentation

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

FAQPage Schema

How do I generate a complete documentation package for a new feature?▼

Generate a complete documentation package by requesting README, API docs, ADRs, runbooks, and architecture diagrams together. The Skill automates multi-file creation using frontmatter-based templates, ensuring all docs are consistent and versioned with your release.

What is the best way to automate technical documentation across releases?▼

Automate technical documentation by generating standard docs directly from code, tests, and architectural decisions. This ensures consistency across releases by aligning documentation versioning with your software shipping cycle, reducing manual effort and errors.

Can I create architecture diagrams and runbooks from existing code?▼

Yes, you can create architecture diagrams and runbooks from existing code. The Skill auto-generates standard documentation from code, tests, and architectural decisions, applying unified blueprints to keep technical artifacts synchronized with your project.

Do I need frontmatter-based templates to maintain API docs and ADRs?▼

Frontmatter-based templates are supported to maintain API docs and ADRs, but are not strictly required to start. They help enforce structure and consistency across multi-file generation, ensuring your documentation remains organized as the project scales.

How do I keep README and getting-started guides consistent during feature shipping?▼

Keep README and getting-started guides consistent by auto-generating them alongside API specs and architecture diagrams during feature shipping. The Skill applies a unified documentation blueprint to ensure all onboarding materials match the current codebase.