「exe」の検索結果

Orchestrate complex development with AUTOMATIC parallel subagent execution, continuous dispatch scheduling, dependency analysis, file conflict detection, and IOSM quality gates. Analyzes task dependencies, builds critical path, launches parallel background workers with lock management, monitors progress, auto-spawns from discoveries. Use for multi-file features, parallel implementation streams, automated task decomposition, brownfield refactoring, or when user mentions "parallel agents", "orchestrate", "swarm", "continuous dispatch", "automatic scheduling", "PRD", "quality gates", "decompose work", "Mixed/brownfield".

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

Use when creating FreeRTOS tasks, queues, semaphores, or mutexes, catching stack overflow, writing FreeRTOSConfig.h, or debugging tasks over OpenOCD and GDB. Not for probe setup: use openocd-jtag.

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

Use when choosing kernel spinlocks versus mutexes, using RCU, seqlocks, completions, or memory barriers, or debugging scheduling-while-atomic. Not for userspace atomics: use concurrency-debugging.

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

Use when explaining branch predictors, mispredict penalties, speculative execution, Spectre or Meltdown mitigations, or branchless code. Not for pipeline stage theory: use cpu-pipelines-and-hazards.

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

Use when the learner is ready to apply cleared concepts in a real project. Not for exercises or quizzes: use drill.

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

Use when building a lexer, Pratt or recursive-descent parser, AST, symbol table, type checker, or LLVM IR emitter for a language or DSL. Not for optimizing IR: use llvm-passes.

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

Use when a course needs numbered problem, solution, and explainer scaffolds. Not for a CLI or Next.js project scaffold: use scaffold-nextjs.

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

Use when a concept needs practising: the user asks for an exercise, quiz, recall, or gap probe. Not for explanations: use explain-concept.

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

Use when writing Bazel BUILD files with cc_library or cc_binary rules, Bzlmod dependencies, toolchain registration, remote execution, sandbox debugging, or bazel query and cquery graphs.

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

Use when asked to execute or investigate a PromQL expression against a Prometheus server. Read-only HTTP queries only. No source or remote-system changes.

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

Use when a knowledge artifact needs review before sharing or execution. Not for source or remote-system changes.

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

Use when a human-curated dbt model index must guide BigQuery SQL for a warehouse question. Not for discovering undocumented models or executing warehouse changes.

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

Use when a LibAFL fuzzer needs an executor, observer, feedback, mutator, scheduler, or objective composed around a target. Not for remote, credential, publish, deploy, or irreversible changes.

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

Use when work is about to grow past the ask, the task may already be done, or the user requests only the minimum. Not for executing the work: use tdd to build or strike-the-root to fix.

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

Optimize a pydantic-ai agent's instructions, tool descriptions, output type, and signature inputs using the gepa CLI. Trigger when the user asks to "optimize this agent", "improve tool descriptions", iterate on prompts driven by eval failures, or otherwise improve a pydantic-ai agent against a dataset. Operates in the user's repo with full filesystem access — YOU are the reflection model; the gepa CLI handles minibatches, evaluation, and Pareto bookkeeping.

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

Convert roman numerals to integers.

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

Design or implement the smallest complete executable evidence for a governed Proto UI behavior. Use for conformance cases, regression tests, cross-layer verification, test-entity mappings, failure-path coverage, or validation-plan design. Do not use tests to decide unsettled semantics.

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

Execute one bounded read-only Proto UI autonomous-maintenance observation mission. Use for drift hunting, external-oracle comparison, repeatability control, or a no-finding maintenance run. Stop before verification or remediation.

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

Measure the active Agent model with pinned offline ModelTrace sampling and return an unsigned closed-set attribution record. Use before Agent-originated commits, Issue/PR creation or material updates, comments, reviews, and current collaboration writes in either execution mode. Do not treat a fingerprint, declared model label, or record reference as authenticated identity, permission, independent review, or acceptance.

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

Independently review a Proto UI change against current authority, bounded scope, executable evidence, projections, provenance, and integration conditions. Use for pull-request review, acceptance review, pre-merge audit, or fresh-context verification. Do not use to approve one's own work.

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

Trace a Proto UI change through authoritative spec lifecycle, legacy explanation, dated context, implementation, executable evidence, package surfaces, and public projections. Use before deciding scope, changing behavior, reviewing a pull request, or investigating drift.

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

Choose local execution versus bounded delegation for Odylith slices and shape routed payloads.

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

Use when a bounded execution note needs to be appended into Compass.

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

Work with Compass timeline and execution-stream evidence for Odylith sessions.

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