Docs writer
21 markdown-first software delivery workflow skills for Claude Code, Codex, and compatible agents. Standalone skill kit covering planning, debugging, CI, review, security, rollout, performance, data quality, and post-incident workflows.
npx -y skills add motao123/dev-workflow-kit --skill docs-writerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when completed or in-progress work needs documentation such as README updates, migration notes, release notes, usage examples, or developer-facing operational guidance. This skill writes docs grounded in the current code and verified behavior.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.7 KB, as published. Nobody here has run it
Docs Writer
Use this skill when project knowledge needs to be turned into durable documentation.
Trigger Conditions
Use this skill when:
- README or setup docs need updates
- a change requires migration notes or release notes
- usage examples must be added
- implementation behavior should be documented for other developers
- the user asks for docs tied to real code changes
Do not use this skill to invent architecture or behavior that is not supported by the current code.
Workflow
- Read the relevant code and existing docs first.
- Identify the audience and purpose.
- Capture only the behavior that is real and current.
- Write the smallest docs that close the knowledge gap.
- Preserve examples and step ordering where they help.
- Note any missing verification if docs depend on untested behavior.
Output
For non-trivial work, provide:
- target audience
- docs updated or drafted
- source of truth consulted
- open gaps or assumptions
Coordination
Before documentation:
- use the active implementation workflow if the behavior is still changing
- use
ship-readinessif docs are part of release completion - use
security-reviewif the docs touch sensitive operational guidance
Invocation Examples
- "Use docs-writer to update the README for this new setup flow."
- "Use docs-writer to draft migration notes for this breaking change."
- "Use docs-writer to create a short release note and usage example."