tech-doc-writer

Name: tech-doc-writer
Availability: InStock
Author: prathmesh2000

Produce audience-focused technical documentation from brainstormed scope.

1|Updated Mar 4, 2026

Search Tags:#brainstorming #ADR #runbook #developer-guides #system-design #technical-docs

Ready to run

npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill tech-doc-writer-prathmesh2000

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-doc-writer
Source: https://github.com/Prathmesh2000/cursor_agent-orchestrator/tree/main/agent-system/skills/tech-doc-writer
Command: npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill tech-doc-writer-prathmesh2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates high-quality, engineer-facing technical documentation by enforcing a brainstorm-first approach to identify audience, scope, and depth before writing.

Core Features & Use Cases

Brainstorm-First Protocol: prompts for audience, scope, and accuracy before drafting any document.
Document Templates: System Design Documents, Architecture Decision Records (ADRs), API references, runbooks, and developer guides.
Versioning and Maintenance: guidelines for last-updated dates, ownership, and keeping docs up to date.

Quick Start

Provide a topic and audience and this skill will brainstorm the scope before producing the requested document.

Frequently Asked Questions about tech-doc-writer

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

FAQPage Schema

How do I write an Architecture Decision Record for a new system design?▼

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.

What is the best way to create audience-focused developer guides from brainstormed scope?▼

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.

Can I generate a runbook template that includes versioning and maintenance guidelines?▼

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.

How do I structure an API reference document for engineering teams?▼

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.

Does this brainstorm-first approach work for maintaining existing technical documentation?▼

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.