Найдите подходящую возможность для вашего агента.
Cette skill devrait être utilisée pour réviser des présentations PowerPoint selon les standards de conseil (McKinsey, BCG), avec analyse de la structure, clarté, design, storytelling et conformité DSFR. Utiliser quand l'utilisateur demande une révision, analyse ou amélioration de présentation, avec ajout de commentaires directement dans les slides.
Perform organisational mining and handover-of-work analysis with privacy-aware controls.
Process files in the Needs_Action folder according to Company Handbook rules. Use this skill when you need to handle tasks placed in the Needs_Action directory by watchers, following the rules defined in the Company Handbook.
Use when asked to create a deep-research handoff bundle: do web research, codebase analysis, Gemini Oracle critique, and produce a prompt + context folder on Desktop for another AI agent (include a zipped archive of the bundle).
This skill should be used when the user reports a "bug", "not working", "fix this", "debug", "test failing", or when investigating unexpected behavior. Four-phase framework ensuring root cause understanding before attempting solutions.
Summarize meeting transcripts or notes into actionable format. Invoke when user provides meeting transcripts, notes, or wants actionable meeting summaries.
Create ATOMIC implementation plan for a single frontend task. Each step has exact code and verification command. IMPORTANT: This skill creates MICRO-LEVEL atomic steps, NOT macro architecture plans. For architecture planning or feature scoping, use EnterPlanMode instead. Use this skill when: - Running /frontend.plan command - User explicitly asks for "atomic steps", "step-by-step plan with verification" - Have a specific task from docs/reference/frontend/tasks/ and need implementation steps - Need granular steps: Setup (create files) → Implementation (write code) → Test (verify) → Commit DO NOT use for: - Architecture planning (use EnterPlanMode) - General development planning - Feature scoping or estimation Output: Present plan to user (not saved to file), each step includes Files, Action, and Verify command.
Multi-ecosystem dependency analysis tools. Provides structured data for vulnerability scanning and version checking. The AI applies intelligence to create rich reports - scripts are data providers only. Supports Maven projects (pom.xml), with Python and Node.js support planned.
Your approach to handling backend state management. Use this skill when working on files where backend state management comes into play.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Refactoring guidance with design patterns and code improvement strategies.
steering skill Trigger terms: steering, project memory, codebase analysis, auto-update context, generate steering, architecture patterns, tech stack analysis, project structure, analyze codebase, understand project Use when: User requests involve steering tasks.
This skill should be used when users need to fetch Jira ticket content using either a specific ticket ID (like RD-3891) or search for tickets by title/description. It defaults to searching within the current sprint but can extend to all tickets when needed. The skill uses the Jira CLI to retrieve ticket details, status, assignee, and descriptions.
Guide git operations using a three-tier branching model (main → staging → feature). Use this skill when the user asks about git commands, branch strategy, PRs, rebasing, merging, deploying to production, hotfixes, or conflict resolution. Triggers include "git", "commit", "branch", "PR", "rebase", "merge", "deploy", "staging", "feature branch", "hotfix".
Creates detailed implementation plans with atomic steps, model selection per step, dependency labels, and embedded TDD specifications
Generates a professional PR description by analyzing git diff between current branch and main. Use when the user wants to prepare a pull request, write a description, or summarize their changes for a PR.
Ability to analyse, design, optimise, and improve systems that integrate people, processes, technology, and resources to meet defined performance, quality, cost, and safety requirements. Includes applying engineering, statistical, and systems methods to model workflows, identify inefficiencies, evaluate trade-offs, and implement improvements across operations and supply chains. Applies across manufacturing, services, logistics, healthcare, and infrastructure contexts and is independent of specific tools or industries, with human accountability retained for decisions, outcomes, and impacts.
Draft outcome-oriented OKRs with leading indicators and initiatives tied to the product strategy.
Unterstützt dabei, aus vagen oder konkreten Vorhaben einen realistischen Projektplan mit Spezifikation, Task-Breakdown und passenden LLM-Prompts für Umsetzungsagenten zu entwickeln; verwenden, wenn Planung, Dokumentation und Prompt-Design für ein neues Vorhaben nötig sind.
