AI Agent Skill HUB
multiAI Summary Pending

doc-writer

Create or update numbered task docs using repo context, DOC_TEMPLATE.md, and naming conventions.

231 stars
byaiskillstore
View on GitHubInstallation ↓

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/doc-writer/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/0xhiroki/doc-writer/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/doc-writer/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How doc-writer Compares

Feature / Agentdoc-writerStandard Approach
Platform SupportmultiLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Create or update numbered task docs using repo context, DOC_TEMPLATE.md, and naming conventions.

Which AI agents support this skill?

This skill is compatible with multi.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Doc Writer Skill

## Purpose
Generate or refresh `docs/planned/XX-*.md` and `docs/completed/XX-*.md` files using the mandated template (`docs/DOC_TEMPLATE.md`) and existing repository content.

## Instructions
1. Inspect relevant source material:
   - Read `docs/DOC_TEMPLATE.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/DOC_TEMPLATE.md` structure.
- Confirm numbering sequence remains unique.