doc-coauthoring

Guide teams through staged co-authoring workflows for technical documents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SMOrchestra-ai/smorch-dist --skill doc-coauthoring-smorchestra-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/SMOrchestra-ai/smorch-dist/tree/main/plugins/smorch-design/skills/doc-coauthoring
Command: npx skills add https://github.com/SMOrchestra-ai/smorch-dist --skill doc-coauthoring-smorchestra-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps teams efficiently co-author structured documents by guiding context gathering, iterative refinement, and reader testing.

Core Features & Use Cases

  • Stage-based workflow: Context gathering, Refinement & Structure, and Reader Testing to ensure clarity and reader readiness.
  • Interactive drafting: Generates structured sections, clarifying questions, and iterative edits to align with user needs.
  • Collaboration-ready: Produces artifact scaffolds, tracks changes, and enables staged reviews for team approval.

Quick Start

Provide a document brief and begin by confirming the target audience and purpose to start Stage 1.

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 specs and design docs with a team?▼

Co-authoring technical specs and design docs is streamlined through a staged workflow that guides context gathering, iterative refinement, and reader testing. Teams use interactive drafting and artifact scaffolds to align on structured sections.

What is the best way to structure a collaborative document for reader testing?▼

Reader testing for collaborative documents is best handled by generating structured sections, clarifying questions, and iterative edits. This staged refinement ensures your proposal or decision record is clear and reader-ready.

How do we gather context before drafting a proposal or decision record?▼

Gathering context for proposals or decision records starts by providing a document brief and confirming the target audience and purpose. This triggers Stage 1, generating clarifying questions to align team input before drafting.

Can I use this workflow for both technical specs and decision records?▼

Yes, this workflow applies to technical specs, proposals, design docs, and decision records. It provides stage scaffolds and artifact-based review loops tailored to each document type across all co-authoring stages.

How does the iterative refinement stage work for team documents?▼

Iterative refinement for team documents works by applying stage scaffolds and tracking changes during structured reviews. It produces collaboration-ready artifacts that enable staged reviews for team approval.

When do I need a staged workflow for document collaboration?▼

A staged workflow for document collaboration is needed when teams require reader-ready clarity through context gathering and iterative refinement. It is ideal for technical specs and decision records demanding structured approval.