vulnerability-management
Vulnerability lifecycle management including CVE tracking, CVSS scoring, risk prioritization, remediation workflows, and coordinated disclosure practices
team-topology-design
Team Topologies methodology for organizational design. Covers the four fundamental team types, three interaction modes, cognitive load assessment, Inverse Conway Maneuver, and team evolution patterns. Use when designing team structures that align with architecture.
backlog-update
Reminder to update backlog.org before commits or when finishing significant work. Use before committing changes, after completing implementation from plan mode, or when wrapping up a work session. This skill ensures the project's task tracking in backlog.org stays current with actual progress. Trigger when about to commit, exiting plan mode, or when user says "done", "let's commit", "wrap up", or similar.
reviews-retros-reflection
Use when conducting sprint retrospectives, project post-mortems, weekly reviews, quarterly reflections, after-action reviews (AARs), team health checks, process improvement sessions, celebrating wins while learning from misses, establishing continuous improvement habits, or when user mentions "retro", "retrospective", "what went well", "lessons learned", "review meeting", "reflection", or "how can we improve".
track-implementation-progress
Track implementation progress against plan. Use to monitor component delivery and identify blockers.
revising-findings
Implement findings from verification reports with scope-based parallel workflow
agent-hierarchy-diagram
Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.
postmortem
Use when analyzing failures, outages, incidents, or negative outcomes, conducting blameless postmortems, documenting root causes with 5 Whys or fishbone diagrams, identifying corrective actions with owners and timelines, learning from near-misses, establishing prevention strategies, or when user mentions postmortem, incident review, failure analysis, RCA, lessons learned, or after-action review.
phase-plan-generate
Generate comprehensive plan documentation following Template 1 format. Use when creating plan.md files for new components or subsections.
conducting-plan-review
Complete workflow for evaluating implementation plans before execution with quality checklist and structured feedback
vendor-evaluation
Evaluate third-party vendors for engineering fit. Use when a senior developer needs a structured vendor assessment.
facilitation-patterns
Use when running meetings, workshops, brainstorms, design sprints, retrospectives, or team decision-making sessions. Apply when need structured group discussion, managing diverse stakeholder input, ensuring equal participation, handling conflict or groupthink, or when user mentions facilitation, workshop design, meeting patterns, session planning, or running effective collaborative sessions.
estimation-techniques
Back-of-envelope calculations for system design. Use when estimating QPS, storage, bandwidth, or latency for capacity planning. Includes latency numbers every programmer should know and common estimation patterns.
org-standardization
Define engineering standards across teams. Use when a senior developer needs to align practices.
scalability-assessment
Assess a system for growth bottlenecks. Use when a senior developer needs to evaluate scaling limits.
use-case-20
Use Case 2.0 methodology by Ivar Jacobson. Covers use case slices, lightweight documentation, user story derivation, and value-driven prioritization. Modern approach to use case modeling for agile teams.
heuristics-and-checklists
Use when making decisions under time pressure or uncertainty, preventing errors in complex procedures, designing decision rules or checklists, simplifying complex choices, or when user mentions heuristics, rules of thumb, mental models, checklists, error prevention, cognitive biases, satisficing, or needs practical decision shortcuts and systematic error reduction.
difficult-conversations
Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.
rt-iac
Reverse Thinking - Information Completeness Assessment. Mandatory pre-planning checkpoint that blocks planning until prerequisites are verified. Use when receiving specs, PRDs, tickets, RFCs, architecture designs, or any multi-step engineering task. Integrates with CoVe-style planning pipelines. Invoke BEFORE creating plans, delegating to agents, or defining acceptance criteria.
prioritization-methods
Requirements prioritization techniques including MoSCoW, Kano Model, WSJF (SAFe), and Wiegers' Value/Cost/Risk matrix. Provides scoring frameworks, trade-off analysis, and priority visualization. Use when ranking requirements by business value, customer impact, or implementation efficiency.
estimation-fermi
Use when making quick order-of-magnitude estimates under uncertainty (market sizing, resource planning, feasibility checks), decomposing complex quantities into estimable parts, bounding unknowns with upper/lower limits, sanity-checking strategic assumptions, or when user mentions Fermi estimation, back-of-envelope calculation, order of magnitude, ballpark estimate, triangulation, or needs to assess feasibility before detailed analysis.
career-progression
Competency frameworks, level expectations (Junior to Staff+), and career progression paths for software engineers. Use when navigating promotions, understanding level requirements, or planning career advancement.