Tech Writer

Generate API docs, ADRs, and governance documents from code changes.

1|Updated Jul 8, 2016
One-click install
npx skills add https://github.com/oehm-smith/linux-env --skill tech-writer-oehm-smith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Tech Writer
Source: https://github.com/oehm-smith/linux-env/tree/main/HOME/.claude/skills/crosscutting/quality/documentation
Command: npx skills add https://github.com/oehm-smith/linux-env --skill tech-writer-oehm-smith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical documentation often falls out of sync with the codebase, leading to confusing API references, governance gaps, and ADRs that no longer reflect decisions.

Core Features & Use Cases

  • Synchronizes API documentation with changes in implementation.
  • Generates Architecture Decision Records (ADRs) and governance documents to reflect current architecture and policies.
  • Maintains consistency across API docs, ADRs, and governance materials for teams seeking reliable references.

Quick Start

Review recent code changes and generate updated API docs, ADRs, and governance docs to reflect the latest decisions.

Frequently Asked Questions about Tech Writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep API documentation aligned with code changes?

To keep API documentation aligned with code changes, you synchronize API references with implementation updates. This ensures technical docs reflect current architecture and maintain consistency across governance materials.

What is an ADR and when do I need to generate one?

An ADR is an Architecture Decision Record that captures architectural decisions. You need to generate ADRs when architectural changes occur, ensuring decisions are traceable and governance docs reflect current policies.

How do I generate governance documents and ADRs from recent code updates?

You generate governance documents and ADRs by reviewing recent code changes and producing updated records. This creates versioned governance templates and ADRs with traceable references reflecting the latest decisions.

Does this approach support frontmatter-driven documentation and versioned updates?

Yes, this approach supports frontmatter-driven documentation and versioned updates. It manages frontmatter metadata within docs and maintains versioned updates with traceable references across projects.

What's the best way to maintain consistency across API docs and governance artifacts?

The best way to maintain consistency across API docs and governance artifacts is to synchronize documentation with implementation changes. This generates aligned ADRs and governance templates, ensuring reliable references for teams.

Why does technical documentation fall out of sync with the codebase?

Technical documentation falls out of sync with the codebase when updates are manual and disconnected from implementation. Synchronizing API docs, ADRs, and governance materials with code changes prevents confusing references.