doc-coauthoring

Guide structured co-authoring of documentation through context gathering, refinement, and reader testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured workflow for guiding users through collaborative document creation. It coordinates context gathering, iterative refinement, and reader testing to produce high-quality documentation and proposals.

Core Features & Use Cases

  • Structured workflow: Stage-based approach (Context Gathering, Refinement & Structure, Reader Testing).
  • Iterative drafting: Stepwise creation with clarifying questions, brainstorming, and refinement.
  • Reader testing prep: Includes testing with a fresh Claude to verify reader comprehension and edge cases.
  • Applicability: Useful for writing docs, proposals, technical specs, decision docs, or similar structured content.

Quick Start

Initiate Stage 1 by prompting the user to share document context and desired audience, then proceed through Context Gathering, Refinement & Structure, and Reader Testing.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
What is a structured workflow for collaborative document writing?

A structured collaborative writing workflow guides documents from initial idea to reader-tested draft through sequential stages: context gathering, iterative refinement and structure, and reader testing to verify comprehension.

How do I co-author technical specs and proposals step by step?

To co-author technical specs and proposals, start by sharing document context and audience, then proceed stepwise through brainstorming, structural refinement, and reader validation to iteratively build the final draft.

Can I test reader comprehension before finalizing documentation?

Yes, reader testing involves validating documentation with a fresh instance to verify reader comprehension and check edge cases before finalizing the draft, ensuring the content is clearly understood.

Does this coauthoring workflow support decision logs and technical specs?

This coauthoring workflow supports writing documentation, proposals, technical specs, and decision logs by enforcing a stage-based drafting process tailored to varied structured content formats.

What is the best way to iteratively refine a draft with collaborators?

The best way to iteratively refine a draft is using artifact-based collaboration, asking clarifying questions during structural refinement to resolve ambiguities and align the document with the intended audience.

When should I not use a stage-based approach for documentation?

Avoid a stage-based documentation approach when writing short, informal notes that do not require structured context gathering, iterative refinement, or formal reader testing to communicate effectively.