writing▌

Structured framework for writing blameless postmortems that drive organizational learning from incidents. \n \n Provides templates for standard postmortems, 5 Whys analysis, and quick incident reviews, with sections for timelines, root cause analysis, detection gaps, and action items \n Emphasizes blameless culture by shifting focus from individual blame to systemic failures and conditions that enabled incidents \n Includes facilitation guide for postmortem meetings, anti-patterns to avoid, and

Create clear, comprehensive technical documentation for specs, architecture, runbooks, and APIs. \n \n Provides templates and step-by-step guidance for five document types: technical specifications, architecture documents, runbooks, API documentation, and changelogs \n Includes audience-specific writing strategies for developers, operations teams, managers, and end users with tailored content focus \n Offers visual aid support via Mermaid diagrams, flowcharts, tables, and code examples with synt

Comprehensive implementation plans for multi-step tasks, breaking down specs into bite-sized, testable steps. \n \n Decomposes requirements into focused tasks (2–5 minutes each) following TDD: write failing test, verify failure, implement, verify pass, commit \n Maps file structure upfront with clear boundaries and responsibilities, ensuring each file has one purpose and files that change together stay together \n Includes exact file paths, complete code samples, and specific commands with expec

Hookify rules are markdown files with YAML frontmatter that define patterns to watch for and messages to show when those patterns match. Rules are stored in .claude/hookify.{rule-name}.local.md files.

Generate Architectural Decision Records (ADRs) following the MADR template with systematic completeness checking.

Comprehensive guide to writing effective, blameless postmortems that drive organizational learning and prevent incident recurrence.

You are an expert editor who specializes in detecting and removing AI writing patterns. Your job is to take content that reads like it was generated by a language model and rewrite it so it sounds like a knowledgeable human wrote it on the first try.

This skill provides comprehensive guidelines for authoring content in adev/src/content. It combines Google's technical writing standards with Angular-specific markdown conventions, components, and best practices.

Write developer-focused technical blog posts via inference.sh CLI.

Write Milvus application-level Jupyter notebook examples as a DevRel workflow. Uses a Markdown-first approach — AI edits .md files, then converts to .ipynb via jupyter-switch.