doc-coauthoring

Guide teams through a structured document creation workflow from context gathering to reader testing.

2|1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/silentbalanceyh/r2mo-lain --skill doc-coauthoring-silentbalanceyh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/silentbalanceyh/r2mo-lain/tree/main/.trae/skills/doc-coauthoring
Command: npx skills add https://github.com/silentbalanceyh/r2mo-lain --skill doc-coauthoring-silentbalanceyh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative document creation often suffers from misalignment, scope creep, and fragmented feedback. This skill provides a structured workflow to guide users from context gathering through refinement and structure to reader testing, ensuring clear, reader-ready documents.

Core Features & Use Cases

  • Context Gathering: Collect relevant background, goals, and constraints from stakeholders.
  • Refinement & Structure: Iteratively craft sections, organize content, and align on tone and requirements.
  • Reader Testing: Validate the document with a fresh perspective to surface ambiguities and gaps. Use Case: Teams drafting technical specs, proposals, or design decisions can leverage this workflow to produce coherent, review-ready documents.

Quick Start

Initiate Stage 1 by gathering all relevant context and asking clarifying questions.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I manage stakeholder feedback and prevent scope creep during collaborative document creation?

Collaborative document creation requires a structured workflow starting with Context Gathering to collect goals and constraints from stakeholders, preventing scope creep and fragmented feedback through controlled iterative refinement.

What is the best way to structure a technical spec co-authoring workflow?

Technical spec co-authoring benefits from a three-stage workflow: Context Gathering, Refinement & Structure for iterative section crafting, and Reader Testing to validate clarity with a fresh perspective.

How do I guide a team through drafting proposals from context gathering to reader testing?

Drafting proposals involves guiding teams through three stages: gathering background and constraints, iteratively refining structure and tone, and conducting reader testing to surface ambiguities and gaps.

Does this documentation workflow support scaffolding scripts and reference directories?

The documentation workflow supports optional artifact scaffolding, allowing teams to create dedicated directories for scripts, references, and assets to support collaborative doc creation.

Can I use structured placeholders for controlled iteration when writing decision records?

Writing decision records uses explicit frontmatter requirements and controlled iteration via placeholders, ensuring teams align on content structure and requirements before finalizing drafts.

When should I not use a multi-stage editorial workflow for content design?

A multi-stage editorial workflow for content design is unnecessary for simple, single-author documents, as it enforces explicit frontmatter, stakeholder context gathering, and reader testing stages that add overhead to straightforward writing tasks.