What problem does it solve? Technical deep-dive articles often degrade into source-location dumps, question-style headings, and marketing language that obscure actual design rationale. This Skill enforces a mechanism-first writing contract so engineering articles explain principles, data flow, trade-offs, and operations instead of listing file:line pointers. ## Core Features & Use Cases - Structured Outline Template: Provides a 10-section default structure covering background, model, end-to-end flow, mechanism deep-dives, trade-offs, operations playbook, and a compact code index appendix. - Style Contract Enforcement: Defines mandatory and forbidden rules for headings, narrative, evidence, tone, and terminology to keep articles precise and neutral. - Quality Gates: Requires at least two troubleshooting scenarios and one trade-off comparison table before final output. - Use Case: When documenting a new storage engine or request pipeline, use this Skill to produce an engineering blog post that explains design intent and failure handling first, with code references kept in an appendix. ## Quick Start Use the tech-impl-deep-dive-writer skill to write a deep-dive article explaining the architecture and mechanisms of our comment moderation pipeline.
