1.8万 件 ・ 関連度順
概要と使いどころ
Manage Codex Taskboard issues and taskctl setup when the request names Codex Taskboard, e-taskboard, or taskctl, or the conversation already establishes that board as the target. Not for GitHub, Phabricator, other external trackers, or unrelated product docs.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks down complex software, writing, or research tasks into small, atomic, independently completable units with dependency graphs and milestone breakdowns. Use when the user asks to plan a project, decompose a feature, create subtasks, split up work, or needs help organizing a large piece of work into a step-by-step plan. Triggered by phrases like "break down", "decompose", "where do I start", "too big", "split into tasks", "work breakdown", or "task list".
日本語の概要は準備中です。原文の説明を表示しています。
Quality gate: verify each acceptance criterion of a completed task/work unit, run quality checks, and create follow-up tasks for gaps. Use before merging or to audit delivered work. Invoked as /agiflow:review-work <work-unit-or-task>. Uses get_work_unit, get_task, update_task, create_task, create_task_comment.
日本語の概要は準備中です。原文の説明を表示しています。
Create a feature branch for a backlog task, switch to it, and start implementation. Use when the user says "start task-123", "work on task-123", "implement task-123", or invokes /start-task with a task ID.
日本語の概要は準備中です。原文の説明を表示しています。
Use when executing a task the orchestrator dispatched — reads the task and its orchestrator response from the work ledger, loads task-level skills, implements against acceptance criteria, records divergences and the completion report as task sections, and closes the attempt. Triggers on task execution within the implement-feature loop or when an agent picks up a specific task from a plan.
日本語の概要は準備中です。原文の説明を表示しています。
Use when orchestration or planning agents are producing task plans, task prompts, or TASK.md instructions that must be unambiguous, verifiable, and resistant to hallucination. Applies CLEAR (Concise, Logical, Explicit, Adaptive, Reflective) to structure and write agent task prompts, then adds CoVe (Chain of Verification) checks where accuracy risk is meaningful. Activates on draft task prompts, swarm plans, migration tasks, and multi-step plans requiring independently executable steps.
日本語の概要は準備中です。原文の説明を表示しています。
Manages feature implementation task state via SAM MCP tools. Use when querying task status, listing ready tasks, dispatching tasks for execution, updating task timestamps, or coordinating multi-task feature rollout. Activated by the /dh:execution orchestrator to track progress — also activates directly when managing tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Claude Code native Tasks from an existing spec. Use when user says "create tasks", "generate tasks from spec", "spec to tasks", "task generation", or wants to decompose a spec into implementation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Execute pending Claude Code Tasks in dependency order with wave-based concurrent execution and adaptive verification. Supports task group filtering and configurable parallelism. Use when user says "execute tasks", "run tasks", "start execution", "work on tasks", or wants to execute generated tasks autonomously.
日本語の概要は準備中です。原文の説明を表示しています。
Implement a single Flutter task following this repository's Riverpod, Freezed, AutoRoute, DTO/entity, codegen, and verification conventions. Reads the task definition, PRD, and tech spec, then executes the implementation. When invoked standalone, verifies the change; when invoked by implement-tasks-sequence, writes code only and leaves verification to start-job/build-verify. Use when the user says "implement task X", "work on task X", or wants to execute a specific task from the task list.
日本語の概要は準備中です。原文の説明を表示しています。
Implements sub-tasks from a task list at .ai/[feature]/tasks.md strictly one at a time, stopping after each to ask the user before starting the next, and keeping the task list and Relevant Files section current. Use when the user wants to review or approve each sub-task before work continues, rather than letting the agent run the list unattended with task-orchestration.
日本語の概要は準備中です。原文の説明を表示しています。
Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.
日本語の概要は準備中です。原文の説明を表示しています。
フォルダ型のタスクチケット（1ファイル1タスク、todo/doing/blocked/done フォルダ）を定期的に1件ずつ拾って実行し、結果をチケットに書き戻すスキル。毎回、状況を一目で把握できる看板ボード形式のダッシュボード（tasks/dashboard.html）も更新する。Coworkのスケジュール実行（1時間ごと等）から呼ばれる想定。「タスクを1件処理して」「tasksフォルダをチェックして」「タスクランナーを実行」「task-runner」「今日のタスクを進めて」「タスク管理の初期設定」「タスクの状況を見せて」「タスクのダッシュボード」「看板ボード」などと言われたら、明示的にスキル名が出ていなくても必ずこのスキルを使うこと。
Create, verify, transfer, and resume compact project handoff packets for long-running Codex work. Use after a second observed automatic context compaction, immediately after a third compaction, when attention or constraints degrade, a major phase ends, the user asks to move work into a fresh task, work must pause, or an existing handoff needs to be imported. Do not interrupt after the first normal compaction. Always ask before creating a new task, transfer the global roadmap only after explicit consent, preserve the old task title when available, then require the fresh task to ask what work matters most. Preserve objectives, constraints, decisions, evidence, approval boundaries, workspace state, validation, and risks without treating an old summary as current truth.
日本語の概要は準備中です。原文の説明を表示しています。
Read-only measurement of an agent's autonomy debt from its approvals log: how many times it asked the human for permission in a window, how many asks expired unanswered, and which classes they fall into (machine noise, login or 2FA, physical UAC, money). Use to find asks the agent should have decided itself and to cut needless interruptions. Triggers: /ask-debt, autonomy debt, how often do I ask, expired asks.
日本語の概要は準備中です。原文の説明を表示しています。
Manage the NV oOS Pro Toolkit Project Management system — projects, tasks, events, sprints, task plans, task templates, and PM workflow rules. Covers complete project lifecycle (planning → active → completed), task tracking with priorities and effort estimation, sprint planning, event scheduling with attendees, and template-driven task plan generation. Use when managing projects, creating or tracking tasks, planning sprints, scheduling events, generating task plans from templates, assigning work to team members, or troubleshooting project management data.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user presents an idea/plan/proposal and wants a specific 16-minds (MBTI) personality to ask probing questions back — instead of giving an answer. Triggers on Japanese phrases like 「ENTPでツッコんで」「INFJに問い詰めて」「ENTJ視点で質問して」「このアイデア叩いて」, English equivalents like "as ENTP, question this" / "INFJ would ask what?", or 16-minds commands with a `--ask` flag. AIに「答えさせる」のではなく「問わせる」ためのSkill。ユーザーが思考を整理したい時に使う。
claude-task-worker のカスタムワーカー（`workerFiles` に登録する TS 定義）を、`AskUserQuestion` で要件を全項目確定させてから生成し、`claude-task-worker list-workers` でロード検証までするスキル。「カスタムワーカーを作って」「独自のワーカーを追加したい」「新しいラベルで動くワーカーを定義したい」といったリクエストで使用する。
Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required. Use when asked to "tune questions", "stop asking me that", "too many questions", "show my profile", "what questions have I been asked", "show my vibe", "developer profile", or "turn off question tuning". (gstack) Proactively suggest when the user says the same gstack question has come up before, or when they explicitly override a recommendation for the Nth time.
日本語の概要は準備中です。原文の説明を表示しています。
Cleanup and triage of the task ledgers FOUND_DEFECTS.md, CURRENT_ERRORS.md, .matrx/AGENT_TASKS.md, .matrx/ARMAN_TASKS.md. Use when invoked as /task-hygiene <step>, cleaning up tasks, defects, or errors, triaging an error dump, promoting defects, or bootstrapping these files.
日本語の概要は準備中です。原文の説明を表示しています。
Writes custom MSBuild tasks. ITask, ToolTask, IIncrementalTask, inline tasks, UsingTask.
日本語の概要は準備中です。原文の説明を表示しています。
複数の Claude Code エージェントに開発作業を割り振り、個別の作業環境で並行実行しながら、依存関係・進捗・変更内容やエラーの報告を管理するスキル。
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
日本語の概要は準備中です。原文の説明を表示しています。
Use before direct filesync calls, reading non-task shared files, pushing mid-task progress, or troubleshooting missing shared files. Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally.
日本語の概要は準備中です。原文の説明を表示しています。