Loading...
Loading...
Found 2,010 Skills
Use when investigating and documenting a production incident, outage, data corruption event, or post-mortem — guides evidence collection during the investigation AND produces a rich, reproducible Root Cause Analysis report. Trigger on phrases like "write an RCA", "post-mortem for X", "document this incident", "what went wrong with...", "the pipeline broke yesterday, help me investigate", or any time the user is debugging a recently-resolved incident and wants a writeup. Also use proactively when the user finishes resolving an incident in-session and the resolution context is fresh — offer to capture it as an RCA before details fade.
Use when writing a new agent skill for the dogfooded-skills library — covers frontmatter spec, section structure, quality criteria, and antipatterns.
Use when an approved Spec Kit `plan.md` + `spec.md` must be decomposed into dependency-ordered `tasks.md`, or when `tasks.md` is missing/stale after planning or reconciliation changes.
Comprehensive patterns and techniques for removing AI-generated verbosity and slop
Mind mapping and exploration state tracking for workshops. Use to maintain awareness of explored vs uncharted territory, implement backtracking, and ensure comprehensive coverage or documented gaps.
Update CHANGELOG.md with user-facing changes from recent commits. Use when the user has merged a PR, completed a release, or wants to document recent changes in the changelog.
GenAI-powered semantic validation - detects outdated docs, version mismatches, and architectural drift
Update PRD based on design decisions and strategic changes made during conversations
Guidelines for writing and editing Plain package READMEs. Use this when creating or updating README files.
Technical Research Expert Skill, providing systematic technical research methodologies, document specifications, and best practices. Trigger this skill when you need to conduct technology selection, architecture research, framework comparison, or implementation scheme research.
Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.
Create adoption strategies and materials to drive design system usage across teams.