doc-coauthoring-for-reviewers

Sub-skill of doc-coauthoring: For Reviewers (+2).

5 stars

Best use case

doc-coauthoring-for-reviewers is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of doc-coauthoring: For Reviewers (+2).

Teams using doc-coauthoring-for-reviewers should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/for-reviewers/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/business/communication/doc-coauthoring/for-reviewers/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/for-reviewers/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How doc-coauthoring-for-reviewers Compares

Feature / Agent	doc-coauthoring-for-reviewers	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Sub-skill of doc-coauthoring: For Reviewers (+2).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# For Reviewers (+2)

## For Reviewers


1. **Be specific**: Point to exact text, not vague areas
2. **Be constructive**: Offer solutions, not just problems
3. **Prioritize**: Distinguish critical from nice-to-have
4. **Explain reasoning**: Help author learn and decide
5. **Respect voice**: Preserve author's style where appropriate


## For Authors


1. **Consider all feedback**: Even if not accepting
2. **Ask clarifying questions**: Before dismissing suggestions
3. **Track decisions**: Note why changes were accepted/rejected
4. **Thank reviewers**: Acknowledge contribution


## For Both


1. **Agree on process**: Establish review expectations upfront
2. **Set timelines**: Clear deadlines for each review round
3. **Use consistent tools**: Same markup/format for all feedback
4. **Communicate changes**: Notify when versions are ready

Related Skills

doc-coauthoring

from vamseeachanta/workspace-hub

Collaborate on documents with tracked changes, suggestions, and iterative refinement. Use for reviewing drafts, providing editorial feedback, and collaborative document development.