「cer」の検索結果

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.

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

Find web sources with query-relevant page excerpts and optional full-page content, and discover workflows, data APIs, and indexes. Use for web research or finding structured records, listings, transcripts, and datasets. Supports semantic tool discovery, domain matching, and progressive catalogue browsing.

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

Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.

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

Integracao completa com Amazon Alexa para criar skills de voz inteligentes, transformar Alexa em assistente com Claude como cerebro (projeto Auri) e integrar com AWS ecosystem (Lambda, DynamoDB, Polly, Transcribe, Lex, Smart Home).

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

Geracao de imagens humanizadas via Google AI Studio (Gemini). Fotos realistas estilo influencer ou educacional com iluminacao natural e imperfeicoes sutis.

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

/cs:aims-audit <scope> — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation. Use before certification stage 1, before annual internal audit cycles, or when onboarding a new AI system into an existing AIMS.

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

Use when implementing or modifying NgRx state management in Angular applications, especially state slices, events, reducers, effects, selectors, and store registration.

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

Forces every code-related claim to include file:line citations. No citation means the claim must be verified or removed. Use when building documentation, writing code reviews, or any output that others will rely on.

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

Complete methodology for preventing AI hallucinations. Use when accuracy is critical and you need Claude to verify before claiming, cite before asserting, and admit uncertainty instead of guessing.

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

Diagnose an uncertain bug by designing experiments that distinguish competing causes, especially speculative cache, timing, environment, or concurrency explanations.

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

Trace the purpose of suspicious legacy code using current callers, tests, and Git history when deciding whether it can be changed or removed.

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

Use for analytical thinking, or when a question needs breaking down and evidence: "why did metric X drop?", "what drives this?", "break this down", "what data do we need?". Builds a tree, hypotheses and evidence, ends with an answer and key uncertainty. Skip for quick verdicts.

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

Select the smallest useful Codex engineering workflow from this repository's existing skills. Use when a task spans multiple engineering concerns, the user is unsure which skill to invoke, or loading every specialist would waste context; return a recommendation only and do not execute the engineering task.

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

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

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

Turns a vague "what should we do about X" into a scored decision - explicit actions, an explicit unknown, an explicit prior, and one utility scale - then picks by maximum expected utility and checks the result for framing effects. Use when facing a choice between options under uncertainty, when a decision has stalled in circular debate, when someone asks "should we do A or B", or before writing any decision record, strategy memo, or roadmap commitment.

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

Prepare and risk-check the next rolling-wave slice for implementation. Use when the user wants to continue a rolling-wave project, draft one bounded slice in the main context by default, use a fresh planning author only when context or discovery cost warrants it, use a fresh preparation reviewer when semantic risk or uncertainty warrants independent pressure-testing, decompose parallel implementation chunks where appropriate, identify agent, human, either, or hybrid execution fit, write or update docs/rolling-wave/{project}/slices/NNN-slug.md, and mark that slice ready even when other slices are active.

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

Review local git changes before opening a PR or merging. First review all local tracked and untracked files; if none exist, review the current branch against a requested base branch or the Git Town parent branch. Use zero to three review subagents only when risk, diff size, language specificity, or uncertainty justifies the token cost, then report high-confidence bugs, regressions, risky assumptions, and missing tests. Use when the user asks for code review, local review, branch sanity check, pre-PR review, or review of work-in-progress changes.

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

Subagent flow for deep-reading GitHub issues + their linked/closing PRs to the bottom. Captures CURRENT state, maintainer status updates, reporter repro, blocking reviewer concerns, hidden second bugs, cross-repo duplicates. Invoked by weekly-report orchestrator; runs as a general-purpose subagent so the orchestrator's context stays small.

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

Expert-level biomaterials covering biocompatibility, metals, ceramics, and polymers for medical implants, surface modification, host response, and regulatory considerations.

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

Expert-level quantum mechanics knowledge. Use when working with wave functions, Schrodinger equation, quantum states, operators, uncertainty principle, quantum tunneling, spin, angular momentum, perturbation theory, or quantum entanglement. Also use when the user mentions 'wave function', 'Schrodinger', 'Heisenberg', 'quantum state', 'eigenvalue', 'superposition', 'tunneling', 'spin', 'Hilbert space', 'Dirac notation', 'commutator', or 'quantum measurement'.

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

Expert-level molecular biology knowledge. Use when working with DNA replication, transcription, translation, gene regulation, cloning, PCR, sequencing, CRISPR, epigenetics, or molecular techniques. Also use when the user mentions 'DNA replication', 'transcription', 'translation', 'gene expression', 'PCR', 'cloning', 'restriction enzyme', 'gel electrophoresis', 'Western blot', 'CRISPR', 'epigenetics', 'promoter', 'enhancer', or 'RNA splicing'.

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

Calcule la vélocité des sprints terminés (Σ points des tickets feuilles livrés) et recommande la capacité du prochain sprint. À lancer en fin de sprint. Thin wrapper bash sur sprint_velocity.sh, zéro LLM lourd. Usage: /velocity [<titre-sprint>]

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

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

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

Use when choosing .NET concurrency patterns for async I/O, queues, pipelines, or thread safety. Keywords: async/await, channels, dataflow, Rx, lock contention, producer consumer, parallel processing.

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