doc-coauthoring

Guide document co-authors through context gathering, section drafting, and reader testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill replaces aimless doc drafting with a deliberate co-authoring workflow that collects context, refines sections, and validates the result before sharing.

Core Features & Use Cases

  • Context Gathering: Promptly pulls in audience, impact, constraints, templates, and related docs while collecting clarifying questions.
  • Refinement & Structure: Builds a section-by-section scaffold, brainstorms options, curates priorities, and iteratively drafts each part with surgical edits.
  • Reader Testing: Runs a fresh reader test to predict questions, surface ambiguities, and ensure the document communicates clearly to people unfamiliar with the background.
  • Use Case: A product team drafting a decision doc can use this skill to gather stakeholder context, craft each argument with the right drafts, and prove the doc stands up to fresh scrutiny before review.

Quick Start

Ask the skill to guide you through context gathering, section drafting, and reader testing for your next proposal.

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 a technical proposal with structured AI guidance?

To co-author a technical proposal, this skill guides your team through a structured workflow that gathers context, drafts sections iteratively, and runs reader testing to ensure shared clarity before publishing.

What is the best way to gather context for a decision doc?

The best way to gather context for a decision doc is using a structured co-authoring workflow that actively pulls in audience details, constraints, and related artifacts while collecting clarifying questions to surface missing information.

How do I test if a specification document makes sense to a fresh reader?

To test if a specification document makes sense to a fresh reader, this skill runs a dedicated reader testing stage that predicts external questions, surfaces ambiguities, and validates that the doc communicates clearly.

Can I use this structured workflow for drafting product specs with multiple stakeholders?

Yes, you can use this structured workflow for drafting product specs with multiple stakeholders. It is designed to collect stakeholder context, refine arguments section-by-section, and prove the doc stands up to scrutiny before review.

Does collaborative documentation benefit from section-level curation?

Collaborative documentation benefits significantly from section-level curation. This approach builds a section-by-section scaffold, brainstorms options, and applies surgical edits to iteratively draft each part to catch blind spots.

When should I avoid aimless doc drafting for team proposals?

You should avoid aimless doc drafting for team proposals whenever you need shared clarity before publishing. Replacing it with a deliberate co-authoring workflow ensures iterative refinement and reader testing catch blind spots early.