doc-coauthoring

Automate stage-based collaborative authoring of RFCs, ADRs, and proposals.

13|2|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/kriscard/kriscard-claude-plugins --skill doc-coauthoring-kriscard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/kriscard/kriscard-claude-plugins/tree/main/plugins/content/skills/doc-coauthoring
Command: npx skills add https://github.com/kriscard/kriscard-claude-plugins --skill doc-coauthoring-kriscard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative document authoring for RFCs, proposals, and ADRs often stalls due to context gaps, misalignment, and iterative editing overhead.

Core Features & Use Cases

  • Structured collaboration prompts: Guides context gathering with clarifying questions and edge-case exploration. Use Case: Co-create an RFC for API design with stakeholders.
  • Iterative drafting workflow: Section-by-section drafting with brainstorm → curate → draft → refine. Use Case: Produce ADRs with decision records.
  • Reader testing & validation: Predicts 5-10 reader questions and verifies clarity for readers with no context.

Quick Start

Begin a collaborative co-authoring session to shape RFCs, proposals, or ADRs from context gathering to reader-ready drafts.

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 an RFC with multiple stakeholders?

Co-authoring an RFC is automated through structured collaboration prompts that guide context gathering and edge-case exploration, enabling multiple stakeholders to align on technical governance documents.

What is the best way to write an ADR collaboratively?

Writing an ADR collaboratively uses an iterative drafting workflow with brainstorm, curate, draft, and refine stages, ensuring decision records are produced systematically section by section.

How does collaborative technical document drafting handle context gaps?

Collaborative technical document drafting handles context gaps by applying clarifying questions during initial context gathering to ensure all stakeholders align before iterative drafting begins.

Can I validate proposal clarity for readers with no prior context?

Yes, you can validate proposal clarity through reader testing that predicts five to ten potential reader questions and verifies the document is understandable for readers lacking background context.

Does the collaborative drafting workflow support stage-based proposal creation?

The collaborative drafting workflow supports stage-based proposal creation by moving sequentially from context gathering through iterative section drafting to final reader-ready validation.

What are the limitations of automated co-authoring for technical governance documents?

Automated co-authoring for technical governance documents requires a structured, stage-based workflow, meaning it is designed specifically for RFCs, ADRs, and proposals rather than freeform documentation.