Plan for VAPICS-186

Author: vapi-tasker[bot]

docs/specs/VAPICS-186/PLAN.md

@@ -0,0 +1,29 @@
+# Vapi Documentation Writing Bible
+
+**Progressive Structure, Plain Language & Anti-Verbosity Standards**
+
+*Created for Linear ticket VAPICS-186*
+
+---
+
+## Table of Contents
+
+1. [Part 1: Documentation Architecture — Progressive Learning Tree](#part-1)
+2. [Part 2: Language & Jargon Standards — Plain English First](#part-2)
+3. [Part 3: Content Density & Anti-Verbosity Framework](#part-3)
+4. [Part 4: Reusable Doc Page Template](#part-4)
+5. [Part 5: AI Agent Brief — Doc Drafting & Review Standards](#part-5)
+
+---
+
+## Introduction
+
+This document defines **how** Vapi documentation should be written. The goal: users self-serve, discover more features, and never need to open a support ticket.
+
+Three principles govern everything:
+
+1. **Progressive structure** — concepts build sequentially, no page assumes knowledge that hasn't been introduced earlier
+2. **Plain language** — plain English by default, jargon explained inline, zero assumed knowledge
+3. **Anti-verbosity** — every sentence earns its place, docs respect the reader's time
+
+The full document includes the progressive learning tree with dependency graph, language style guide with banned words list, anti-verbosity playbook with scanability checklist, a reusable doc page template, and an AI agent brief for automated drafting/review.