doc-coauthoring

Guide users through a three-stage co-authoring workflow for structured documentation.

8|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kensaurus/cursor-kenji --skill doc-coauthoring-kensaurus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/kensaurus/cursor-kenji/tree/main/skills/doc-coauthoring
Command: npx skills add https://github.com/kensaurus/cursor-kenji --skill doc-coauthoring-kensaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide users through a structured, repeatable workflow to co-author documentation such as proposals, technical specs, decision docs, PRDs, RFCs, ADRs, READMEs, and other artifacts.

Core Features & Use Cases

The skill provides a three-stage process (Context Gathering, Refinement & Structure, Reader Testing) to drive collaborative writing, ensure alignment, and surface gaps before publication. It supports stage-specific prompts, brainstorming of options, and iterative drafting to produce clear, well-structured documents across teams.

Quick Start

Start with Context Gathering to collect context and goals.

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 documentation like RFCs and PRDs with a structured workflow?

Co-authoring technical documentation like RFCs and PRDs involves a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This process applies stage-specific prompts and iterative drafting to align teams and surface gaps before publication.

What is the best way to structure a decision document or ADR before publication?

The best way to structure a decision document or ADR is through iterative drafting within a structured co-authoring workflow. This approach uses stage-specific prompts and brainstorming options to ensure alignment and surface gaps before publication.

How does a structured co-authoring workflow improve proposal writing?

A structured co-authoring workflow improves proposal writing by driving collaborative creation through three defined stages. It enforces strict guardrails and templates, ensuring alignment and surfacing structural gaps early in the drafting process.

Can I use templates for writing technical specifications and READMEs collaboratively?

Yes, you can use templates for collaboratively writing technical specifications and READMEs. The co-authoring process applies strict templates and stage-specific prompts to guide iterative drafting across teams.

What are the limitations of using a stage-based workflow for collaborative writing?

The limitation of a stage-based collaborative writing workflow is that it enforces strict guardrails and requires completing sequential stages—Context Gathering, Refinement, and Reader Testing—which may restrict highly unstructured or spontaneous drafting approaches.