write-docs

Gather context, refine outlines, and test documentation drafts for fresh readers.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/vh2224/forge-executor --skill write-docs-vh2224
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-docs
Source: https://github.com/vh2224/forge-executor/tree/main/src/resources/skills/write-docs
Command: npx skills add https://github.com/vh2224/forge-executor --skill write-docs-vh2224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you write documentation that a fresh reader can actually use, instead of producing notes that only make sense to the person who built the feature. It is meant for cases where the document must stand alone and transfer intent clearly.

Core Features & Use Cases

  • Context gathering: Clarifies who the reader is, what they need to do after reading, and what background they already have.
  • Structure-first drafting: Builds and refines an outline before writing prose, so the document stays organized around the reader's task.
  • Reader-testing: Checks the draft as if it were brand new, removes bloat, and closes gaps before shipping.
  • Use cases: Writing READMEs, RFCs, ADRs, runbooks, PR descriptions, public docs, and other long-form explanations that must work for someone arriving cold.

Quick Start

Ask for a documentation draft that is optimized for a fresh reader and include the audience, the action they need to take after reading, and any source material you want reflected.

Frequently Asked Questions about write-docs

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

FAQPage Schema
How do I write technical documentation that a fresh reader can understand?

Writing a README for a new audience requires gathering context on the reader's background, building an outline-first structure, and cold-testing the draft to remove context-dependent gaps before publishing.

What is the best way to structure an RFC or ADR for a new team member?

The best way to structure an RFC or ADR is to build and refine an outline before writing prose, ensuring the document stays organized strictly around the reader's required actions and background knowledge.

How do I turn rough engineering notes into a runbook?

Turning rough notes into a runbook requires refining the structure into an outline, explicitly defining the audience and their actions, and reader-testing the draft to remove bloat and context gaps.

Can I use this approach to write PR descriptions that stand alone?

Yes, you can use this approach to write PR descriptions that stand alone by defining the reader's required action, applying structure-first drafting, and cold-testing the text to eliminate missing context.

When should I avoid outline-first drafting for technical writing?

You should avoid outline-first drafting for technical writing when a document does not need to stand alone, such as internal notes that only require the original author's context to make sense.