doc-coauthoring

Name: doc-coauthoring
Availability: InStock
Author: simorgh3196

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

1|Updated May 29, 2026

Search Tags:#workflow #documentation #collaboration #context gathering #co-authoring #reader testing

Ready to run

npx skills add https://github.com/simorgh3196/tsuzulint --skill doc-coauthoring-simorgh3196

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/simorgh3196/tsuzulint/tree/main/.agents/skills/doc-coauthoring
Command: npx skills add https://github.com/simorgh3196/tsuzulint --skill doc-coauthoring-simorgh3196

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users through a structured co-authoring workflow to produce high-quality documentation.

Core Features & Use Cases

Context Gathering: Collect essential context and clarifying questions at the start to align goals, audience, and success criteria.
Refinement & Structure: Iteratively draft sections, brainstorm options, and converge on a clear document structure.
Reader Testing: Validate the document with a fresh reader perspective to surface ambiguities, gaps, or assumptions.
Artifact-Driven Collaboration: Use shared artifacts or files to track progress, enable collaboration, and maintain version history.

Quick Start

Initiate the workflow by offering the three-stage co-authoring process to a user writing a document; proceed to Stage 1: Context Gathering, then Stage 2, and finally Stage 3 for reader testing.

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 documentation using a structured workflow?▼

To co-author technical documentation, this skill organizes collaboration into three structured stages: Context Gathering, Refinement & Structure, and Reader Testing. It uses staged prompts and iterative drafting to ensure reader-ready outputs.

What is the best way to gather context when writing a proposal or decision doc?▼

The best way to gather context for proposals or decision docs is starting with Stage 1 of this co-authoring workflow. It collects essential context and clarifying questions upfront to align goals, audience, and success criteria before drafting begins.

Can I use an iterative drafting process to refine and structure a technical spec?▼

Yes, you can iteratively draft and refine a technical spec during Stage 2: Refinement & Structure. This stage helps brainstorm options and converge on a clear document structure through artifact-based collaboration.

How does reader testing validate assumptions in a drafted document?▼

Reader testing validates a drafted document by applying a fresh reader perspective during Stage 3. This process surfaces ambiguities, gaps, or assumptions to ensure the final documentation is reader-ready.

Do I need shared artifacts to track version history during document collaboration?▼

Yes, shared artifacts are used to track progress, enable collaboration, and maintain version history. This artifact-driven approach ensures structured co-authoring throughout the documentation workflow.

Does this co-authoring workflow apply to writing proposals and technical specs?▼

Yes, this co-authoring workflow applies to writing documentation, proposals, technical specs, and decision docs. It enforces a disciplined process with staged prompts to produce reader-ready outputs across various document types.