doc-coauthoring

no response text, returning binary only for efficiency. Actually returning JSON.

1|Updated Aug 25, 2024
One-click install
npx skills add https://github.com/7loro/dotfiles --skill doc-coauthoring-7loro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/7loro/dotfiles/tree/main/dot_config/agents/skills/doc-coauthoring
Command: npx skills add https://github.com/7loro/dotfiles --skill doc-coauthoring-7loro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users through a structured, stage-based workflow for collaborative documentation, reducing back-and-forth and ensuring reader-ready output.

Core Features & Use Cases

  • Stage-based workflow: Context Gathering, Refinement & Structure, and Reader Testing to manage writing projects end-to-end.
  • Guided questions and prompts that surface gaps, constraints, and audience needs.
  • Artifact scaffolding: creates skeleton drafts and checklists to accelerate drafting and reviews.
  • Collaboration support: aligns multiple contributors with clear handoffs and iteration loops.
  • Use Cases: technical specs, proposals, decision docs, design docs, and other structured documents.

Quick Start

Initiate the co-authoring workflow by asking your AI to guide you through the three stages: Context Gathering, Refinement & Structure, and Reader Testing. Then respond to the initial questions to surface context, draft sections, and validate readability with a reader test. For example: "doc-coauthoring: start Stage 1" or "doc-coauthoring: draft a proposal using the Stage 2 workflow."

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 proposals with a structured documentation workflow?

To co-author technical specs and proposals, use a stage-based documentation workflow that guides contributors through Context Gathering, Refinement & Structure, and Reader Testing to reduce back-and-forth and ensure reader-ready output.

What is the best way to manage collaborative writing for design docs across multiple contributors?

The best way to manage collaborative writing for design docs is using a guided workflow with interactive questions and artifact scaffolding, which aligns multiple contributors through clear handoffs and iteration loops.

How do I ensure readers understand the final version of my decision documents?

To ensure readers understand decision documents, apply a Reader Testing stage at the end of the documentation workflow to validate readability and confirm the audience comprehends the final output.

Can I use this co-authoring workflow for general documentation projects without any dependencies?

Yes, you can use this co-authoring workflow for general documentation projects without dependencies, as it operates independently to guide context gathering, structure refinement, and reader testing.

What are the stages in a stage-based process for drafting and reviewing documentation?

The stages in a stage-based process for drafting and reviewing documentation are Context Gathering, Refinement & Structure, and Reader Testing, which collectively manage writing projects end-to-end.

How do I start the co-authoring workflow to draft a proposal?

To start the co-authoring workflow to draft a proposal, initiate the process and respond to the initial guided questions to surface context, draft sections using artifact scaffolding, and validate readability.