incident-postmortem
Draft an incident postmortem with timeline, RCA, and action items. Use when a senior developer needs a structured post-incident report.
Découvrez les skills databases project management, comparez leurs dépôts et consultez leurs instructions.
Draft an incident postmortem with timeline, RCA, and action items. Use when a senior developer needs a structured post-incident report.
Perform threat modeling for a system or feature. Use when a senior developer needs security risk assessment.
Define or review SLOs and SLAs for a service. Use when a senior developer needs reliability targets.
Define performance budgets and guardrails. Use when a senior developer needs performance targets and enforcement.
Model domains and bounded contexts for complex systems. Use when a senior developer needs domain-driven design guidance.
Assess readiness for compliance audits. Use when a senior developer needs a gap analysis for standards.
Assess a system for growth bottlenecks. Use when a senior developer needs to evaluate scaling limits.
Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.
Break a task or ticket into small steps. Use when a junior developer needs guidance on how to start.
Review system costs and propose reductions. Use when a senior developer needs cost-saving recommendations.
Evaluate third-party vendors for engineering fit. Use when a senior developer needs a structured vendor assessment.
Explain CSS layout issues and propose fixes. Use when a junior developer is struggling with alignment or spacing.
Assess and prioritize tech debt items. Use when a senior developer needs an investment plan for debt reduction.
Define engineering standards across teams. Use when a senior developer needs to align practices.
Audit dependencies for licensing, security, and maintenance risk. Use when a senior developer needs risk assessment.
Creates a PostMortem given enough context about an incident/outage. Will guide user to timeline, action items/bugs, and finally draft a Google Doc with the results.
Expert-level SRE skill for Google Cloud Build (GCB) and Cloud Run investigations. Activate when user mentions Cloud Build failures, deployment issues to Cloud Run, or needs help debugging GCB pipelines. Special...
This skill should be used when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords...
This skill should be used when the user mentions GitHub PRs, issues, workflows, releases, or repository management. Triggers on keywords like "github", "gh", "pr", "pull request", "issue", "workflow", "actions"...
Manage time tracking with Toggl or Clockify. Use when user asks about time tracking, timers, timesheets, logging hours, starting/stopping work, checking what's running, viewing time entries, or creating manual...
Multi-agent coordination patterns for OpenCode swarm workflows. Use when working on complex tasks that benefit from parallelization, when coordinating multiple agents, or when managing task decomposition. Do NO...
Threat modeling skill for identifying security threats, attack surfaces, and designing mitigations. This skill should be used when performing threat assessments using STRIDE, PASTA, or Attack Trees, creating da...
AI-powered task management for structured, specification-driven development. Use this skill when you need to manage complex projects with PRDs, break down tasks into subtasks, track dependencies, and maintain o...
Install and initialize task-master for AI-powered task management and specification-driven development. Use this skill when users ask you to parse a new PRD, when starting a new project that needs structured ta...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.