document-writer

Create templated ADR, RFC, and system design documentation.

8|11|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/belokonm/claude-supercode-skills --skill document-writer-belokonm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-writer
Source: https://github.com/belokonm/claude-supercode-skills/tree/main/document-writer-skill
Command: npx skills add https://github.com/belokonm/claude-supercode-skills --skill document-writer-belokonm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing consistent technical documentation (ADRs, RFCs, and system design docs) is time-consuming and error-prone without templates and standards.

Core Features & Use Cases

  • ADR creation and templated decision records for architectural choices.
  • RFC drafting with problem statements, constraints, and implementation plans.
  • System design documentation, runbooks, and knowledge-base articles for operational clarity.
  • Cross-linking between documents and template-driven consistency across projects.

Quick Start

Ask me to draft an ADR, RFC, and system design document for your upcoming feature.

Frequently Asked Questions about document-writer

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

FAQPage Schema
How do I create consistent ADRs for architectural decisions?

Create consistent ADRs by applying standardized templates to architectural decision records, ensuring structured context, decision drivers, and consequences across engineering teams. This approach standardizes architectural choices and reduces documentation errors.

What is the best way to draft an RFC with implementation plans?

Draft an RFC by structuring problem statements, constraints, and implementation plans into a standardized template. This ensures all technical constraints and proposed solutions are clearly communicated before development begins.

Can I use templates for system design documentation and runbooks?

Yes, you can use templates for system design documentation and runbooks to achieve operational clarity. Standardized structures provide consistent knowledge-base articles and cross-linking between documents across software projects.

Does this approach support cross-linking between design docs and reference materials?

Yes, this approach supports cross-linking between design docs and reference materials. It enables versioned documentation workflows and template-driven consistency, connecting ADRs, RFCs, and system docs across multiple projects.