Agent skill
doc-coauthoring
문서 작성, 문서화, 문서, 스펙 작성, 기술 문서, 제안서, RFC, 설계 문서, 의사결정 문서 - Collaborative document co-authoring through 3 stages: context gathering, iterative refinement, and reader testing. Use when writing docs, proposals, tech specs, decision docs, or RFCs. Do NOT use for PRD/product requirements (use prd-strategist) or implementation plans (use writing-plans).
Install this agent skill to your Project
npx add-skill https://github.com/aimskr/aims-claude-toolkit/tree/main/skills/doc-coauthoring
Metadata
Additional technical details for this skill
- author
- jaehashin
- version
- 1.2.0
SKILL.md
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.
Completion
Stage 3 Reader Testing을 통과하고 최종 문서가 사용자 승인을 받으면 완료.
Troubleshooting
User dumps a wall of text with no structure: Start Stage 1 — ask meta-context questions to organize their input into sections before attempting to structure. User wants to skip straight to writing: Confirm they have audience and purpose clear. If yes, jump to Stage 2 with their existing outline. If no, brief Stage 1. Reader testing reveals fundamental gaps: Don't patch — return to Stage 2 for the affected section. Rewrite based on new understanding.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
build-error-resolver
빌드 에러, 빌드 오류, 컴파일 에러, 빌드 실패 해결, 의존성 에러 - Specialized in resolving build errors, compilation failures, and dependency issues. Use when build fails, compilation errors occur, or dependency conflicts arise. Do NOT use for runtime bugs or logic errors (use debug-specialist instead).
brainstorming
브레인스토밍, 아이디어, 기획, 구상, 아이디어회의, 설계, 요구사항 분석, 접근법 탐색 - Use before creating new features or significant changes to explore user intent, requirements, and design options. Collaborative brainstorming through step-by-step questioning. Do NOT use for simple bug fixes, config changes, or tasks with clear requirements already defined.
testing-strategy
테스트 전략, 테스팅 계획, QA 전략, 품질 보증, 테스트 피라미드, 테스트 시나리오, 커버리지 목표 - Designs test strategies including test pyramid ratios, scenario categories, and coverage targets. Use when planning how to test a feature, designing QA approach, or creating test plans. Do NOT use for TDD implementation (use tdd-workflow) or E2E test execution (use e2e-runner).
learning-research
학습 리서치, 학습 자료, 공부 자료, 학습, 공부, 스터디, 개념 정리, 이해 - 특정 주제를 깊이 이해하기 위한 학습 자료를 수집·정리한다. 병렬 전문가 서브에이전트로 개념, 원리, 실습, 심화 자료를 수집하고 이해도별로 체계화된 학습 노트를 생성한다. Obsidian vault에 자동 저장. 의사결정용 자료 조사는 research 스킬을, 시장조사는 market-research 스킬을 사용할 것.
devil-advocate
ui-ux-design
UI, UX, 디자인, UI 디자인, UX 디자인, 사용자 경험, 화면, 인터랙션, 라이브 리뷰, 와이어프레임, 화면 설계 - Create and review UI/UX designs with live browser testing. Use for design implementation, interaction testing, visual inspection, and iterative refinement with Playwright. Also triggered when continuing from prd-strategist's Design Direction output.
Didn't find tool you were looking for?