What problem does it solve? Technical writing often buries the answer under filler, vague claims, and unstructured prose, forcing readers to reconstruct the reasoning themselves. This Skill enforces a clarity-first writing policy so explanations, diagnoses, reviews, and reports are compact, precise, and immediately actionable for a Senior developer audience. ## Core Features & Use Cases - Task-specific templates: Provides ready structures for interview mini-notes, diagnosis-and-fix reports, architecture recommendations, code reviews, and completed-work summaries. - Evidence discipline: Distinguishes observed fact, hypothesis, and recommendation, and prevents overstated claims such as unscoped "exactly once" or "thread-safe" guarantees. - Verification reporting: Separates passed, failed, skipped, and not-run checks with concrete commands and scopes. - Use Case: After debugging a Kafka consumer issue, produce a report following the symptom → evidence → cause → fix → verification → next step structure, with the hypothesis clearly labeled and the smallest distinguishing check stated. ## Quick Start Write a diagnosis report for the duplicate Kafka message processing issue using the technical-communication structure with labeled evidence and verification status.
