The Rewrite Room

Use when the primary outcome is creating publishable source-attributed content from URLs or supplied material, including research summaries, articles, briefs, and posts whose factual claims and quotations need reader-visible, verifiable citations.

Use when the primary outcome is comparing documentation claims with implementation evidence, synchronizing docs from verified changes, or freshness review, including drift, missing coverage, stale claims, and post-change updates.

Use when the primary outcome is authoring, rewriting, summarizing, or validating user-facing documentation without implementation comparison or required source attribution, including READMEs, tutorials, API docs, GitLab Markdown, source-faithful summaries, and audience-specific prose.

Use when the primary outcome is creating a new portable Agent Skill directory from one local documentation file, documentation directory, or Git repository, including mixed text and capability-gated binary sources that require exhaustive source-to-output accounting.

Use when the user explicitly asks Rewrite Room to route documentation work, or when audit/sync/freshness, user-facing authoring, citation-driven writing, docs-to-skill conversion, and AI-instruction optimization overlap and exactly one workflow must be chosen.