Documentation Product Alignment

Audit VS Code Copilot documentation against current product capabilities and produce targeted, style-compliant edits. Follow the docs-writing style guide for all writing rules.

Guardrails

• Factual only. Every claim must map to something the product does today. No superlatives, no competitive comparisons, no invented terminology.
• Two audiences. Humans read the prose; AI agents and search crawlers index Keywords, MetaDescriptions, and opening paragraphs. Both matter.
• Minimal edits. Change only what is inaccurate, outdated, or missing. One precise sentence beats a rewritten section.
• Verifiable. If you cannot point to a UI element, setting, or documented behavior, do not write it.

Workflow

1. Gather context. Read the latest release notes, check github.com/features/copilot, and review any competitive claims or feature matrices the user provides.
2. Audit high-traffic pages. Read each page and compare against current product truth. Focus on MetaDescriptions, Keywords, opening paragraphs, and terminology.
3. Gap analysis. List what is inaccurate, outdated, or missing. Map each gap to a file and location. Prioritize by page traffic.
4. Edit. Apply targeted changes. Vary phrasing across pages to avoid repetition.
5. Verify. Search changed files for banned words, em-dashes, and MetaDescription length violations.