Receber por email
← Voltar para o catálogo

doc-writer

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

367estrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/doc-writer/svg)](https://www.skillteca.com.br/skills/doc-writer)

Skills relacionadas

Ver todas de Segurança →

Alerta por categoria

Receba novas skills de Segurança toda segunda

1 email curto, só com as skills novas de Segurança. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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:
  2. Read docs/DOC_TEMPLATE.md for structure expectations.
  3. Gather context from PLAN.md, AGENTS.md, and any existing task doc being updated.
  4. When creating a new task, identify prior numbering and ensure a unique two-digit prefix.
  5. Draft the document following exact sections: metadata block, Objective, Prerequisites / Dependencies, Implementation Steps, Validation, Completion Criteria, Notes / Follow-ups.
  6. Reference existing code or documentation by linking relative paths rather than duplicating large excerpts.
  7. Confirm acceptance criteria reflect the latest repository state (tests, tooling, env requirements).
  8. Save the file under the correct directory (docs/planned/ or docs/completed/) with the naming convention NN-task-name.md.
  9. Run required validators (lint/tests) if file changes mandate repository updates; record commands executed.
  10. 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.
Compartilhar X LinkedIn