document

Generate changelogs, guides, and architecture documents from plan artifacts.

Updated Jul 21, 2026

Search Tags:#changelog #architecture #documentation #content generation #guides #artifact processing

Ready to run

npx skills add https://github.com/roborew/opencode --skill document-roborew

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document
Source: https://github.com/roborew/opencode/tree/main/skills/document
Command: npx skills add https://github.com/roborew/opencode --skill document-roborew

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of essential documentation content, including changelogs, user guides, and architecture documents, from completed plan artifacts.

Core Features & Use Cases

Changelog Generation: Creates concise release notes based on implementation details.
Guide Creation: Develops user-friendly guides explaining functionality and usage.
Architecture Documentation: Produces ADR-style documents detailing design decisions and context.
Use Case: After a new feature is implemented and verified, this Skill can automatically draft the corresponding changelog entry and update the user guide.

Quick Start

Use the document skill to generate a changelog for the artifact located at .plan/feature.new-login.md.

Frequently Asked Questions about document

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

FAQPage Schema

How do I generate release notes and changelogs automatically from completed feature artifacts?▼

You can generate changelogs by providing completed plan artifacts to the document skill, which derives concise release notes directly from the implementation details and artifact paths.

What is the best way to create architecture documentation like ADRs from existing plan files?▼

The best way to create architecture documentation is processing plan artifacts through the document skill, which produces ADR-style documents detailing design decisions and technical context from the provided completion data.

Can I automatically draft user guides and manuals based on implementation details?▼

Yes, you can automatically draft user guides by supplying implementation artifacts to the document skill, which develops user-friendly manuals explaining functionality and usage based on the completion context.

Do I need to provide artifact paths and completion context to generate technical documentation?▼

Yes, you need to provide artifact paths and completion context because accurate content derivation for technical design documents, changelogs, and guides requires access to the completed plan artifacts.

When should I use automated content generation for documentation instead of writing manually?▼

You should use automated content generation when a new feature is implemented and verified, allowing the document skill to automatically draft the corresponding changelog entry and update the user guide simultaneously.