Writing
- 92 installs
- 125 repo stars
- Updated February 4, 2026
- igorwarzocha/opencode-workflows
Co-author professional documents like proposals, specs, and RFCs through a gather, refine, and reader-test workflow.
About
A skill for structured collaborative drafting of professional documentation. A developer uses it to gather context, iteratively refine sections with surgical edits, and reader-test the draft with sub-agents.
- Three stages: context gathering, refinement structure, reader testing
- Brainstorm-then-curate per section; sub-agent reader testing
Writing by the numbers
- 92 all-time installs (skills.sh)
- +3 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #662 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/igorwarzocha/opencode-workflows --skill writingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 92 |
|---|---|
| repo stars | ★ 125 |
| Last updated | February 4, 2026 |
| Repository | igorwarzocha/opencode-workflows ↗ |
What it does
Co-author professional documents like proposals, specs, and RFCs through a gather, refine, and reader-test workflow.
Files
<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_filefor sections,str_replacefor edits. - Quality over Speed: Each iteration MUST make meaningful improvements.
</guidance_tips>
</professional_coauthoring_workflow> </instructions>
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71