doc coauthoring

Documentation Community

Skill notes

When to Offer This Workflow

Trigger conditions: User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up" User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC" User seems to be starting a substantial writing task Initial offer:

Stage 1: Context Gathering

Goal: Close the gap between what the user knows and what Claude knows, enabling smart guidance later.

Initial Questions

Start by asking the user for meta-context about the document: What type of document is this? (e.g., technical spec, decision doc, proposal) Who's the primary audience? What's the desired impact when someone reads this? Is there a template or specific format to follow?

Info Dumping

Once initial questions are answered, encourage the user to dump all the context they have. Request information such as: Background on the project/problem Related team discussions or shared documents Why alternative solutions aren't being used Organizational context (team dynamics, past incidents, politics)

Stage 2: Refinement & Structure

Goal: Build the document section by section through brainstorming, curation, and iterative refinement. Instructions to user: Explain that the document will be built section by section. For each section: Clarifying questions will be asked about what to include 5-20 options will be brainstormed

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Documentation
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@anthropics · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview doc-coauthoring.preview
# Step 4: Iterate Based on Results

Ask what Reader Claude got wrong or struggled with. Indicate intention to fix those gaps. Loop back to refinement for any problematic sections. ---

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.