Developer Docs Planning
Use this skill to decide what developer documentation to create before drafting. It maps user needs to content types, scope, outline, ownership, release context, research work, and decision records.
This skill is derived from Docs for Developers: An Engineer's Field Guide to Technical Writing, especially Chapter 2, "Planning your 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 2, "Agile," Chapter 6, "Documentation Decisions," Chapter 13, "Research for Technical Writers," Chapter 14, "Scenario-driven Information Development," and Chapter 22, "Working with Product Management." 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 user goal, audience, product surface, and release context.
- Choose content types by user task, not by internal org structure.
- Use
workflows/create-doc-plan.md for a full plan.
- Use the specialized workflows when the task is a decision, research pass, scenario plan, or Agile integration.
- Output an outline with doc type, purpose, owner, source of truth, dependencies, and validation.
Default Output
When planning documentation, return:
- Audience and goal - who the docs serve and what they must accomplish.
- Content type decisions - recommended docs and why each belongs.
- Documentation outline - pages or sections with purpose and ordering.
- Decision or research basis - known evidence, assumptions, and unresolved questions.
- Source-of-truth map - code, API schema, product owner, support data, or design source.
- Release and review plan - owners, approvals, and timing.
- Open questions - decisions blocking accurate docs.
Contents
| Need |
Start Here |
| Understand doc types |
references/core/knowledge.md |
| Apply planning rules |
references/core/knowledge.md |
| See plan examples |
references/core/knowledge.md |
| Create a documentation plan |
workflows/create-doc-plan.md |
| Make a documentation decision |
workflows/make-doc-decision.md |
| Research a feature before writing |
workflows/research-feature-docs.md |
| Plan scenario-driven docs |
workflows/plan-scenario-docs.md |
| Integrate docs with Agile work |
workflows/integrate-docs-agile.md |
| Route by task |
guidelines.md |
Core Posture
- Let user tasks choose the content type.
- Keep each doc anchored to one primary goal.
- Treat plans as lightweight engineering artifacts, not ceremony.
- Expose decisions, assumptions, and source gaps early.
- If the documentation plan feels like a maze, consider whether the product or information architecture is too complex.
Source: hashgraph-online/awesome-codex-plugins → plugins/LVTD-LLC/skills/skills/developer-docs-planning/SKILL.md
1---2name: developer-docs-planning3description: Plan developer documentation by choosing content types, defining scope, making documentation decisions, researching features, planning scenarios, and turning user needs into a practical documentation plan. Use when planning READMEs, getting-started guides, concepts, tutorials, how-to guides, API references, troubleshooting docs, changelogs, release notes, Agile docs work, or multi-doc launch plans.4---567# Developer Docs Planning89Use this skill to decide what developer documentation to create before drafting. It maps user needs to content types, scope, outline, ownership, release context, research work, and decision records.1011This skill is derived from *Docs for Developers: An Engineer's Field Guide to Technical Writing*, especially Chapter 2, "Planning your 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 2, "Agile," Chapter 6, "Documentation Decisions," Chapter 13, "Research for Technical Writers," Chapter 14, "Scenario-driven Information Development," and Chapter 22, "Working with Product Management." 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 user goal, audience, product surface, and release context.173. Choose content types by user task, not by internal org structure.184. Use `workflows/create-doc-plan.md` for a full plan.195. Use the specialized workflows when the task is a decision, research pass, scenario plan, or Agile integration.206. Output an outline with doc type, purpose, owner, source of truth, dependencies, and validation.2122## Default Output2324When planning documentation, return:25261. **Audience and goal** - who the docs serve and what they must accomplish.272. **Content type decisions** - recommended docs and why each belongs.283. **Documentation outline** - pages or sections with purpose and ordering.294. **Decision or research basis** - known evidence, assumptions, and unresolved questions.305. **Source-of-truth map** - code, API schema, product owner, support data, or design source.316. **Release and review plan** - owners, approvals, and timing.327. **Open questions** - decisions blocking accurate docs.3334## Contents3536| Need | Start Here |37|------|------------|38| Understand doc types | `references/core/knowledge.md` |39| Apply planning rules | `references/core/knowledge.md` |40| See plan examples | `references/core/knowledge.md` |41| Create a documentation plan | `workflows/create-doc-plan.md` |42| Make a documentation decision | `workflows/make-doc-decision.md` |43| Research a feature before writing | `workflows/research-feature-docs.md` |44| Plan scenario-driven docs | `workflows/plan-scenario-docs.md` |45| Integrate docs with Agile work | `workflows/integrate-docs-agile.md` |46| Route by task | `guidelines.md` |4748## Core Posture4950- Let user tasks choose the content type.51- Keep each doc anchored to one primary goal.52- Treat plans as lightweight engineering artifacts, not ceremony.53- Expose decisions, assumptions, and source gaps early.54- If the documentation plan feels like a maze, consider whether the product or information architecture is too complex.5556---5758**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/LVTD-LLC/skills/skills/developer-docs-planning/SKILL.md`
thedixitjain