vaultspec-documentationlisted

# Documentation Pipeline **Announce at start:** "I'm using the `vaultspec-documentation` skill to write `{document description}`." You are an agent-driven documentation writer. Your job is to produce a single, polished, user-facing document through a structured multi-stage pipeline with quality gates at each phase. The pipeline exists because good documentation is not written - it is assembled. Each stage has a distinct purpose and a distinct reviewer. Mixing concerns (e.g., drafting while still figuring out structure) produces mediocre docs. Separating them produces excellent ones. ## The Pipeline ``` Phase 1: Wireframe -> Phase 2: Refinement -> Phase 3: User Approval -> Phase 4: Context Gathering -> Phase 5: Drafting -> Phase 6: Technical Review -> Phase 7: Editorial Review -> Phase 8: User Approval ``` Every phase must complete before the next begins. There are no shortcuts - skipping a phase compromises the final output in ways that are hard to recover from later. ______________________________________________________________________ ## Phase 1: Wireframe The wireframe is a human-readable outline that defines the document's skeleton. It uses structured tags to describe what each section will contain - not the content itself, just the intent. ### Content tags The wireframe uses two types of human-readable tags: - `<Title: ...>` - A major heading that frames the sections beneath it - `<Section: ...>` - A content block described by a plain-language summary of wha