「task」の検索結果

Assess development requests, then execute and resume complete TaskBelay tasks in Claude Code with Core-owned state.

日本語の概要は準備中です。原文の説明を表示しています。

Turn one task into a tree of GitHub issues worked by agents. Creates (or reuses) an epic issue, then launches the recursive orchestrator → decomposer → worker pipeline. Use when asked to "decompose a task", "break this down into issues and work it", "spawn agents to build X", or run via /task-decompose.

日本語の概要は準備中です。原文の説明を表示しています。

プラグイン構想から index+13 フェーズファイル+component-inventory.json とタスク粒度の型付き依存グラフ (task-graph) を第3の射影として生成したいとき、後段のrun-skill-createへ渡す前段の開発計画を立て build 中の discovered-task を --mode update の外ループで graph へ還流したいときに使う。

Convert tasks from tasks.md into GitHub issues. Use after task breakdown to track work items in GitHub project management.

日本語の概要は準備中です。原文の説明を表示しています。

gogcli（gog コマンド）の専門家スキル。Google Workspace と関連サービス25以上（Gmail, Calendar, Chat, Drive, Sheets, Docs, Slides, Tasks, Keep, Contacts, People, Groups, Admin, Classroom, Forms, Meet, Maps, YouTube, Photos, Sites, Analytics, Search Console, Apps Script, Zoom）をターミナルから操作するGoベースCLIツールの使い方を支援。OAuth2/サービスアカウント認証、マルチアカウント管理、自動化・エージェント安全機能を提供。Use when working with Google Workspace services via CLI, managing Gmail/Calendar/Drive/Sheets, automating Google Workspace tasks, or setting up gogcli authentication.

Coordinate Codex work across the current task, internal subagents, user-owned tasks, worktrees, handoffs, formal review gates, or recurring automation. Use for delegation, parallel roles, another Codex task, cross-repo work, QA/review handoffs, scheduled follow-up, or task inspection and continuation. Chinese triggers include 子Agent/子进程/子对话, 另一个对话接手, 并行处理, 分给QA, 多仓库收口, 巡检, 持续推进, 定时自动继续, 创建/读取/转交任务.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrates multi-step tasks autonomously using a 3-tier agent hierarchy (Director/Manager/Worker). Use when user says "run this end-to-end", "handle everything", "execute all tasks", or needs parallel task execution with queuing, course correction, and session resume. Provides FIFO task queue, escalation policy, git worktree isolation, and context persistence across agent sessions.

日本語の概要は準備中です。原文の説明を表示しています。

機能・画面の実装着手前に「状態×見た目×周辺」を列挙する体験網羅チェックリスト。宣言外の実装を防ぐ関所として task-run/auto-task 等から使う。

Author or expand browser-agent benchmark tasks in data/real_world_bench.json (Odysseys schema, per-rubric graded). Use when creating, adding, or expanding real-world browser tasks, writing rubrics, or picking bot-friendly sites — every task MUST be verified runnable through ego-browser before it is written.

日本語の概要は準備中です。原文の説明を表示しています。

Search and analyze Estuary task logs with jq filtering. Use when investigating task failures, debugging connector errors, analyzing behavior patterns, or streaming live logs. Use when user says "check logs", "show me logs", "task failing", "why is my capture failing", "why is my materialization failing", "error messages", "why did it fail", "search task logs", "shard failed", "follow logs", "increase log level", "debug logging", "is this log message normal", "what does this message mean", "connection timeout", or "i/o timeout".

日本語の概要は準備中です。原文の説明を表示しています。

Run flowctl catalog status to check the control-plane state of an Estuary resource, or list catalog specs to see which connectors exist and which are active. Use when checking whether a task is running, disabled, or failing, interpreting status output, or enumerating connectors. Use when user says "check task status", "is my capture running", "catalog status", "flowctl catalog status", "what's wrong with my capture", "task failing", "check catalog status", "collection status", "derivation status", "why is my task disabled", "list my connectors", "show me my connectors", "list captures", "list materializations", "what connectors do I have", or "show me all my active connectors".

日本語の概要は準備中です。原文の説明を表示しています。

Use when executing implementation plans with independent tasks in the current session — trigger phrases "execute the plan", "independent tasks", "parallel tasks", "subagents for the plan","split the plan into subagents". Dispatches a fresh subagent per task with two-stage review after each: spec compliance first, then code quality.

日本語の概要は準備中です。原文の説明を表示しています。

Multi-agent SWE team built on the Workshop model. Full-stack vertical workers, meeting room with @mention notification, private pipes, shared task board. Git worktree isolation, Leader-driven coordination. Mixed Codex/Claude Code engine. Use when a task needs engineering depth beyond a single agent. NOT for simple task parallelism (use agent-task-orchestration) or design discussions (use agent-brainstorm).

日本語の概要は準備中です。原文の説明を表示しています。

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

日本語の概要は準備中です。原文の説明を表示しています。

Search the documents uploaded for the CURRENT task/row (e.g. an Agentic Table row's attached files) via the `unique-cli uploaded-search "<query>"` command, with the same per-turn citation tracking as `unique-cli search` so cited facts render as `<sup>N</sup>` footnotes and clickable reference chips on the Unique platform. ALWAYS use this skill when the user refers to documents they uploaded/attached to this task, or when you need facts from the task's own attached files. These uploaded files are scoped to the chat, NOT to a knowledge-base folder, so they will NEVER appear in `unique-cli search` results no matter the folder or metadata filters. Use `unique-cli search` for the knowledge base and this command for the task's uploaded documents; the two are complementary and citation numbering is shared across them within a turn.

日本語の概要は準備中です。原文の説明を表示しています。

Delegate tasks to an external CLI agent (OpenAI Codex, Google Gemini, or Claude Code) for second opinions or parallel execution. Use when the user explicitly mentions "codex", "gemini", or "claude" or asks to delegate work to one of them (e.g., "codexで実行", "codexに聞いて", "geminiで実行", "Geminiに聞いて", "claudeで実行", "Claudeに聞いて", "run with codex", "ask gemini", "ask claude"). Also use when the user mentions Claude's "fable" model alias for delegation or consultation (e.g., "fableで実行", "fableに相談", "Fableに聞いて", "ask fable"). Do NOT use for general coding tasks that don't mention codex, gemini, claude, or fable.

Security-Scanner Agent fuer fabrikIQ und andere Projekte. Fuehrt umfassende Sicherheitspruefungen durch. Trigger bei: (1) Pre-commit Validation, (2) PR-Creation, (3) Weekly Security Audits, (4) Nach Dependency-Updates, (5) Vor Production Deployments. <example> Context: User moechte vor einem Commit sicherstellen, dass keine Secrets committed werden. user: "Ich will gleich committen. Pruefe mal auf Secrets." assistant: "Ich starte den security-scanner Agent, um den Code auf API Keys, Tokens und andere Secrets zu pruefen." <Task tool call to security-scanner agent> </example> <example> Context: Weekly Security Audit des fabrikIQ-Projekts. user: "Fuehre den woechentlichen Security-Scan durch." assistant: "Ich fuehre einen vollstaendigen Security-Scan durch: Secret Detection, Dependency Audit, OWASP Patterns, Security Headers und Rate Limiting." <Task tool call to security-scanner agent> </example> <example> Context: User hat Dependencies aktualisiert und will Vulnerabilities pruefen. user: "Ich habe npm update und pip install -U gemacht. Gibt es Sicherheitsprobleme?" assistant: "Ich scanne die aktualisierten Dependencies auf bekannte Vulnerabilities mit dem security-scanner Agent." <Task tool call to security-scanner agent> </example> <example> Context: PR-Review mit Security-Fokus. user: "Review den PR #42 auf Security-Probleme." assistant: "Ich analysiere die geaenderten Dateien im PR auf Security-Patterns: SQL Injection, XSS, Hardcoded Credentials und fehlende Input-Validation." <Task tool call to security-scanner agent> </example>

日本語の概要は準備中です。原文の説明を表示しています。

Windows アプリ開発 (Windows App SDK / WinRT) の OS 統合 API リファレンス。 DeviceInformation, DeviceWatcher, センサー (Accelerometer, Gyrometer, Compass, OrientationSensor, Pedometer, ActivitySensor), Bluetooth LE, USB, Serial, HID, Battery, HttpClient, StreamSocket, WebSocket, BackgroundDownloader/Uploader, NetworkInformation, PointerInput, KeyboardInput, FocusManager, DragAndDrop, IME/TextInput, Calendar, DateTimeFormatter, CurrencyFormatter, ResourceLoader (多言語化・地域化), PasswordVault, CryptographicBuffer, WindowsHello/Passkeys, WebAuthenticationBroker, Clipboard, DataTransferManager, Launcher, JumpList, TaskbarManager, SecondaryTile, StartupTask, ProtocolActivation。

Swift Standard Library・Concurrency・プロトコル/ジェネリクス・Observation リファレンス。 async/await、actor、Sendable、Task、TaskGroup、AsyncSequence、AsyncStream、 Equatable、Hashable、Comparable、Codable、Identifiable、Optional、Result、 generics、some/any opaque types、Observable、@Observable、ObservationRegistrar。

このMacで定期実行するジョブを新しく作る・作り直す・やめる。エージェントに判断させる巡回は taskboard の定期起動、決まった処理だけのシェルスクリプトは launchd で作り、手順書・状態ファイル・ログ・秘密情報の置き場と、登録後の試運転までを同じ型で揃える。「定期実行を作って」「毎朝◯◯させたい」「毎時巡回させたい」「cronで回したい」「LaunchAgentを作って」等の依頼時、既存の定期実行が失敗・スキップし続けている時、不要になった定期実行を片付ける時に使用。境界: クラウドで動かす routine は schedule、今のセッション内での繰り返しは loop、定期起動の tool の引数・見回りは taskboard。

Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an approved plan needs executing task by task in this session, with a fresh implementer per task and review between tasks

日本語の概要は準備中です。原文の説明を表示しています。

task-list.jsonのタスクを実行。workflowフィールド（tdd/e2e/task）に応じたワークフローで実装。 Trigger: dev:developing, /dev:developing, 実装, 開発, implementing, develop