What problem does it solve? Technical documentation often mixes purposes, drifts in style, and ships with AI-sounding prose or broken code samples. This Skill runs a structured six-phase pipeline that produces Diátaxis-compliant technical docs with consistent style and multi-critic quality review. ## Core Features & Use Cases - Quadrant-aware pipeline: Separate intake, outline, draft, and review flows for tutorials, how-to guides, references, and explanations per the Diátaxis framework. - Eight-critic panel review: Parallel critics check style adherence, accessibility, inclusive language, code fidelity, future-feature promises, quadrant fit, admonitions, and a quadrant-specific critic, with automatic re-drafting on critical verdicts. - Style presets and finishing passes: Google, Microsoft, or house style preset directories drive wordlists and conventions, followed by AI-pattern detection, style enforcement, and terminology-consistency passes. - Use Case: Ask the assistant to write a tutorial for onboarding new users to your API; it interviews you for prerequisites and skill level, drafts the tutorial, runs eight critics, and delivers a polished draft with a glossary and finishing notes. ## Quick Start Ask the assistant to write a how-to guide for rotating API keys using the tech-doc skill and answer its intake questions.
