doc-coauthoring

Guide structured co-authoring of technical specs, proposals, and decision docs.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/alexajuno/dotfiles --skill doc-coauthoring-alexajuno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/alexajuno/dotfiles/tree/main/dot_claude/plugins/marketplaces/anthropic-agent-skills/skills/doc-coauthoring
Command: npx skills add https://github.com/alexajuno/dotfiles --skill doc-coauthoring-alexajuno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating structured documents like proposals, technical specifications, and decision documents, ensuring clarity and reader comprehension.

Core Features & Use Cases

  • Structured Workflow: Guides users through context gathering, iterative refinement, and reader testing.
  • Contextual Understanding: Actively asks clarifying questions to build a comprehensive understanding of the document's purpose and audience.
  • Iterative Drafting: Builds documents section by section, allowing for brainstorming, curation, and surgical edits.
  • Reader Testing: Simulates a new reader's perspective to identify ambiguities and blind spots before finalization.
  • Use Case: A product manager needs to draft a new Product Requirements Document (PRD). This Skill will help them gather all necessary context, structure the PRD logically, draft each section collaboratively, and finally test it to ensure it's clear for engineers and designers.

Quick Start

Use the doc-coauthoring skill to help write a new technical specification for a user authentication system.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
What is the best way to co-author technical documentation with a team?

Co-authoring technical documentation is streamlined through a structured workflow involving context gathering, iterative drafting, and reader testing. This ensures clarity and comprehension for documents like technical specs and proposals.

How do I write a Product Requirements Document (PRD) that is clear for engineers?

Writing a clear PRD for engineers requires gathering necessary context, structuring the document logically, drafting iteratively, and simulating a new reader's perspective to identify ambiguities before finalization.

Can I use this workflow to draft various document types like proposals and decision docs?

Yes, you can use this workflow to draft various document types. It actively supports creating structured content including technical specifications, proposals, and decision documents through section-by-section iterative drafting.

How does iterative drafting work for content creation?

Iterative drafting for content creation works by building documents section by section, which allows for targeted brainstorming, content curation, and surgical edits. This refinement process ensures the final document meets reader comprehension goals.

What is reader testing when finalizing a technical specification?

Reader testing for a technical specification is simulating a new reader's perspective to identify ambiguities and blind spots before finalization. This verification step ensures the document is comprehensible to its intended audience.