sdlc-research
Use when researching how to implement a feature, analyzing codebase patterns, investigating existing implementations, exploring dependencies, or finding relevant code for a user story.
Найдите подходящую возможность для вашего агента.
Use when researching how to implement a feature, analyzing codebase patterns, investigating existing implementations, exploring dependencies, or finding relevant code for a user story.
Use when planning animation workflows, deciding between spontaneous vs controlled approaches, or balancing creative freedom with structural precision.
Use when conducting comprehensive design review before launch, for stakeholder presentation, or when user requests expert-level design analysis. Produces detailed report from senior Apple product designer perspective.
Use when planning and tracking work - creates visible, emergent work breakdown using bd (beads) with just-in-time planning and hierarchical task trees
This skill should be used when coordinating "multiple specialized agents", "complex workflow orchestration", "autonomous development teams", "agent collaboration", "distributed task management", or when managing sophisticated multi-agent development processes.
Skill for research-oriented scientific software development, balancing reproducibility, correctness, and long-term maintainability, with selective engineering rigor.
Comprehensive guide to creating, communicating, and maintaining technical and product roadmaps for strategic alignment and stakeholder communication
Deeply interviews the user about a bug before investigating or fixing it. Use this when the user says "interview me about [bug]", "I have a bug to report", "let's work on this bug", "found a bug", "there's a bug", or describes a bug they encountered. Asks probing questions about reproduction steps, environment, patterns, impact, and context that help isolate the root cause. Continues until the bug is well-understood, then writes a detailed investigation/fix plan.
software-developer skill Trigger terms: implement, code, development, programming, coding, build feature, create function, write code, SOLID principles, clean code, refactor Use when: User requests involve software developer tasks.
Create Azure DevOps work items (Epics, Features, User Stories) from generated markdown documentation with automatic UCP calculation and parent-child linking. Use when creating epics in DevOps, creating features in DevOps, creating user stories in DevOps, or any Azure DevOps work item creation task. Ensures required fields are captured including Objective UCP and maintains naming consistency for traceability.
Gestionar tareas en notas Markdown de Obsidian (captura, inbox, priorización, daily/weekly). Respeta el formato existente de tasks.
Coordinate multi-agent discussions to reach decisions. Use when 2+ agents deliberate or for board meetings.
This skill MUST be used when the user asks to "analyze backlog issues", "analyze backlog", "analyze top backlog items", "Claude analyze tickets", "run analysis on backlog", "AI analyze Jira issues", "bulk analyze issues", "analyze unanalyzed tickets", or wants to have Claude automatically analyze and annotate multiple backlog issues. This skill finds the top 3 backlog issues without the claude-analyzed label, performs issue-analysis on each, and updates the Jira description with a Claude Analysis section.
A learning methodology skill based on Dr. Justin Sung's PACER system for effective information retention and application. Use when helping users (1) learn new material efficiently, (2) take notes or summarize content, (3) create study plans, (4) review or memorize information, (5) understand how to retain knowledge better, or (6) process educational content like books, lectures, courses, or articles.
Design System Enforcer that maintains visual consistency at scale. Use when creating UI, reviewing styles, or ensuring brand consistency.
Pulls ticket details from Jira, creates feature branches with proper naming conventions, and handles planning steps. Use when starting work on a Jira ticket, creating branches for tickets, or when users mention "work on ticket", "start ticket", "create branch for", or Jira ticket IDs.
HAIOS Plan Validation Bridge for validating plan readiness. Use before entering DO phase. Guides CHECK->VALIDATE->APPROVE workflow.
Turn ideas/brain dumps into a structured project brief (problem, goals, scope, milestones, success criteria). Use when starting a project.