Framework for creating end-of-day summary documents. Use when user says "daily summary", "generate summary", or similar at end of day. Provides structured markdown template with date verification, filename patterns, and formatting guidelines. Extend with personal metrics and domain-specific content.
Perform operability analysis combining multiple sea states to assess system availability and weather downtime. Generate operability envelopes, critical heading analysis, and downtime calculations from wave scatter diagrams.
Use when resolving PR review threads. Enforces that all threads are marked resolved before completion.
GitHub プロジェクト管理を一括操作。Issue作成、ラベル設定、プロジェクト紐付け、マイルストーン、日付、ステータス変更。 トリガー例: 「Issue作成」「プロジェクト管理」「project-mgmt」「Issueを立てて」「プロジェクトに追加」
ストーリーポイント、プランニングポーカー、相対見積もりを用いたアジャイル見積もり技法。 チーム合意に基づく予測可能性と柔軟性を両立する見積もりプロセスを実践する。 Anchors: • Agile Estimating and Planning (Mike Cohn) / 適用: 見積もり手法全般 / 目的: ストーリーポイント理論 • Scrum Guide / 適用: スプリント計画 / 目的: ベロシティ運用 • Planning Poker実践ガイド / 適用: セッション進行 / 目的: アンカリング防止 Trigger: Use when estimating user stories, running planning poker sessions, tracking velocity, or improving estimation accuracy. 見積もり, ストーリーポイント, プランニングポーカー, ベロシティ, 相対見積もり, スプリント計画, 工数見積もり
Meta-improvement skill that analyzes conversation context and uncommitted git changes to propose improvements to the AI agent ecosystem itself (agents, skills, commands). Use when the user asks to reflect on the conversation, improve the agent ecosystem, or optimize workflows based on patterns observed. This skill ALWAYS acts as supervisor first, producing an initial analysis report, then spawns specialized builder agents based on user-approved plan. Always requires user approval before making changes.
Create technical diagrams using Mermaid syntax for architecture, sequences, ERDs, flowcharts, and state machines. Use for visualizing system design, data flows, and processes. Triggers: diagram, mermaid, architecture diagram, sequence diagram, flowchart, ERD, entity relationship, state diagram, C4 model, component diagram, visualize, draw.
Show project detail. Requires authentication. Use for project management operations
Coaches on leadership, management, and team development. Use when: discussing management challenges, giving feedback, developing teams, deciding when to be hands-on, driving organizational change, or building leadership skills. Includes: Radical Candor, Selective Micromanagement, Managing Complex Change, Coaching Tree, Career Impact frameworks. Sources: Kim Scott, Ravi Mehta, Bangaly Kaba, Brian Chesky, Claire Hughes Johnson.
Deployments - rollback, feature flags, ops tooling. Use when shipping to production.
Agent lifecycle management specialist skill. Ensures continuous quality through startup, execution, state management, shutdown, versioning, and maintenance. • The Pragmatic Programmer (Andrew Hunt, David Thomas) / Apply: Lifecycle management and maintenance strategies / Purpose: Practical agent operations and versioning philosophy Trigger: Use when designing agent initialization strategies, implementing agent state management mechanisms, developing agent versioning strategies, planning agent maintenance, implementing agent shutdown and cleanup, coordinating multi-agent system lifecycles. initialization, state management, versioning, maintenance, shutdown, cleanup, monitoring, logging
複雑な問題を分解し、推論の流れを整理して短い根拠サマリーを作成するスキル。 前提整理、論点分解、選択肢比較、判断理由の要約を通じて、説明責任のあるアウトプットを作る。 Anchors: • The Pragmatic Programmer / 適用: 問題分解 / 目的: 実践的な整理 • Thinking, Fast and Slow / 適用: 判断バイアス確認 / 目的: 判断根拠の明確化 • Critical Thinking / 適用: 論点整理 / 目的: 根拠の一貫性 Trigger: Use when structuring reasoning, summarizing decision rationale, clarifying assumptions, or documenting a step-by-step analysis.
Deployments - rollback, feature flags, ops tooling. Use when shipping to production.
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
READ-ONLY quick overview of GitHub Elements workflow state. Shows active threads, phase distribution, and workflow health at a glance. USE THIS SKILL WHEN: - User asks "what's the status" or "show me the status" - User asks "what threads are active" or "what am I working on" - User asks "show me the workflow state" or "what's happening" - User wants a quick overview before starting work - Starting a session and need context DO NOT USE THIS SKILL WHEN: - User wants to CLAIM an issue (use ghe-claim) - User wants to POST a checkpoint (use ghe-checkpoint) - User wants to TRANSITION phases (use ghe-transition) - User wants DETAILED metrics/health reports (use ghe-report) EXAMPLES: <example> Context: User starting a session wants to see current state user: "What's the github elements status?" assistant: "I'll use ghe-status to show you the current workflow state" </example> <example> Context: User wants to know what work is available user: "Show me what threads are active" assistant: "I'll use ghe-status to disp
ユーザーから与えられたタスクを単一責務の原則に基づいて分解し、 Phase 1からPhase 13までの実行可能なタスク仕様書ドキュメントを生成する。 Anchors: • Clean Code (Robert C. Martin) / 適用: 単一責務の原則 / 目的: タスク分解の基準 • Continuous Delivery (Jez Humble) / 適用: フェーズゲート / 目的: 品質パイプライン構築 • Domain-Driven Design (Eric Evans) / 適用: ユビキタス言語 / 目的: 一貫した用語設計 Trigger: タスク仕様書作成, タスク分解, ワークフロー設計, 実行計画作成 Use when creating task specifications for complex development tasks.
優先順位付けフレームワークの専門スキル。 MoSCoW法、RICE Scoring、Kano Modelを用いて、限られたリソースで最大の価値を提供するための意思決定を支援します。 Anchors: • 『Inspired』（Marty Cagan） / 適用: プロダクト優先順位 / 目的: 価値最大化 • Intercom RICE Scoringガイド / 適用: 定量的スコアリング / 目的: データドリブンな意思決定 • Kano Model理論（Noriaki Kano） / 適用: 顧客満足度分析 / 目的: 戦略的投資判断 Trigger: Use when prioritizing features, requirements, backlog items, or strategic initiatives. Apply to sprint planning, release planning, roadmap development, feature evaluation, or resource allocation decisions.
スプリント計画の体系的な立案と実行管理を支援するスキル。 チームキャパシティの可視化、タスク分解、リスク管理を通じて、 価値提供と持続可能な速度（サステーナブルペース）を両立させる。 Anchors: • Agile Estimating and Planning (Mike Cohn) / 適用: 見積もり・計画手法 / 目的: スプリント計画の方法論習得 • Scrum Guide / 適用: スプリント計画イベント / 目的: 公式フレームワークとの整合 • ストーリーポイント / 適用: キャパシティ計算・タスク見積もり / 目的: チーム能力の可視化と予測精度向上 Trigger: Use when planning sprints, calculating team capacity, estimating stories, setting sprint goals, or managing iteration cycles. sprint planning, agile, iteration, capacity, velocity, story points, sprint goal, scrum
Conducts systematic root cause analysis using proven methodologies including Toyota's 5 Whys, Ishikawa fishbone diagrams, Pareto analysis, and fault tree analysis. Use when investigating bugs, debugging code, troubleshooting systems, diagnosing equipment failures, analyzing life problems, or identifying underlying causes of any issue across software engineering, hardware maintenance, process failures, or personal challenges.
