Developer Docs Drafting
Use this skill to draft developer documentation that readers can skim, follow, and apply. It turns audience and plan context into clear page structure and usable prose.
This skill is derived from Docs for Developers: An Engineer's Field Guide to Technical Writing, especially Chapter 3, "Drafting documentation." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's The Product Is Docs: Writing Technical Documentation in a Product Development Group, especially Chapter 9, "Learning Objectives," Chapter 14, "Scenario-driven Information Development," and Chapter 25, "Writing SaaS Documentation." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6
Quick Start
- Load
guidelines.md to choose the smallest useful reference set.
- Confirm audience, doc type, one primary reader goal, and learning objective when available.
- Outline before drafting; treat the outline like pseudocode for the doc.
- Use
workflows/draft-developer-doc.md for full-page drafts.
- Put the most important information first and make the page easy to skim.
Default Output
When drafting a doc, return:
- Title - aligned with the reader goal.
- Opening context - what the reader will accomplish and prerequisites.
- Structured body - headings, steps, concepts, examples, lists, and callouts as appropriate.
- Scenario or route - real-world path, scope boundary, or self-contained topic context when useful.
- Verification or expected result - how the reader knows the task worked.
- Next steps - where the reader should go next.
- Draft notes - assumptions, TODOs, or source details needing review.
Contents
| Need |
Start Here |
| Understand drafting components |
references/core/knowledge.md |
| Apply drafting rules |
references/core/knowledge.md |
| See before/after examples |
references/core/knowledge.md |
| Draft a page |
workflows/draft-developer-doc.md |
| Route by task |
guidelines.md |
Core Posture
- Write for the reader's next decision or action.
- Make the page understandable to skimmers.
- Keep procedures actionable and verifiable.
- Lead scenario docs with the user's problem, not the product feature.
- Use templates to reduce blank-page work, not to force every doc into the same shape.
Source: hashgraph-online/awesome-codex-plugins → plugins/LVTD-LLC/skills/skills/developer-docs-drafting/SKILL.md
1---2name: developer-docs-drafting3description: Draft developer documentation with clear goals, outlines, titles, headers, procedures, scenario walkthroughs, lists, callouts, skimmable structure, and reusable templates. Use when writing or rewriting READMEs, getting-started docs, tutorials, how-to guides, concepts, API guides, troubleshooting pages, migration guides, SaaS topics, or release documentation.4---567# Developer Docs Drafting89Use this skill to draft developer documentation that readers can skim, follow, and apply. It turns audience and plan context into clear page structure and usable prose.1011This skill is derived from *Docs for Developers: An Engineer's Field Guide to Technical Writing*, especially Chapter 3, "Drafting documentation." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 9, "Learning Objectives," Chapter 14, "Scenario-driven Information Development," and Chapter 25, "Writing SaaS Documentation." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-61213## Quick Start14151. Load `guidelines.md` to choose the smallest useful reference set.162. Confirm audience, doc type, one primary reader goal, and learning objective when available.173. Outline before drafting; treat the outline like pseudocode for the doc.184. Use `workflows/draft-developer-doc.md` for full-page drafts.195. Put the most important information first and make the page easy to skim.2021## Default Output2223When drafting a doc, return:24251. **Title** - aligned with the reader goal.262. **Opening context** - what the reader will accomplish and prerequisites.273. **Structured body** - headings, steps, concepts, examples, lists, and callouts as appropriate.284. **Scenario or route** - real-world path, scope boundary, or self-contained topic context when useful.295. **Verification or expected result** - how the reader knows the task worked.306. **Next steps** - where the reader should go next.317. **Draft notes** - assumptions, TODOs, or source details needing review.3233## Contents3435| Need | Start Here |36|------|------------|37| Understand drafting components | `references/core/knowledge.md` |38| Apply drafting rules | `references/core/knowledge.md` |39| See before/after examples | `references/core/knowledge.md` |40| Draft a page | `workflows/draft-developer-doc.md` |41| Route by task | `guidelines.md` |4243## Core Posture4445- Write for the reader's next decision or action.46- Make the page understandable to skimmers.47- Keep procedures actionable and verifiable.48- Lead scenario docs with the user's problem, not the product feature.49- Use templates to reduce blank-page work, not to force every doc into the same shape.5051---5253**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/LVTD-LLC/skills/skills/developer-docs-drafting/SKILL.md`
thedixitjain