ベストプラクティスの収集・評価・統合・更新を体系化するスキル。 情報源の信頼性評価、品質スコアリング、統合パターンを用いて知識ベースを改善する。 Anchors: • The Pragmatic Programmer / 適用: 実践的改善 / 目的: 継続的な品質向上 • Evidence-Based Management / 適用: 評価基準 / 目的: 判断の一貫性を担保 • Knowledge Management (Nonaka) / 適用: 知識統合 / 目的: 暗黙知の体系化 Trigger: Use when collecting best practices, assessing source credibility, scoring quality, integrating guidance, or updating knowledge bases.
Proactively captures significant work into the journal for future reference
Matches targets against configured patterns for work-ID-free planning
システム障害・インシデントの検知から解決、事後分析までを体系的に支援。ITIL・SRE原則に基づき、迅速な復旧と再発防止を実現。 Anchors: • The Site Reliability Workbook (Google) / 適用: ポストモーテム文化 / 目的: 非難なき事後分析と学習 • ITIL 4 / 適用: インシデント・問題管理 / 目的: 構造化されたエスカレーション • The Phoenix Project (Kim, Behr) / 適用: 変更管理 / 目的: 変更起因インシデントの予防 Trigger: Use when responding to system outages, handling alerts, writing incident reports, conducting postmortems, or analyzing root causes. incident, outage, postmortem, RCA, 5 whys, rollback, escalation, severity, on-call
SLO（Service Level Objective）とSLI（Service Level Indicator）の設計、 エラーバジェット管理、信頼性目標の策定を支援するスキル。 Googleの SRE プラクティスに基づき、適切な信頼性目標を設計する。 Anchors: • Site Reliability Engineering (Google) / 適用: SLO/SLI設計原則 / 目的: 信頼性目標の最適化 • The Site Reliability Workbook (Google) / 適用: 実践的なSLO実装 / 目的: 運用可能なSLO設計 • Implementing Service Level Objectives (Hidalgo) / 適用: SLO成熟度モデル / 目的: 段階的導入 Trigger: Use when designing SLOs, defining SLIs, calculating error budgets, or establishing reliability targets. SLO design, SLI definition, error budget, reliability target, service level objective
Troubleshoot and resolve OrcaFlex static analysis convergence issues. Diagnose common problems including line connectivity, tensions, environmental conditions, and numerical instabilities.
TODO list discipline for task tracking. Activates for multi-step tasks (3+), complex work, or when systematic organization is needed. Use for tracking progress and ensuring completeness.
Assign and unassign issues to users (CLI not yet available)
Generate a project tree annotated with context.md notes to help future sessions, (auto-call at session start)
Classify work type from issue metadata (CLI not yet available)
Generate comprehensive security audit reports for applications and systems. Use when you need to assess security posture, identify vulnerabilities, evaluate compliance status, or create formal security documentation. Trigger with phrases like "create security audit report", "generate security assessment", "audit security posture", or "PCI-DSS compliance report".
Expert IT Risk Manager with deep knowledge of ISO 27005 (IT risk management), ISO 31000 (enterprise risk management), and ISO 27001 integration. Specializes in optimizing workflows through the Data Reuse principle - leveraging existing Assets, Incidents, Controls, and Business Processes to streamline risk assessments. Automatically activated when user asks about risk management, risk assessment, risk treatment, risk appetite, risk acceptance, ISO 27005, ISO 31000, threat analysis, vulnerability assessment, or risk matrices.
Validates JIRA tickets have required fields and sufficient information for development. Activates when users ask about ticket quality, readiness, or completeness, or when reviewing tickets before sprint planning.
研究專案的建立、切換、設定管理。 LOAD THIS SKILL WHEN: 新專案、切換專案、專案設定、paper type、start exploration、convert exploration CAPABILITIES: create_project, list_projects, switch_project, get_current_project, setup_project_interactive, start_exploration, convert_exploration_to_project
Plan implementation skill. Executes approved technical plans phase by phase with verification checkpoints.
Use when an agent needs to write user stories for a project
Faster on-call handoffs and better postmortems with triage SOPs
Use when creating implementation plans to generate properly structured plans with phases, success criteria, and project references.
This skill should be used when creating or updating PROJECT.md files, planning sprints, defining project goals, or managing project scope. It provides templates and best practices for PROJECT.md-first development.
This skill should be used when the user asks to "document discussion", "save meeting notes", "record conversation", "capture meeting", or mentions needing to document team discussions with participants, decisions, and action items.
Use when starting any feature, project, or design work. Guides collaborative design refinement through incremental questioning before any code is written.
