doc-coauthoring

Guide collaborative drafting of structured documents from vague ideas.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/remiconnesson/insights-garden --skill doc-coauthoring-remiconnesson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/remiconnesson/insights-garden/tree/main/.agents/skills/doc-coauthoring
Command: npx skills add https://github.com/remiconnesson/insights-garden --skill doc-coauthoring-remiconnesson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps people turn scattered context into clear, structured documents without getting stuck at the blank page. It is designed to reduce ambiguity, surface missing details early, and improve documents before others read them.

Core Features & Use Cases

  • Context Gathering: Collect background, constraints, audience, and goals before drafting begins.
  • Refinement & Structure: Build the document section by section with brainstorming, curation, and targeted edits.
  • Reader Testing: Check whether a fresh reader would understand the document, spot gaps, or find contradictions.
  • Use Case: A team lead can use this Skill to draft a decision doc, align on the right structure, and verify the final version is readable by teammates with no prior context.

Quick Start

Ask me to help co-author a proposal, spec, or decision doc using the structured workflow.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I co-author technical specs and decision docs from scattered ideas?

Co-authoring technical specs is guided through staged context gathering, section-by-section drafting, and iterative refinement to turn scattered ideas into structured decision docs.

What is the best way to structure a proposal when starting from a blank page?

The best way to structure a proposal is using a guided workflow that collects background and goals first, then builds the document section by section to reduce ambiguity and prevent blank page paralysis.

How does reader testing work for technical documentation drafts?

Reader testing for technical documentation works by simulating a fresh reader's perspective to check clarity, spot gaps, and find contradictions in the draft before others read it.

Can I use a structured workflow to draft RFCs and technical specs?

Yes, you can use this structured workflow to draft RFCs and technical specs, as it supports staged context gathering and section-by-section refinement specifically designed for substantial writing tasks.

How do I check decision docs for clarity and completeness gaps?

Checking decision docs for clarity and completeness is handled by built-in gap checking that reviews the drafted sections to surface missing details and resolve contradictions early.