doc-coauthoring

Generate Architectural Decision Records from structured inputs with Markdown outputs.

1|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/abdullah1854/ClaudeSuperSkills --skill doc-coauthoring-abdullah1854
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/abdullah1854/ClaudeSuperSkills/tree/main/doc-coauthoring
Command: npx skills add https://github.com/abdullah1854/ClaudeSuperSkills --skill doc-coauthoring-abdullah1854

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative document writing often suffers from misalignment, scattered notes, and inconsistent structure. This Skill guides co-authoring with a three-stage workflow to ensure clarity, alignment, and quality across all sections of your documentation.

Core Features & Use Cases

  • Three-stage drafting workflow: Context gathering, section-by-section drafting, and reader testing.
  • Template-driven outputs: ADRs, RFCs, design docs, and user guides with a consistent voice.
  • Use Case: When multiple stakeholders must contribute to an RFC, this Skill orchestrates the process end-to-end, reducing back-and-forth and rework.

Quick Start

Prompt Claude to draft a design doc for a new feature, including audience, goal, decisions, and constraints.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I create architectural decision records for my project?

ADRs document project decisions with structured context, reasoning, and consequences. This Skill generates ADRs from your inputs—title, context, decision, and status—auto-numbering them and rendering Markdown outputs ready for versioned governance and team review.

What's the best way to co-author design documentation with multiple stakeholders?

Co-authoring design docs benefits from structured workflow and templates to prevent misalignment and scattered notes. This Skill guides three-stage drafting—context gathering, section-by-section writing, and reader testing—producing consistent design docs, RFCs, and ADRs across contributors.

How do I ensure consistency across team-written documentation like RFCs and design docs?

Template-driven outputs enforce consistent structure and voice across collaborative docs. This Skill applies predefined templates for ADRs, RFCs, design docs, and user guides, reducing back-and-forth rework by orchestrating the drafting workflow end-to-end.

Can I automate numbering and metadata for architectural decision records?

Yes. This Skill auto-numbers ADRs sequentially and injects metadata like title, date, and status into Markdown outputs, eliminating manual versioning and enabling REST and MCP gateway API access to your generated records.

What information should I include when drafting a design document?

Effective design docs capture audience, goal, decisions, and constraints. This Skill prompts you to gather these inputs and structures them into sections—context, decision, consequences, alternatives, status, and references—ensuring completeness for stakeholder alignment.