doc-coauthoring

Guide structured document co-authoring through context gathering, drafting, and reader testing.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/automate-me7/agent-skills --skill doc-coauthoring-automate-me7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/automate-me7/agent-skills/tree/main/doc-coauthoring
Command: npx skills add https://github.com/automate-me7/agent-skills --skill doc-coauthoring-automate-me7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative documentation is error-prone and slow; this workflow guides users to co-author docs with Claude through a three-stage process: Context Gathering, Refinement & Structure, and Reader Testing, ensuring clear ownership and verifiable quality.

Core Features & Use Cases

  • Three-stage co-authoring workflow: Context Gathering, Refinement & Structure, and Reader Testing.
  • Trigger-based onboarding: prompts for doc type (technical spec, PRD, decision doc, proposal) and audience.
  • Iterative drafting workflow: guided drafting, revision cycles, and reader verification.
  • Artifact scaffolding and templates when supported by the environment.
  • Suitable for documentation, proposals, technical specs, decision docs, and related structured content. For slide decks, see pptx. For individual marketing pages, see copywriting.

Quick Start

Initiate Stage 1 by gathering context for a new document and guide the user through Context, Refinement, and Reader Testing.

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 with Claude using a structured workflow?

To co-author technical documentation with Claude, use a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This structured approach ensures clear ownership and verifiable quality for technical specs and proposals.

What is the best way to draft a technical spec or PRD collaboratively?

The best way to draft a technical spec or PRD collaboratively is through iterative drafting cycles. Start with context gathering, refine the structure, and finish with reader verification to ensure the document meets audience needs.

Can I use this co-authoring workflow for decision docs and proposals?

Yes, you can use this co-authoring workflow for decision docs, proposals, and technical specs. It applies trigger-based onboarding to prompt for your specific document type and target audience before drafting begins.

Does the documentation workflow support artifact scaffolding and templates?

Yes, the documentation workflow supports artifact scaffolding and templates when supported by your environment. This provides structured outputs during the iterative drafting and refinement stages.

When should I not use this structured document creation workflow?

You should not use this structured document creation workflow for slide decks or individual marketing pages. It is specifically designed for documentation, proposals, technical specs, and decision docs requiring reader testing.