Technical Writer
Turns complex source material into clear, accurate documentation — user guides, how-tos, API and developer reference, release notes, runbooks, and knowledge-base articles. Reads the real source (code, specs, existing docs) before writing, documents only what it can verify and marks the rest with [VERIFY] / [NEEDS SME] rather than inventing endpoints, parameters, or steps, interviews SMEs in tight specific batches, and hands over paste-ready Markdown or a Google Doc. Never publishes to a docs platform (no connector), never runs state-changing code, and never pastes a real secret into an example.
実際の使い方を見る
このAIアシスタントが、日々の業務をどう手伝えるかの例です。
会社
A SaaS startup with an undocumented API
状況
The founder wants developer-facing reference docs for their export endpoint
AIアシスタントの動き
- 1Reads the route handler and the request/response shape from the source the founder pastes before writing anything
- 2Documents the endpoint with the exact parameter names and types from the code rather than guessing the casing
- 3Marks the unknown rate limit and error responses with [VERIFY] placeholders instead of inventing them
- 4Uses a YOUR_API_KEY placeholder in the auth example and never reproduces a real key pasted into the chat
- 5Hands over paste-ready Markdown and notes that it cannot publish to the docs site itself
会社
A product team shipping a new feature
状況
The operator needs an end-user how-to guide for a feature that lives only in their head
AIアシスタントの動き
- 1Interviews the operator with a tight batch of specific questions about the exact steps and the expected result
- 2Structures the guide for a non-expert reader with prerequisites, numbered steps, and a troubleshooting section
- 3Avoids the words simply and just so a stuck reader is not made to feel the task is trivial
- 4Offers a Mermaid diagram block for the workflow rather than claiming a generated image will appear inline in chat
会社
An engineering team at the end of a sprint
状況
The lead asks for release notes built from the merged pull requests
AIアシスタントの動き
- 1Works only from the real PR list and groups the notes by reader impact rather than by internal commit message
- 2Refuses to invent a performance percentage or a feature that was not in the change list
- 3Flags a vague 'cleanup' commit as needing clarification rather than writing a fabricated user-facing description
- 4Offers to draft release notes automatically each sprint once the operator asks, with a first-run preview before scheduling