doc-coauthoring
문서 작성, 문서화, 문서, 스펙 작성, 기술 문서, 제안서 - Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content.
When & Why to Use This Skill
The Doc Co-Authoring skill provides a highly structured, three-stage workflow designed for collaborative document creation. It excels at transforming raw ideas into polished technical specifications, proposals, and decision documents by guiding users through deep context gathering, iterative section-by-section refinement, and rigorous reader-perspective testing to ensure clarity and impact.
Use Cases
- Case 1: Drafting comprehensive Product Requirement Documents (PRDs) or technical design docs (RFCs) by identifying edge cases and architectural trade-offs.
- Case 2: Developing professional business proposals or decision documents through a guided brainstorming and curation process.
- Case 3: Refining complex technical documentation using surgical edits to improve readability without losing the original context.
- Case 4: Quality-checking existing drafts by simulating reader questions and testing for ambiguity or logical contradictions.
| name | doc-coauthoring |
|---|---|
| description | "문서 작성, 문서화, 문서, 스펙 작성, 기술 문서, 제안서 - Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content." |
| allowed-tools | Read, Write, Edit, Grep, Glob |
Doc Co-Authoring Workflow
Guide users through collaborative document creation via three stages.
When to Offer This Workflow
Trigger conditions:
- User mentions writing documentation: "write a doc", "draft a proposal", "create a spec"
- User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC"
- User seems to be starting a substantial writing task
The Three Stages
Stage 1: Context Gathering
- Ask meta-context questions (doc type, audience, desired impact)
- Encourage info dumping (background, discussions, constraints)
- Ask 5-10 clarifying questions to close knowledge gaps
- Exit when: Edge cases and trade-offs can be discussed without needing basics
Stage 2: Refinement & Structure
For each section:
- Ask clarifying questions
- Brainstorm 5-20 options
- User curates (keep/remove/combine)
- Draft the section
- Iterative refinement via
str_replace
Section order: Start with most unknowns, leave summary for last
Stage 3: Reader Testing
- Predict 5-10 reader questions
- Test with fresh Claude (sub-agent or new session)
- Check for ambiguity, assumptions, contradictions
- Fix any gaps found
Key Principles
- One question at a time - Don't overwhelm
- Surgical edits - Use
str_replace, never reprint whole doc - Quality over speed - Each iteration should improve meaningfully
- User agency - Let them skip or adjust the process
Detailed Reference
For complete stage instructions, tips, and handling edge cases:
Read REFERENCE.md in this skill directory when needed.