doc-coauthoring

Guide structured co-authoring workflows for technical documents with staged drafting and testing.

Updated Nov 28, 2025
One-click install
npx skills add https://github.com/SoftSystemsStudio/Soft-Systems-Studio --skill doc-coauthoring-softsystemsstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/SoftSystemsStudio/Soft-Systems-Studio/tree/main/.claude/skills/doc-coauthoring
Command: npx skills add https://github.com/SoftSystemsStudio/Soft-Systems-Studio --skill doc-coauthoring-softsystemsstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, stage-based approach to collaborative document creation, helping teams write clear, reader-tested docs with fewer iterations.

Core Features & Use Cases

  • Context Gathering: collects goals, audience, constraints, and context through guided questions.
  • Refinement & Structure: iteratively builds sections and organizes content with stakeholder feedback.
  • Reader Testing: validates the document with a fresh reviewer to uncover gaps and ambiguities.
  • Use Cases: ideal for technical specs, proposals, design docs, PRDs, decision records, and other structured documents.

Quick Start

Start co-authoring by describing the target document (type, audience, impact) and prompting the assistant to begin Stage 1: Context Gathering. The assistant will guide you through questions, structure, and testing phases.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I structure collaborative documentation across multiple stakeholders?

Structured collaborative documentation follows a three-stage workflow: context gathering for goals and audience, iterative refinement for section organization, and reader testing to validate clarity with fresh reviewers.

What is the best way to write technical specs that pass reader testing?

Reader testing for technical specs involves validating the drafted document with a fresh reviewer to uncover gaps and ambiguities, ensuring the structured content is clear before finalizing the proposal.

How do I start co-authoring a design doc or PRD with guided questions?

Start co-authoring a design doc or PRD by describing the target document type, audience, and impact, which triggers guided context gathering questions to collect goals and constraints.

Can I use a structured workflow for decision records and team proposals?

Structured workflows support decision records and team proposals by enforcing iterative drafting with stakeholder feedback, organizing content into clear sections through refinement stages.

Does structured writing help reduce iterations on technical documentation?

Structured writing reduces iterations on technical documentation by applying stage-based co-authoring that gathers context upfront and tests documents with readers, catching ambiguities early.

When do I need a stage-based approach for documentation procedures?

A stage-based approach for documentation procedures is needed when producing high-quality structured documents like specs or design docs that require explicit artifacts and stakeholder alignment.