AgentSkillsCN

writing

在专业文档的结构化协作编写中，可灵活运用此方法。在撰写提案、技术规格说明书，以及 RFC 文档时，当需要经历“收集→精炼→测试”的协作起草流程时，应主动展开相关工作。 示例： - 用户：“为新 API 草拟一份技术 RFC” → 遵循第一阶段的背景信息收集流程 - 用户：“对这份提案的引言部分进行精炼” → 采用迭代式的精细修改 - 用户：“测试这份文档是否易于读者理解” → 运行读者测试工作流

SKILL.md
--- frontmatter
name: writing
description: |-
  Handle structured co-authoring of professional documentation. Use for proposals, technical specs, and RFCs. Use proactively when a collaborative drafting process (Gathering -> Refinement -> Testing) is needed.
  
  Examples:
  - user: "Draft a technical RFC for the new API" -> follow Stage 1 context gathering
  - user: "Refine the introduction of this proposal" -> use iterative surgical edits
  - user: "Test if this document is clear for readers" -> run reader testing workflow
<instructions> <professional_coauthoring_workflow>

<stage_1_context_gathering>

  1. •Ask for meta-context (type, audience, impact, constraints).
  2. •Encourage a context dump (background, discussions, stakeholders).
  3. •Ask 5-10 clarifying questions to close the gap. </stage_1_context_gathering>

<stage_2_refinement_structure>

  1. •Create initial document structure with placeholders.
  2. •For each section:
    • •Ask clarifying questions.
    • •Brainstorm 5-20 options.
    • •Curation (User selects/combines).
    • •Draft the section using surgical edits.
    • •Iteratively refine based on feedback. </stage_2_refinement_structure>

<stage_3_reader_testing>

  1. •Predict reader questions.
  2. •Invoke sub-agents (Reader Claude) with just the doc and questions.
  3. •Check for ambiguity, false assumptions, or contradictions.
  4. •Report findings and fix gaps. </stage_3_reader_testing>

<guidance_tips>

  • •Tone: Direct and procedural.
  • •Artifacts: Use create_file for sections, str_replace for edits.
  • •Quality over Speed: Each iteration MUST make meaningful improvements. </guidance_tips>

</professional_coauthoring_workflow> </instructions>