Updating Docs For Release
streamlit/docs
Update the streamlit/docs repo for a new Streamlit release. An agent skill from streamlit/docs.
Plan developer documentation by choosing content types, defining scope, making documentation decisions, researching features, planning scenarios, and turning user needs into a practical…
Install Developer Docs Planning
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-planning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-planning .claude/skills/developer-docs-planning && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "developer-docs-planning" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-planning into .claude/skills/developer-docs-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-planning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-planningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-planning .agents/skills/developer-docs-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "developer-docs-planning" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-planning into .agents/skills/developer-docs-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-planning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-planning .cursor/skills/developer-docs-planning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "developer-docs-planning" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-planning into .cursor/skills/developer-docs-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-planning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hashgraph-online/awesome-codex-plugins.git --path plugins/LVTD-LLC/skills/skills/developer-docs-planning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-planning .gemini/skills/developer-docs-planning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "developer-docs-planning" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-planning into .gemini/skills/developer-docs-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-planning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-planningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-planning .github/skills/developer-docs-planning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "developer-docs-planning" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-planning into .github/skills/developer-docs-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-planning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-planning .opencode/skills/developer-docs-planning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "developer-docs-planning" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-planning into .opencode/skills/developer-docs-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-planning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
developer-docs-planning- GitHub stars
- 1.2k
- Token cost
- ~913 tokens
- SKILL.md length
- 364 words
- Files
- 8 (incl. references)
- Skills in repo
- 736
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan developer documentation by choosing content types, defining scope, making documentation decisions, researching features, planning scenarios, and turning user needs into a practical…
- Works in 6 steps: Load guidelines.md to choose the… → Confirm user goal, audience, product… → Choose content types by user task, not… → …
- Planning READMEs
- SKILL.md covers Quick Start, Default Output, Contents and Core Posture
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Developer Docs Planning is an agent skill from hashgraph-online/awesome-codex-plugins. 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.
Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `guidelines.md`, `references/core/knowledge.md` and `workflows/create-doc-plan.md`). Compatibility notes: Codex, Claude Code, and other Agent Skills-compatible clients.
It sits in Development, covering Changelog and release notes, Technical writing and Technical documentation. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is MIT.
When your agent uses it
- Planning READMEs
- Getting-started guides
- Troubleshooting docs
- Agile docs work
Example prompts
- “/developer-docs-planning”
Requirements
- Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients.
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- 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.
What it can do on your machine
Read from SKILL.md and the folder at commit 16b4156. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
link.springer.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Codex, Claude Code, and other Agent Skills-compatible clients.
From compatibility in the SKILL.md frontmatter.
Context cost
Developer Docs Planning loads about 913 tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 364 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hashgraph-online/awesome-codex-plugins at commit 16b4156, republished under its MIT licence (© hashgraph-online). 364 words, ~913 tokens.
Download SKILL.mdSave it as
.claude/skills/developer-docs-planning/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- developer-docs-planning
- description
- 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.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
- license
- MIT
- metadata.version
- 0.1.0
- metadata.displayName
- Developer Docs Planning
- metadata.category
- Writing
- metadata.tags
- developer-docs,technical-writing,documentation,planning,content-strategy
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.mdto 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.mdfor 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.
Show full SKILL.md (175 more words)Show less
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.
© hashgraph-online, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (references) in plugins/LVTD-LLC/skills/skills/developer-docs-planning of hashgraph-online/awesome-codex-plugins.
- SKILL.md
- guidelines.md
- references/core/knowledge.md
- workflows/create-doc-plan.md
- workflows/integrate-docs-agile.md
- workflows/make-doc-decision.md
- workflows/plan-scenario-docs.md
- workflows/research-feature-docs.md
Open the folder on GitHubat commit 16b4156
Compare with similar skills
Developer Docs Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Developer Docs Planning this skillhashgraph-online/awesome-codex-plugins | 1.2k | — | ~913 | Automated safety check: Pass | MIT | |
| Updating Docs For Releasestreamlit/docs | 178 | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Documentcodewhale-hq/Codewhale | 41k | — | ~170 | Automated safety check: Pass | MIT | |
| Technical Writingfrappe/skills | 146 | — | ~1.1k | Automated safety check: Pass | None | |
| Documentationaiskillstore/marketplace | 430 | 1 repos | ~2.7k | Automated safety check: Pass | None | |
| User Manual Authoringdevcodex-labs/devcodex | 439 | — | ~1.9k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Document
codewhale-hq/Codewhale
Write or update repository/product documentation: README, user guides, API docs, architecture, migration notes, and changelog material.
Technical Writing
frappe/skills
Write prose in "Simplified Technical English". An agent skill from frappe/skills.
Documentation
aiskillstore/marketplace
Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation.
User Manual Authoring
devcodex-labs/devcodex
开源/公开用户站点与最终用户手册写作 Owner — guide/README/reference/migration/changelog/operations；与维护者开发站不等价；经 DocsAudienceIntent 路由。
Docs Interfaces
jh941213/my-cc-harness
Generate interface/API docs — OpenAPI 3.1/AsyncAPI 3.0 specs, API topology diagrams, interface flow (sequence) diagrams, API changelog.
More from hashgraph-online/awesome-codex-plugins
All 736 skills in this repoAnime Reaction Gif
hashgraph-online/awesome-codex-plugins
Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.
Calibredb
hashgraph-online/awesome-codex-plugins
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).
Rust API Test Harness
hashgraph-online/awesome-codex-plugins
A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…
Art
hashgraph-online/awesome-codex-plugins
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…
Calle
hashgraph-online/awesome-codex-plugins
Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.
Game Balance Economy
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
Related
Categories
Questions about Developer Docs Planning
What does Developer Docs Planning do?
Plan developer documentation by choosing content types, defining scope, making documentation decisions, researching features, planning scenarios, and turning user needs into a practical…. Developer Docs Planning is an agent skill from hashgraph-online/awesome-codex-plugins. 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.
When should I use Developer Docs Planning?
Developer Docs Planning fits situations like: planning READMEs; getting-started guides; troubleshooting docs; agile docs work.
How do I install Developer Docs Planning in Claude Code?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-planning -a claude-code`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/developer-docs-planning in hashgraph-online/awesome-codex-plugins) into .claude/skills/developer-docs-planning in your project. Claude Code loads it when a task matches its description.
How do I install Developer Docs Planning in Codex?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-planning -a codex`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/developer-docs-planning in hashgraph-online/awesome-codex-plugins) into .agents/skills/developer-docs-planning in your project. Codex loads it when a task matches its description.
Can I use Developer Docs Planning in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developer-docs-planning, .gemini/skills/developer-docs-planning, .github/skills/developer-docs-planning and .opencode/skills/developer-docs-planning in your project.
What does Developer Docs Planning need to run?
SKILL.md names no scripts, command-line tools or credentials: Developer Docs Planning is instructions for the agent only. Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients..
Does Developer Docs Planning access the network?
SKILL.md names 1 domain. As links in the text: link.springer.com. This is read from the text; nothing was executed.
Is Developer Docs Planning safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Developer Docs Planning use?
Developer Docs Planning is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Developer Docs Planning use?
About 913 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.8k tokens, read only when the agent opens those files.
What are the alternatives to Developer Docs Planning?
Skills that share tags, products or a category with Developer Docs Planning: Updating Docs For Release (streamlit/docs, 178 stars), Document (codewhale-hq/Codewhale, 41k stars), Technical Writing (frappe/skills, 146 stars) and Documentation (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Developer Docs Planning?
hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,232 GitHub stars. The repository holds 736 skills in this directory. The repository was last updated on October 6, 2026.
Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.