doc-coauthoring
Co-author documentation with structured AI guidance
也可從以下取得: 7Spade,7Spade,davila7,AstraBit-CPT,Azeem-2,ZhanlinCui,anthropics
Creating quality documentation requires iteration and fresh perspectives. This skill provides a proven three-stage workflow that transforms vague ideas into clear, reader-tested documents.
下載技能 ZIP
在 Claude 中上傳
前往 設定 → 功能 → 技能 → 上傳技能
開啟並開始使用
測試它
正在使用「doc-coauthoring」。 User wants to write a design doc for a new caching layer
預期結果:
A structured workflow begins with context questions about the caching problem, audience, and constraints. After info-dumping and clarifying questions, the document is built section-by-section (problem statement, alternatives considered, proposed approach, implementation plan) with iterative refinement. Reader testing validates the doc catches key questions before team review.
正在使用「doc-coauthoring」。 User has a draft RFC that feels incomplete
預期結果:
The workflow identifies gaps through targeted questions, brainstorms missing considerations for each section, and produces a refined RFC. Reader testing with a fresh Claude instance surfaces ambiguities that are then addressed before final publication.
安全審計
安全All static analysis findings are false positives. The 'external_commands' references are Claude Code tool calls (create_file, str_replace), not shell execution. The 'network' reference is documentation text directing users to claude.ai, not actual network calls. Cryptographic and reconnaissance patterns are text matches in documentation context only. This is a pure instructional skill with no executable security risks.
品質評分
你能建構什麼
Technical Specification Writing
Engineers creating technical specs can use this workflow to systematically capture requirements, explore alternatives, and produce reader-ready documentation that anticipates implementation questions.
Design Decision Documentation
Teams documenting architectural decisions benefit from the structured approach that captures context, explores trade-offs, and validates clarity through reader testing.
Product Requirements and Proposals
Product teams can transform rough ideas into polished PRDs by following the context gathering, refinement, and testing stages to ensure stakeholder-ready output.
試試這些提示
I need to write a technical specification for a new feature. Can you guide me through the documentation co-authoring workflow?
I have an existing design doc that needs improvement. Let's use the co-authoring workflow to refine it section by section.
My document is mostly complete. Let's do the reader testing stage to find gaps before I share it with the team.
I need to create a proposal document from scratch. Guide me through all three stages: context gathering, refinement and structure, and reader testing.
最佳實務
- Complete all three stages without skipping - each stage catches different types of issues
- Provide thorough context during stage 1 to enable better guidance in later stages
- Use reader testing feedback to identify genuine gaps rather than defending existing content
避免
- Skipping context gathering and jumping straight to drafting results in incomplete documents
- Making broad rewrites instead of surgical section-by-section refinements
- Ignoring reader testing feedback because the content seems obvious to the author