incident-rca
インシデント調査で根本原因を特定するためのなぜなぜ分析ファシリテーションツールです。推測を避け、ユーザーの発言を記録し、リアルタイムでマインドツリーを作成して全体を可視化します。複合要因を分割し、最低1つの根本原因を特定します。
インシデント調査で根本原因を特定するためのなぜなぜ分析ファシリテーションツールです。推測を避け、ユーザーの発言を記録し、リアルタイムでマインドツリーを作成して全体を可視化します。複合要因を分割し、最低1つの根本原因を特定します。
Primary orchestration hub that FIRST enforces skill discipline (checking for applicable skills before any action), then manages deliverables, deadlines, team coordination, priority coaching, and work-life balance. Provides structured task management, daily standups, and orchestrates specialized skills when technical deep-dives are needed.
Event Storming 引導專家,透過 Plan Mode 問答帶領使用者完成 Event Storming 工作坊,識別 Domain Events、Commands、Actors、Policies 等元素,最終生成 Markdown 文件。
Issue解決のための高度な思考プロセスと手順を定義したスキル。柔軟な判断が求められるIssue対応全般を担当する。
Brutal, honest critique of strategies, plans, and analyses. Use when someone explicitly wants their thinking torn apart, stress-tested to destruction, or called out on weak logic. Triggers include requests like "tear this apart", "be brutal", "what's wrong with this", "play devil's advocate", "tell me why this won't work", or "poke holes in this". This is adversarial by design, not for collaborative exploration, but for ruthless pressure-testing.
複雑なタスク(3ステップ以上・複数ファイル変更)の実装前に使用。計画ファイルを作成し進捗を追跡。
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
Create or audit requirements-to-design-to-code-to-test traceability. Builds a traceability matrix (REQ → design/ADR → implementation files → tests → evidence) and flags gaps (unimplemented requirements, untested changes, undocumented decisions). Use when you need a requirements traceability check for a PR/release, regulated/compliance work, or when requirements are drifting from implementation.
구현 계획 수립. Use when (1) "계획 세워줘", "설계해줘", (2) 복잡한 기능 구현 전, (3) 리팩토링 계획. ⚠️ 특화된 계획은 별도 스킬 사용: - 테스트 계획 → write-test 스킬
Ably real-time messaging patterns, WebSocket channel management, message validation and processing, staleness filtering, error recovery strategies, collaborative editing with drag-and-drop, optimistic updates for voting, real-time board collaboration, and Ably integration best practices for ree-board project
Open source community building and engagement. Welcoming contributors, managing discussions, writing release notes, and fostering a healthy project ecosystem.
FreightClub/ShipStation Shipping Data Analysis v3.0 - Enhanced with Revenue Architect rubrics. Triggers on: "freightclub analysis", "shipping data analysis", "PLD analysis", "shipstation export" Use when: Customer provides shipping data export for rate analysis or FirstMile opportunity assessment.
Create or refine VibeFlow issue files under issues/. Use when turning plan items into implementable tasks with clear acceptance criteria.
Comprehensive SessionStart hook showing PhD countdown, project status, uncommitted changes, and loaded todos.
Guide for executing engineering plans through coordinated subagent work. Use when executing existing plans from knowledge/plans/ directory.
Lightweight Linear skill for fetching issue details. Returns only essential data (title, description, state, assignee) to optimize context usage compared to full Linear MCP.
Personal research backlog. Quick-capture ideas for later exploration. Check when you have unstructured time.
Cost-effective task delegation strategy using Haiku model for straightforward work. Use when planning how to approach simple, pattern-following tasks to minimize costs.
開発作業のタスクリスト(tasklist.md)を生成します。このスキルは単独で使用することも、generate-working-docsから呼び出されることもあります。
Apply SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion) for systematic development. Use for feature development, TDD workflows, and structured problem-solving.
Manages GitHub issue blocking/blocked-by relationships using the native dependencies feature via GraphQL API. Use when showing that one issue must complete before another can proceed, querying dependency relationships, or preventing circular dependencies.