Agent skill · writing content · aiskillstore
doc-writer
Create or update numbered task docs using repo context, DOC_TEMPLATE.md, and naming conventions.
Why this skill is useful
Codifies specific documentation standards and naming conventions for task documentation that the AI could infer but doesn't have to guess.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Doc Writer Skill Purpose Generate or refresh docs/planned/XX-.md and docs/completed/XX-.md files using the mandated template (docs/DOCTEMPLATE.md) and existing repository content. Instructions 1. Inspect relevant source material: Read docs/DOCTEMPLATE.md for structure expectations. Gather context from PLAN.md, AGENTS.md, and any existing task doc being updated. When creating a new task, identify prior numbering and ensure a unique two-digit prefix. 2. Draft the document following exact sections: metadata block, Objective, Prerequisites / Dependencies, Implementation Steps, Validation, Completion Criteria, Notes / Follow-ups. 3. Reference existing code or documentation by linking relative paths rather than duplicating large excerpts. 4. Confirm acceptance criteria reflect the latest repository state (tests, tooling, env requirements). 5. Save the file under the correct directory (docs/planned/ or docs/completed/) with the naming convention NN-task-name.md. 6. Run required validators (lint/tests) if file changes mandate repository updates; record commands executed. 7. Summarize the edits in the PR/task notes. Verification Ensure the new/updated doc passes markdown lint (if configured) and adheres to docs/DOCTEMPLATE.md structure. Confirm numbering sequence remains unique.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/doc-writer