smithery/igorwarzocha

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. - 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

Installation

$ npx skills add smithery/igorwarzocha --skill writing

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/igorwarzocha · top by installs.

npx skills add smithery/igorwarzocha

Browse all from smithery/igorwarzocha

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,662 B
  • docs SUMMARY.md 491 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

<instructions> <professionalcoauthoringworkflow>

<stage1context_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.

</stage1context_gathering>

<stage2refinement_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. </stage2refinement_structure>

<stage3reader_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.

</stage3reader_testing>

<guidance_tips>

  • Tone: Direct and procedural.
  • Artifacts: Use createfile for sections, strreplace for edits.
  • Quality over Speed: Each iteration MUST make meaningful improvements.

</guidance_tips>

</professionalcoauthoringworkflow> </instructions>