# 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

```bash
npx skillstore add 0xhiroki/doc-writer
```

## Metadata

- Status: approved
- Slug: 0xhiroki-doc-writer
- Skillstore revision: r1
- Version status: missing
- Tree hash: ced043044c34e76ef0ede83e9cc60a69024d843019670fe1666bd80bfa3a94cc
- Author: 0xhiroki
- GitHub username: 0xhiroki
- License: MIT
- Repository: https://github.com/0xhiroki/tassp/tree/main/.factory/skills/doc-writer
- Ref: e9e4712298ed071d92417a41714be123eb8364fa
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/0xhiroki-doc-writer
- Manifest: https://skillstore.pages.dev/api/skills/0xhiroki-doc-writer/manifest

## Capabilities

- Reads docs/DOC\_TEMPLATE.md to follow the required task document structure.
- Uses PLAN.md, AGENTS.md, and existing task documents as repository context.
- Creates numbered files under docs/planned or docs/completed with the NN-task-name.md format.
- Drafts required sections for objectives, dependencies, implementation steps, validation, and completion criteria.
- Links to related repository files instead of copying long excerpts.
- Records validation commands when file changes require linting or tests.

## Use Cases

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

## Prompt Templates

### Create a Basic Task Doc

```
Create a new planned task document for [task name]. Use docs/DOC_TEMPLATE.md and relevant repository context.
```

### Refresh an Existing Task Doc

```
Update docs/planned/[file name].md using PLAN.md, AGENTS.md, and current repository files. Keep the required template sections.
```

### Document Completion Evidence

```
Create a completed task document for [task name]. Include implemented changes, validation commands, completion criteria, and follow-up notes.
```

### Reconcile Numbering and Scope

```
Review existing docs/planned and docs/completed numbering. Create the next task document for [scope] with unique numbering and repository links.
```

## Limitations

- Requires the repository to provide the expected docs/DOC\_TEMPLATE.md file.
- Does not define project strategy without source plans or task context.
- May need human review for acceptance criteria and scheduling decisions.
- Validator execution depends on the tools configured in the repository.

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

## Anti Patterns

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

## Security Audit

- Audited at: 2026-07-04T13:29:54.681\+00:00
- Summary: The 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.

## Stats

- Views: 199
- Downloads: 30
- Favorites: 0
- Popularity score: 0