allbeingsfuture/skills@doc-coauthoring

Guides teams through a structured, stage-based doc co-authoring workflow with Context Gathering, Refinement & Structure, and Reader Testing.

9|2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill allbeingsfuture-skills-doc-coauthoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: allbeingsfuture/skills@doc-coauthoring
Source: https://github.com/AllBeingsFuture/AllBeingsFuture/tree/main/electron/embedded-assets/skills/doc-coauthoring
Command: npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill allbeingsfuture-skills-doc-coauthoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams through a structured doc co-authoring workflow to streamline collaboration on documentation tasks such as writing docs, proposals, technical specs, PRDs, RFCs, or other structured content. It helps users efficiently transfer context, refine content through iteration, and verify that the document works for readers.

Core Features & Use Cases

  • Stage-based guidance through Context Gathering, Refinement & Structure, and Reader Testing.
  • Artifact scaffolding and iterative drafting to ensure consistency and readability.
  • Triggered when users mention writing documentation, proposals, or similar tasks.

Use cases include creating technical specs, design docs, decisions docs, PRDs, RFCs, or any structured documentation where collaboration and reader readiness matter.

Quick Start

Initiate Stage 1 by offering the structured doc co-authoring workflow and guiding the user through Context Gathering.

Frequently Asked Questions about allbeingsfuture/skills@doc-coauthoring

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

FAQPage Schema
What is structured document co-authoring and when do I need it?

Document co-authoring is a stage-based workflow guiding teams through Context Gathering, Refinement & Structure, and Reader Testing. You need it for writing technical specs, PRDs, or RFCs where collaboration, clarity, and reader readiness are essential.

How do I start writing technical specs using a co-authoring workflow?

Start writing technical specs by initiating Stage 1 to guide your team through Context Gathering. The workflow applies artifact scaffolding, clarifying questions, and brainstorming to iteratively draft the document and ensure structural consistency before proceeding to refinement.

Can I use this workflow to write proposals and PRDs with my team?

Yes, you can use this workflow to write proposals and PRDs with your team. It applies stage-based guidance and iterative drafting to structured content, ensuring your proposals and PRDs achieve clarity, consistency, and reader readiness through refinement and reader testing.

What is the best way to refine and test documentation for readers?

The best way to refine and test documentation is using a structured workflow with Refinement & Structure and Reader Testing stages. This approach applies iterative drafting and artifact scaffolding to verify the document works for readers and ensures clarity and consistency.

What are the limitations of stage-based co-authoring for RFCs?

The limitations of stage-based co-authoring for RFCs include its reliance on a rigid Context Gathering, Refinement, and Reader Testing sequence. This structured process may not suit rapid, ad-hoc drafting, though it ensures thorough iteration and reader readiness for complex RFCs.