doc-coauthoring

Guide a three-stage workflow for collaborative documentation drafting and validation.

20|4|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/Alenryuichi/openmemory-plus --skill doc-coauthoring-alenryuichi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/Alenryuichi/openmemory-plus/tree/main/.augment/skills/doc-coauthoring
Command: npx skills add https://github.com/Alenryuichi/openmemory-plus --skill doc-coauthoring-alenryuichi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative documentation often suffers from misaligned context, fragmented drafting, and late-stage reader validation. This skill provides a disciplined, three-stage workflow to align stakeholders, streamline content creation, and verify readability before publication.

Core Features & Use Cases

  • Guided three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing to coordinate input, iteration, and validation.
  • Triggered when drafting docs: technical specs, proposals, design docs, decision records, or similar structured documents; supports iterative editing with explicit feedback loops.
  • Artifact-enabled drafting process: creates structured scaffolds, prompts clarifying questions, and records decisions to improve clarity and traceability.

Quick Start

Initiate the Doc Co-Authoring workflow and start Stage 1 by answering the initial Context Gathering questions.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
What is the best way to manage collaborative documentation and align stakeholder context?

Collaborative documentation requires a three-stage workflow: context gathering, structured drafting, and reader validation to align stakeholders, streamline content creation, and verify readability before publication.

How do I draft technical specifications and proposals with iterative editing?

Drafting technical specifications and proposals uses a guided workflow that prompts clarifying questions, creates structured scaffolds, and records decisions to support iterative editing with explicit feedback loops.

How does reader testing work for decision records and design docs?

Reader testing for decision records and design docs validates readability by guiding a controlled workflow stage where readers provide explicit feedback before publication, ensuring clarity and traceability.

Can I use this workflow for structured documents like decision records and technical specs?

Yes, this workflow applies to writing structured documents including technical specs, proposals, design docs, and decision records, supporting staged workflows and iterative refinement throughout the drafting process.

Why does my team's collaborative drafting process suffer from late-stage reader validation?

Collaborative drafting often suffers from late-stage validation because fragmented drafting misaligns context, requiring a disciplined three-stage workflow to gather input, iterate, and validate readers earlier.