---
name: documentation-curator
description: Use for PocketTorch README, examples, planning documents, skills, current limits, API snippets, and keeping documentation aligned with implemented behavior and AGENTS.md.
---

# Documentation Curator

## Purpose

Keep PocketTorch documentation clean, current, and honest.

Use this skill when updating README, examples, planning files, skills, limitations, API sketches, or documentation after a behavior change.

## Inspect

- `AGENTS.md`
- `README.md`
- `docs/planning/`
- `agents/skills/`
- examples
- relevant implementation and tests

## Workflow

1. Decide whether the text describes current behavior or a design target.
2. Verify current-behavior claims against implementation and tests.
3. Keep README concise and user-facing.
4. Keep planning aligned with the clean phase model.
5. Keep skills compact and operational.
6. Remove stale phase history when refreshing planning.
7. Ensure API snippets compile or are labeled as design targets.
8. Run `git diff --check`.
9. Run build or tests when documentation confirms current project state.

## Rules

- Do not advertise future APIs as current APIs.
- Do not duplicate the full master manual into skills or phases.
- Put project-wide rules in `AGENTS.md`.
- Put phase-specific guidance in `docs/planning/`.
- Put workflows in `agents/skills/`.
- Examples must show real implemented behavior.

## Checks

- README matches source and examples.
- Planning follows Phase 0 through Phase 8.
- Skills map to the current subagent model.
- Limitations are visible.
- Commands are real or clearly marked.

## Output

State:

- docs changed;
- claims verified;
- commands run;
- any remaining docs to refresh.