11 件 ・ 関連度順
概要と使いどころ
This skill should be used when the user asks to "task-breakdown", "タスク分割", "タスク分解", "タスクを分割", "タスクを分解", "WBSを作成", "作業分解", "break down task", "decompose task", "create WBS". 依頼をゴール/制約/前提に正規化し、トップダウンで構造分解（1階層1軸）、粒度の停止条件を適用し、MECE・依存関係・DoD を検証して、ツリー＋表のタスク分割結果を生成する。分野を問わない汎用スキルで、単独利用と他スキル/コマンドからの呼び出しの両方に対応。
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
日本語の概要は準備中です。原文の説明を表示しています。
Converts a specification into a phased, dependency-ordered implementation plan. Use after specification is complete and before execution begins.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks down complex tasks into ordered, verifiable sub-tasks with dependencies, milestones, and risks.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks work into ordered, parallel-dispatchable tasks with an execution DAG. Output format is consumable by CI matrices and parallel agent runners — each task has a stable ID, declared file writes, conflict edges, and branch suffix. Use when you have a spec, brief, or shaper output and need to decompose it into implementable units. Use when a task feels too large, when scope spans multi-repo or multi-week work, or when parallel execution across multiple agents is on the table.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "既存プロジェクトのタスクを整理して", "技術的負債をIssue化して", "このコードベースを改善するタスクを洗い出して", "GitHub Projectに健全化タスクを登録して", "break down what needs to be fixed in this project", "surface tech debt as issues", or "create a project board for cleanup work". Diagnoses pain points and codebase health of an existing project, then registers improvement tasks as GitHub Issues and a Project Board.
Break a clear scope or accepted specification into ordered tasks/packages when the user explicitly asks for a plan, estimate, dependency order, or task breakdown; do not trigger for ordinary implementation, every multi-step task, speculative parallelism, review, or completion.
日本語の概要は準備中です。原文の説明を表示しています。