doc-coauthoring

Guides collaborative document creation through context gathering, iterative drafting, and reader testing.

3|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/ruskicoder/system-prompts --skill doc-coauthoring-ruskicoder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/ruskicoder/system-prompts/tree/main/prompt-orchestrator/.opencode/skills/doc-coauthoring
Command: npx skills add https://github.com/ruskicoder/system-prompts --skill doc-coauthoring-ruskicoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation, proposals, and technical specs alone often produces documents full of blind spots, missing context, and unclear sections that confuse readers. This Skill structures the co-authoring process so the final document actually works for its intended audience. ## Core Features & Use Cases - Three-Stage Workflow: Walks users through Context Gathering, Refinement & Structure, and Reader Testing for any substantial writing task. - Section-by-Section Drafting: Brainstorms 5-20 options per section, curates with the user, then drafts and refines through surgical edits. - Reader Testing: Validates the finished document with a fresh, context-free reviewer (sub-agent or manual test) to catch ambiguity and false assumptions before publication. - Use Case: A product manager needs to write a decision doc for a new architecture. The Skill gathers project context, builds the doc section by section, then tests whether a fresh reader can correctly answer likely questions from the document alone. ## Quick Start Ask the assistant to help you write a design doc or proposal using the structured co-authoring workflow.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I write a technical spec or design doc with AI assistance?▼

Use a structured co-authoring workflow: first dump all project context, then build the document section by section through brainstorming and curation, and finally test the draft with a fresh reader. This produces clearer specs than one-shot generation.

How to test whether my document is clear to readers?▼

Reader testing validates clarity by having a fresh reviewer with no prior context answer realistic questions using only the document. Wrong answers or confusion reveal blind spots, ambiguous passages, and assumed knowledge that need fixing.

What types of documents does this workflow support?▼

The workflow supports documentation, proposals, technical specs, decision docs, PRDs, RFCs, and similar structured content. It adapts section suggestions based on the document type and any template the user provides.

Can I use this workflow without integrations like Slack or Google Drive?▼

Yes, integrations are optional. Without them, you paste relevant context directly into the conversation, and reader testing is done manually by opening a fresh conversation and pasting the document there.

When should I skip the structured workflow and write freeform?▼

Freeform writing suits short or low-stakes content where reader testing adds little value. The structured workflow is best for substantial documents that others will rely on for decisions or implementation.