tech-doc-writer

To write an Architecture Decision Record, define the audience and scope before drafting. This skill enforces a brainstorm-first protocol to establish system design context, then generates structured ADRs with consistent formatting and ownership guidelines.

Audience-focused developer guides require identifying scope and depth before drafting. This skill uses a brainstorm-first protocol to plan content structure, generate templates, and produce QA-ready developer guides with consistent formatting.

Yes, you can generate runbook templates with versioning and maintenance guidelines. The skill produces runbooks that include last-updated dates, ownership details, and rules for keeping technical documentation up to date.

To structure an API reference, establish the target audience and scope through brainstorming first. This skill then produces QA-ready API references with consistent formatting, tailored specifically for engineering teams.

Yes, the brainstorm-first approach supports the entire documentation lifecycle. It applies to maintaining existing technical documentation by enforcing scope planning, audience discovery, and versioning guidelines before updating system design documents or runbooks.