Найдите подходящую возможность для вашего агента.
Access Jira issues and Confluence pages via Python scripts with OAuth 2.0 authentication. Use when user asks about Jira tickets, issues, bugs, stories, epics, sprints, or Confluence pages, wiki, documentation.
Use this skill when working on releases, version numbers, or release preparation.
Orchestrate the full product flow from vision to shipped code. Use when starting a new feature or product.
Incident response documentation, timeline analysis, containment procedures, and IR reporting. Support the full incident lifecycle from detection to lessons learned. Use for security incidents, breach response, and IR planning.
Guide the planning of microservices architecture. Use when designing, planning, or architecting a system using microservices.
Analyze current spec completion status and provide detailed progress report. Use when checking progress, identifying blockers, or planning what to work on next. More detailed than the /spec-flow:status command.
Use when executing implementation plans with independent tasks in the current session
Validate schedules against hard gates and score quality. Phase 3 of EROS pipeline. Invoked automatically after schedule generation completes.
This skill should be used when the user asks about "long-running agents", "antibrittle patterns", "agent reliability", "agents that run for hours", "run boxes", "context boundaries", or needs architecture guidance for AI agents that work autonomously for extended periods.
Copilot agent that assists with systematic requirements review using Fagan Inspection and Perspective-Based Reading (PBR) techniques Trigger terms: requirements review, specification review, SRS review, Fagan inspection, perspective-based review, requirements validation, requirements verification, quality gate review, formal inspection, requirements checklist Use when: User requests involve requirements review, validation, or inspection tasks.
Skill for committing changes to this repository using Git, generating a commit message from recent history and current changes.
JIRA 티켓 기반 전체 개발 파이프라인 자동화. 티켓 분석→구현→빌드→PR까지 semi-auto로 실행. "jira", "ticket", "workflow", "pipeline" 키워드 시 활성화
Persistent schema-driven running log with three-component architecture - quick-capture ideas, AI auto-detection, and backlog review librarian
ガイドライン自動読み込み - プロジェクトの技術スタックを検出し、必要なガイドラインのみをセッションに適用。トークン節約。
Automatically bridge long technical sessions to keep context window small and costs low. Extracts key technical decisions, resolved bugs, active tasks, and essential code snippets from conversation history into a compact markdown summary (2,000–5,000 tokens). Use when reaching a project phase milestone, when Claude warns the context window is getting full, or to start a fresh session with minimal token cost while maintaining continuity.
Triage and merge PRs from parallel Claude Code sessions. Discovers open PRs, detects overlaps, quality-checks diffs, builds merge plan, and executes merges after approval. Use after running parallel-code-review sessions, or when you have multiple PRs to evaluate and merge systematically. Triggers on "triage PRs", "merge parallel PRs", "process review PRs".
순차적 사고, 분석, 문제 해결, 복잡한 문제, 단계별 분석 - Use when solving complex problems. Systematic thinking workflow using Sequential Thinking MCP for multi-step analysis, trade-off evaluation, and architectural decisions.
Setup observability platform configuration (Datadog, Prometheus, Splunk) with REQ-* dashboards and alerts. Creates monitors for each requirement with SLA tracking. Use when deploying to production or setting up monitoring.
