Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Install with Tessl CLI
npx tessl i github:boisenoise/skills-collections --skill doc-coauthoring87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 91%
↑ 1.59xAgent success when using this skill
Validation for skill structure
Context gathering workflow
Five meta-context questions
20%
100%
Shorthand encouragement
0%
100%
Info dump topic areas
10%
100%
Don't worry about organizing
0%
100%
Multiple input methods
0%
0%
Numbered clarifying questions
0%
100%
Shorthand answer format
0%
100%
Exit condition logic
30%
100%
Integration mention
0%
0%
Confirmation before search
0%
0%
Transition prompt
60%
100%
Section-by-section refinement
Six-step section workflow
50%
100%
Brainstorm range 5-20
0%
50%
Curation shorthand examples
0%
100%
Freeform feedback handling
0%
75%
Gap check step
100%
100%
Targeted edits only
100%
70%
Section suggestion
100%
100%
Section ordering by unknowns
0%
100%
First section style note
0%
50%
Three-iteration removal check
0%
62%
Placeholder scaffold creation
0%
100%
Reader testing process
Reader question generation
100%
100%
Fresh perspective testing
0%
40%
Ambiguity check
100%
100%
Assumption check
100%
100%
Contradiction check
100%
100%
Issue reporting
100%
100%
Fix recommendations
100%
100%
Readiness determination
100%
100%
Question answer evaluation
100%
100%
Sample doc issues found
100%
100%
Full workflow orchestration
Three-stage structure
100%
100%
Initial workflow offer
100%
100%
Stage transition logic
100%
100%
Skip/deviation handling
100%
100%
Frustration handling
0%
100%
Direct tone
100%
100%
Final review recommendations
100%
100%
Final tips provided
0%
100%
Near-completion review
0%
100%
Example session completeness
100%
100%
Brainstorming not in artifacts
100%
100%
Document scaffold and section ordering
Section suggestions per type
100%
100%
Unknowns-first ordering
100%
100%
Summary sections last
100%
100%
Decision doc ordering
100%
100%
Tech spec ordering
100%
100%
Placeholder content
100%
100%
User customization
100%
100%
Review checks flow
0%
100%
Review checks redundancy
0%
100%
Review checks filler
0%
100%
Markdown file output
100%
100%
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.