Marketplace doc-writer

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

install

source · Clone the upstream repo

git clone https://github.com/aiskillstore/marketplace

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/aiskillstore/marketplace "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/0xhiroki/doc-writer" ~/.claude/skills/aiskillstore-marketplace-doc-writer && rm -rf "$T"

manifest: skills/0xhiroki/doc-writer/SKILL.md

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

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.
Draft the document following exact sections: metadata block, Objective, Prerequisites / Dependencies, Implementation Steps, Validation, Completion Criteria, Notes / Follow-ups.
Reference existing code or documentation by linking relative paths rather than duplicating large excerpts.
Confirm acceptance criteria reflect the latest repository state (tests, tooling, env requirements).
Save the file under the correct directory (
```
docs/planned/
```
or
```
docs/completed/
```
) with the naming convention
```
NN-task-name.md
```
.
Run required validators (lint/tests) if file changes mandate repository updates; record commands executed.
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.