Writing
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
igorwarzocha Writing by igorwarzocha · a02068a
npx skillmds@latest add igorwarzocha/writing File contents
---name: writingdescription: 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>
igorwarzocha/opencode-workflows/tree/main/cowork/.opencode/skill/writing commit a02068ab11
Frequently asked questions
Run npx skillmds@latest add igorwarzocha/writing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
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 It is listed under Docs & Writing on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
igorwarzocha (@igorwarzocha) published this skill. Their other Agent Skills are listed on their SkillMD profile.