doc-writer
Create Structured Task Documentation
Teams often lose task context when plans, requirements, and validation steps are scattered. This skill creates consistent task documents from repository context and templates.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "doc-writer" from https://skillstore.io/skills/0xhiroki-doc-writer.md and its manifest at https://skillstore.io/api/skills/0xhiroki-doc-writer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "doc-writer". Create a planned task document for adding OAuth callback validation.
Expected outcome:
A numbered planned task document with objective, dependencies, implementation steps, validation, completion criteria, and repository links.
Using "doc-writer". Update the completed task document after linting and tests passed.
Expected outcome:
A refreshed completed task document that records validation commands, current status, and any remaining follow-up work.
Using "doc-writer". Prepare documentation for a handoff to another maintainer.
Expected outcome:
A template-aligned task document that explains scope, context, next steps, and acceptance criteria for the maintainer.
Security Audit
SafeThe static findings are false positives caused by Markdown inline code around file paths and naming examples in SKILL.md. I found no prompt injection, data exfiltration intent, or unsafe command construction in the reviewed skill instructions.
Risk Factors
⚙️ External commands (5)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/0xhiroki-doc-writer/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/0xhiroki-doc-writer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/0xhiroki-doc-writer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/0xhiroki-doc-writer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/0xhiroki-doc-writer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
0xhiroki. (2026). doc-writer security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/0xhiroki-doc-writer/audits/6BibTeX citation
@techreport{0xhiroki-0xhiroki-doc-writer-2026,
author = {0xhiroki},
title = {doc-writer security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/0xhiroki-doc-writer/audits/6},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "doc-writer security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "0xhiroki"
date-released: "2026-07-04"
url: "https://skillstore.io/skills/0xhiroki-doc-writer/audits/6"
identifiers:
- type: other
value: "skillstore:0xhiroki-doc-writer:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a New Engineering Task
Create a planned task document with clear objectives, dependencies, steps, validation, and completion criteria.
Update an Existing Task Record
Refresh a task document so it reflects current repository state, latest decisions, and completed validation work.
Standardize Documentation Before Review
Align task notes with the shared template before opening a pull request or handing work to another contributor.
Try These Prompts
Create a new planned task document for [task name]. Use docs/DOC_TEMPLATE.md and relevant repository context.
Update docs/planned/[file name].md using PLAN.md, AGENTS.md, and current repository files. Keep the required template sections.
Create a completed task document for [task name]. Include implemented changes, validation commands, completion criteria, and follow-up notes.
Review existing docs/planned and docs/completed numbering. Create the next task document for [scope] with unique numbering and repository links.
Best Practices
- Provide the task name, target directory, and relevant repository files before asking for a new document.
- Review generated acceptance criteria against actual project requirements before relying on them.
- Run configured markdown linting or tests when documentation changes affect repository workflows.
Avoid
- Do not ask the skill to invent missing requirements without project context.
- Do not copy large source excerpts into task documents when relative links are enough.
- Do not skip numbering checks when creating a new planned or completed task file.