Individual skill
developer-docs-planning
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.
plugins/LVTD-LLC/skills/skills/developer-docs-planning/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,532
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- docs Derived category
- engineering Derived category
- writing Derived category
- productivity Derived category
- productivity-notes Derived category
Declared tags are partial or unavailable.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,652 bytesSKILL.mdcore · 3,652 bytesSKILL.mdcore · 3,652 bytesguidelines.mddoc · 2,406 bytesreferences/core/knowledge.mddoc · 11,083 bytesworkflows/create-doc-plan.mddoc · 2,244 bytesworkflows/integrate-docs-agile.mddoc · 2,716 bytesworkflows/make-doc-decision.mddoc · 2,026 bytesworkflows/plan-scenario-docs.mddoc · 2,602 bytesworkflows/research-feature-docs.mddoc · 2,849 bytes
Read excerpt
# 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
1. Load `guidelines.md` to choose the smallest useful reference set.
2. Confirm user goal, audience, product surface, and release context.
3. Choose content types by user task, not by internal org structure.
4. Use `workflows/create-doc-plan.md` for a full plan.
5. Use the specialized workflows when the task is a decision, research pass, scenario plan, or Agile integration.
6. Output an outline with doc type, purpose, owner, source of truth, dependencies, and validation.