documentation

Generates structured technical documentation from code, APIs, and architectural decisions.

39|2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/hffmnnj/opencode-goopspec --skill documentation-hffmnnj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/hffmnnj/opencode-goopspec/tree/main/skills/documentation
Command: npx skills add https://github.com/hffmnnj/opencode-goopspec --skill documentation-hffmnnj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert codebases, APIs, and architecture decisions into clear, maintainable documentation, reducing confusion and manual drafting.

Core Features & Use Cases

  • Template-driven documentation for READMEs, API references, ADRs, and developer guides.
  • Automatic cross-linking and references to source material and decisions.
  • Use Case: On a new project with multiple services, generate a complete documentation package including overview, setup, API surface, and ADRs.

Quick Start

Describe the target codebase, API surface, or design goals to generate a cohesive documentation suite.

Frequently Asked Questions about documentation

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

FAQPage Schema
How do I generate technical documentation from my codebase and API?

Generate technical documentation by describing your codebase, API surface, or design goals to produce structured docs including READMEs, API references, architecture documents, and developer guides. The skill uses plain-language templates to create cohesive documentation packages across different tech stacks.

What documentation formats can I create with templates?

You can create READMEs, API references, Architecture Decision Records (ADRs), developer guides, and project overviews. Templates provide consistent structure and style guidelines across all documentation types, reducing manual drafting and ensuring maintainability.

Can I use this for multi-service projects?

Yes. For projects with multiple services, generate a complete documentation suite in one pass, including architecture overview, setup instructions, API surface documentation, and architectural decisions—eliminating the need to draft separate docs for each component.

Do I need to write documentation manually, or does this automate it?

The skill reduces manual drafting by automating structure and cross-linking. You describe your codebase or API; the skill generates clear, organized documentation from templates and best practices, minimizing the effort to maintain accurate technical docs.

What problem does structured documentation solve for teams?

Structured documentation converts codebases and architectural decisions into maintainable, clear references that reduce confusion, onboarding time, and the need for repetitive explanations across team members.