technical-writer Claude Code subagentA

technical-writer from kamiazya/whiteboard is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.

Install it, pinned
mdr add kamiazya/whiteboard/.claude/agents/technical-writer.md@git:20260712.393de85

Pins git:20260712.393de85 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 14 of 14 checks passed
Kind
Claude Code subagent
Repository
kamiazya/whiteboard
Path
.claude/agents/technical-writer.md
Versions recorded
2
Latest version
git:20260712.393de85, committed Jul 12, 2026
First version recorded
Jun 15, 2026
Size
2,204 bytes
Repository stars
11
License
Apache-2.0

Keeps the whiteboard project's developer/user docs in sync with code & behavior changes, and maintains docs IA (Diátaxis). Spawned by the dev-loop Docs phase and invoked ad-hoc for doc gaps. Updates only doc files; commits them separately. Pass the change range/scope in the prompt.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

You keep documentation truthful and in sync with the code. You edit DOCS only — never production source or tests.

**Audience split (project rule):** `./docs/**` is USER-facing only, organized by Diátaxis (tutorials / how-to / reference / explanation). Developer-facing docs follow OSS convention at the repo root — `README.md`, `SECURITY.md`, `CONTRIBUTING.md` (+ `CODE_OF_CONDUCT.md`, `.github/` templates, etc.). Do not put developer/contributor guides under `./docs`.

**Language: all project docs are written in ENGLISH** at this stage. (Local `tmp/` notes may be other languages, but anything under `docs/`, `README`, `SECURITY`, `CONTRIBUTING`, `.github` is English.)

## How

1. Read the change you're documenting (e.g. `git diff <baseRef>..HEAD`) and identify which docs are affected (see the `docs-sync` skill for the trigger→target map).
2. Update the affected docs to match the SHIPPED behavior. **Honesty first**: never describe a feature, flag, route, or path that does not exist yet — if the code is partial, document the real current state, not the aspiration.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add kamiazya/whiteboard/.claude/agents/technical-writer.md@sha256:cc1b4cc54672c996

The line at the top of this page pins the label git:20260712.393de85, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_iotxujcqaj6lomoz.svg)](https://markdownregistry.com/a/art_iotxujcqaj6lomoz)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in kamiazya/whiteboard/.claude/agents/technical-writer.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of technical-writer.md from somewhere else? Ask it: where did my technical-writer.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, between Jun 15, 2026 and Jul 12, 2026, about one every 26 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260712.393de85 latest2026-07-12 393de85 2,204 BA view · diff
git:20260615.5a9e01c2026-06-15 5a9e01c 2,204 BA view
Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  14 of 14 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Size between 200 bytes and 200 KB (2204 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

kamiazya/whiteboard · 11 stars · license Apache-2.0 · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_iotxujcqaj6lomoz
GET https://markdownregistry.com/api/v1/resolve?ref=kamiazya/whiteboard/.claude/agents/technical-writer.md
GET https://markdownregistry.com/api/v1/blob/cc1b4cc54672c996b1d676fc6fd7eb8ac1ce515688ae5348b20dc4c1cb16617b

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: which agent file does what.

More from kamiazya/whiteboard

whiteboard-marketplace Plugin marketplace
kamiazya/whiteboard · .claude-plugin/marketplace.json · Claude Code plugin distribution for the @kamiazya/whiteboard collaborative diagramming MCP. (1 plugin: whiteboard)
v0.0.20 · audit A · 11 stars
architect Claude Code subagent
kamiazya/whiteboard · .claude/agents/architect.md · System-design perspective for the plan-initiative panel. Given an initiative + brief, analyzes seams, data model…
git:20260615.5a9e01c · audit A · 11 stars
codebase-auditor Claude Code subagent
kamiazya/whiteboard · .claude/agents/codebase-auditor.md · Read-only whole-codebase health auditor for ONE dimension (wiring-gaps / architecture / maintainability /…
git:20260823.f4de3fa · audit A · 11 stars
developer Claude Code subagent
kamiazya/whiteboard · .claude/agents/developer.md · TDD implementer for one well-scoped change in the whiteboard repo. Spawned by the dev-loop workflow's Implement phase…
git:20261006.53380bb · audit A · 11 stars
dogfood-persona Claude Code subagent
kamiazya/whiteboard · .claude/agents/dogfood-persona.md · Drives the running whiteboard app as a realistic end-user persona via the Playwright MCP browser tools, to surface…
git:20261012.6fa4c18 · audit A · 11 stars
marketing Claude Code subagent
kamiazya/whiteboard · .claude/agents/marketing.md · Drafts release notes, changelog entries, README hero/positioning, and announcements for the whiteboard project…
git:20260615.5a9e01c · audit A · 11 stars
plan-reviewer Claude Code subagent
kamiazya/whiteboard · .claude/agents/plan-reviewer.md · Reviews a draft design/plan for one whiteboard dev task BEFORE implementation, against the repo's completeness rubric…
git:20261002.0803037 · audit A · 11 stars
product-manager Claude Code subagent
kamiazya/whiteboard · .claude/agents/product-manager.md · Product/value perspective for the plan-initiative panel. Given an initiative + brief, clarifies user value, scope vs…
git:20260615.5a9e01c · audit A · 11 stars
project-manager Claude Code subagent
kamiazya/whiteboard · .claude/agents/project-manager.md · Delivery/sequencing perspective for the plan-initiative panel. Given an initiative + brief, slices the work into…
git:20260811.7b616bf · audit A · 11 stars
qa-scenario Claude Code subagent
kamiazya/whiteboard · .claude/agents/qa-scenario.md · QA tester for one specific scenario (startup/docs-reachability/smoke/error-recovery/migration). Spawned by qa to…
git:20261002.0803037 · audit A · 11 stars
repo-hygiene-investigator Claude Code subagent
kamiazya/whiteboard · .claude/agents/repo-hygiene-investigator.md · Lightweight read-only investigator for repo-hygiene / policy / portability questions — e.g. "should we track .claude/…
git:20260615.5a9e01c · audit A · 11 stars
research-analyst Claude Code subagent
kamiazya/whiteboard · .claude/agents/research-analyst.md · External-research perspective for the plan-initiative panel. Uses web search/fetch to surface industry best practices…
git:20260615.5a9e01c · audit A · 11 stars

Every file in kamiazya/whiteboard

Other files named technical-writer

technical-writer SKILL.md skill
vercel-labs/agent-browser · .agents/skills/technical-writer/SKILL.md · Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as…
v1.3 · audit A · 52,506 stars
technical-writer SKILL.md skill
vercel-labs/fx · .fx/skills/technical-writer/SKILL.md · Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as ai-sdk.dev…
v1.3 · audit A · 3,893 stars
technical-writer SKILL.md skill
codeaholicguy/ai-devkit · skills/technical-writer/SKILL.md · AI DevKit · Review and improve documentation for novice users. Use when users ask to review docs, improve…
git:20260509.950097b · audit A · 1,668 stars
technical-writer SKILL.md skill
onewave-ai/claude-skills · technical-writer/SKILL.md · Write comprehensive technical documentation including user guides, how-to articles, system architecture docs…
git:20260608.d82d20f · audit A · 433 stars
technical-writer SKILL.md skill
vercel-labs/issue-graph · .agents/skills/technical-writer/SKILL.md · Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as…
v1.3 · audit A · 195 stars
technical-writer SKILL.md skill
widnyana/eyay-toolkits · plugins/prose-engineers/skills/technical-writer/SKILL.md · This skill should be used when the user asks to "write a blog post", "draft a postmortem", "document this process"…
git:20260829.6d9d2bb · audit A · 9 stars
technical-writer SKILL.md skill
oneafrikan/the-grid · agent-factory/roles/technical-writer/SKILL.md
git:20261001.99b2282 · audit C · 5 stars

Browse by kind, by grade A, or by owner.