Skip to content
Back to skills

Doc Writer

ASecurity

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

  • 416 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 7, 2026
documentationgitdocumentation

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add aiskillstore/marketplace --skill doc-writer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Doc Writer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Doc Writer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aiskillstore-doc-writer/badge)](https://www.skillsdirectory.com/skills/aiskillstore-doc-writer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: doc-writer
description: Create or update numbered task docs using repo context, DOC_TEMPLATE.md, and naming conventions.
---

# 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.

Files in this skill

  • SKILL.md1.5 KB
  • skill-report.json9.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…