technical-writing

Draft, rewrite, and review decision-ready technical documents for specific audiences.

7|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/AndurilCode/craftwork --skill technical-writing-andurilcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-writing
Source: https://github.com/AndurilCode/craftwork/tree/main/plugins/craftwork-professional/skills/technical-writing
Command: npx skills add https://github.com/AndurilCode/craftwork --skill technical-writing-andurilcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical writing often fails because readers skim, details overwhelm the decision, and documents don’t match the audience’s attention and depth needs.

Core Features & Use Cases

  • Audience- and purpose-driven drafting: Classifies common technical document types (RFCs, ADRs, one-pagers, runbooks, postmortems, announcements, PR descriptions, Slack/async) and aligns structure to the reader’s decision or action.
  • Decision-first clarity: Forces a single “key sentence” (opening/TL;DR) that states the conclusion in a way that remains understandable with zero additional context.
  • Depth calibration and compression: Applies three laws (lead with the point, write less, match depth to audience size) to reduce ceremony and remove non-decision context.
  • Template-first execution: Preserves user-provided templates, applies the Three Laws within sections, and flags gaps as suggestions rather than inventing structure.
  • Review readiness: Includes checklist-style review checks (first-sentence test, so-what test, stranger test, compression test, decision test) to improve usefulness for real stakeholders.

Quick Start

Ask the skill to rewrite your draft as a decision-ready technical document by using the appropriate template type and applying the three writing laws for your target audience.

Frequently Asked Questions about technical-writing

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

FAQPage Schema
How do I write an RFC or design doc that gets approved faster?

To write an RFC that gets approved faster, lead with a single key sentence stating the conclusion so readers understand the decision with zero context. Calibrate depth to audience attention and remove non-decision context.

What is the best way to structure a technical postmortem?

The best way to structure a technical postmortem is to apply a template-first approach that preserves your structure while flagging gaps as suggestions. Lead with the main conclusion and match detail to the audience's needs.

Can I use my existing templates for ADRs and runbooks?

Yes, you can use your existing templates for ADRs and runbooks. The process preserves your provided templates and applies compression laws within sections rather than inventing new structure.

How do I review a technical document for audience clarity?

You review a technical document for audience clarity by running checklist tests like the first-sentence, so-what, stranger, and decision tests. These checks ensure the document remains useful for real stakeholders.

Why does my technical writing fail to drive decisions?

Your technical writing fails to drive decisions when details overwhelm the conclusion and documents don’t match the audience's depth needs. Fix this by leading with the point and writing less to reduce ceremony.