project-management
4
handler-work-tracker-linear
[DEPRECATED] Linear handler - Use Fractary CLI instead
fractary
business
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
project-management
4
goal-setter
Helps set effective goals, prioritize work, and manage time. Use when: setting OKRs or goals, quarterly planning, prioritizing work, managing time, or diagnosing why goals aren't being met. Includes: NCT Framework, GEM Prioritization, LNO Time Management frameworks. Sources: Ravi Mehta, Gibson Biddle, Shreyas Doshi.
qingxuantang
business
project-management
4
estimation-techniques
ストーリーポイント、プランニングポーカー、相対見積もりを用いたアジャイル見積もり技法。 チーム合意に基づく予測可能性と柔軟性を両立する見積もりプロセスを実践する。 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. 見積もり, ストーリーポイント, プランニングポーカー, ベロシティ, 相対見積もり, スプリント計画, 工数見積もり
daishiman
business
project-management
4
start-working
Autonomously execute ALL tasks from the backlog until complete. Runs in a continuous loop - picks task, implements via subagent, moves to done, repeats. No user prompts between tasks. Follows task-board workflow (backlog → in-progress → done).
andersnygaard
business
project-management
4
log-capturer
Captures Claude Code conversation sessions in structured markdown format tied to work items with redaction
fractary
business
project-management
4
agentuity-cli-project-show
Show project detail. Requires authentication. Use for project management operations
agentuity
business
project-management
4
leadership-coach
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.
qingxuantang
business
project-management
4
agent-lifecycle-management
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
daishiman
business
project-management
4
chain-of-thought
複雑な問題を分解し、推論の流れを整理して短い根拠サマリーを作成するスキル。 前提整理、論点分解、選択肢比較、判断理由の要約を通じて、説明責任のあるアウトプットを作る。 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.
daishiman
business
project-management
4
speckit-constitution-zh
从交互式或提供的原则输入创建或更新项目章程，确保所有依赖模板保持同步。用于项目管理、规范制定、章程维护和团队协作场景。触发词包括 "speckit章程"、"创建章程"、"更新章程"、"项目章程"、"制定规范"、"团队章程"。
forztf
business
project-management
4
label-manager
Add, remove, and list labels on issues via Fractary CLI
fractary
business
project-management
4
systematic-debugging
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
alexanderop
business
project-management
4
task-specification-creator
ユーザーから与えられたタスクを単一責務の原則に基づいて分解し、 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.
daishiman
business
project-management
4
prioritization-frameworks
優先順位付けフレームワークの専門スキル。 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.
daishiman
business
project-management
4
sprint-planning
スプリント計画の体系的な立案と実行管理を支援するスキル。 チームキャパシティの可視化、タスク分解、リスク管理を通じて、 価値提供と持続可能な速度（サステーナブルペース）を両立させる。 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
daishiman
business
project-management
4
root-cause-analysis
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.
markpitt
business
project-management
4
requirements-triage
複数の要件や要望を体系的に分析・評価し、実装する項目を決定するスキル。 MoSCoW分類、優先度スコアリング、影響分析を提供する。 プロジェクト初期段階での要件整理から、開発中の追加要望への対応まで幅広く活用できる。 Anchors: • Software Requirements (Karl Wiegers) / 適用: 要件優先順位付け / 目的: リソース最適配分 • Lean Analytics (Alistair Croll) / 適用: ビジネス価値評価 / 目的: 戦略的決定支援 • Prioritization Frameworks / 適用: MoSCoW, RICE, Kano / 目的: 体系的な優先順位決定 Trigger: Use when triaging multiple requirements, prioritizing features, defining scope, or making resource allocation decisions. requirements triage, priority scoring, MoSCoW classification, scope management, feature prioritization, 要件トリアージ, 優先順位付け
daishiman
business
project-management
4
ghe-checkpoint
POST a progress checkpoint to the CURRENTLY ACTIVE thread. Saves work state without changing phases. Requires an already-claimed in-progress thread. USE THIS SKILL WHEN: - User says "post a checkpoint" or "save my progress" - User says "update the issue" or "record current state" - User says "checkpoint" or "save checkpoint" - User completed a milestone and wants to record it - User encountered a blocker and wants to document it - User is about to take a break and wants to save state - Meaningful state change occurred during work PRECONDITION: User must already have an active (claimed, in-progress) thread. DO NOT USE THIS SKILL WHEN: - User wants to SEE status (use ghe-status) - User wants to START work on new issue (use ghe-claim) - User wants to FINISH current phase and MOVE to next (use ghe-transition) - User wants reports (use ghe-report) - No active thread exists (must claim first) EXAMPLES: <example> Context: User working on DEV wants to save progress user: "Post a checkpoint" assistant: "I'll use g
Emasoft
business
project-management
4
todo-backlog
Use when working on a project with a .todo/ backlog directory, or when asked to create/manage task files
oribarilan
business
project-management
4
issue-linker
Create relationships between issues via comment references
fractary
business
project-management
4
task-decomposition
複雑なタスクを目的・成果・制約から分解し、実行可能な作業単位に落とし込むスキル。 依存関係、優先順位、検証条件まで整理して、実行計画を一貫した形で提示する。 Anchors: • PMBOK Guide / 適用: WBS作成 / 目的: 分解粒度と成果物の整合 • User Story Mapping (Jeff Patton) / 適用: 価値分解 / 目的: 価値順序の可視化 • The Pragmatic Programmer / 適用: 反復計画 / 目的: 実行可能性の担保 Trigger: Use when breaking down complex work, clarifying ambiguous tasks, or planning phased execution. task decomposition, work breakdown, WBS, dependency mapping, phased planning
daishiman
business
