engineering-writing

Draft long-form engineering prose that argues a position for external readers.

6|1|Updated Apr 26, 2025
One-click install
npx skills add https://github.com/edobry/minsky --skill engineering-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineering-writing
Source: https://github.com/edobry/minsky/tree/main/.claude/skills/engineering-writing
Command: npx skills add https://github.com/edobry/minsky --skill engineering-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft long-form engineering prose that argues a clear position. It helps writers produce externally-facing technical essays that are clear, structured, and hard to misinterpret.

Core Features & Use Cases

  • Structural patterns (lead with position, justify after) to ensure a strong thesis.
  • Section-heading heuristics (sentence case, specific, opinionated) for scannable narratives.
  • Revision workflow to tighten argumentation and improve clarity.
  • Guidance for Notion-style position papers, RFCs, and architecture memos meant for external readers.

Quick Start

Use this skill to draft a long-form engineering memo that argues for a specific architectural decision.

Frequently Asked Questions about engineering-writing

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

FAQPage Schema
How do I draft an engineering memo that clearly argues an architectural decision?

Draft an engineering memo by leading with your position and justifying it afterward, ensuring a strong thesis. This approach enforces structural patterns and section heuristics to make your architecture memos clear and hard to misinterpret.

What's the best way to structure long-form technical essays for external readers?

Structure long-form technical essays using argument-first patterns and opinionated sentence-case section headings for scannability. This ensures your position papers remain focused and logically tight for external readers.

How does a revision workflow improve persuasive RFC writing?

A revision workflow improves persuasive RFC writing by systematically tightening argumentation and enhancing clarity. It enforces structural patterns that ensure your technical position is well-justified and easy to follow.

Can I use this approach for Notion position papers and architecture memos?

Yes, you can use this approach for Notion position papers and architecture memos. It provides specific guidance and heuristics tailored for externally-facing technical documents meant to argue a clear position.

When do I need an argument-first approach for engineering prose?

You need an argument-first approach for engineering prose when drafting long-form documents like RFCs and position papers. Leading with your thesis prevents misinterpretation and ensures your architectural justification remains the focal point.

What are the limitations of using structural heuristics for technical writing?

Structural heuristics for technical writing are designed for long-form, externally-facing documents arguing a specific position. They may not suit shorter internal notes or purely descriptive documentation that lacks a persuasive architectural argument.