「handoff」の検索結果

Work on Grida account and billing client adapters, credit display, Console handoffs and native execution receipts. Excludes financial policy and provider operations.

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

Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and release gates—not for clinical decision-making.

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

Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or "reorg". Also trigger when reorganizing engineering teams, aligning team and service boundaries, splitting a monolith and deciding ownership, reducing cross-team handoffs, or designing an internal platform. Covers the four team types, three interaction modes, the inverse Conway maneuver, and fracture planes. For bounded contexts, see domain-driven-design. For dependency direction in code, see clean-architecture.

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

Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.

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

Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to assess delivery risk, or when the same failure keeps recurring. Also use to decide whether to build, hire, or outsource a capability.

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

Plan and carry a Seedance video from brief through references, storyboard, generation handoff, shot-level review, and targeted repair. Use for an end-to-end Seedance production request; use a narrower prompt skill for a single prompt.

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

Orchestrate workflows across multiple applications and APIs — inter-app coordination, data handoff, and multi-system task completion.

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

Manage agent sessions including initialization, handoffs, revival (seance), and persistent identity for Polecats and Crew agents.

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

Draft and review contributions to existing MEX project knowledge in the repo wiki. Use when the user wants to capture a team decision, convention, or architecture note, propose an addition or correction for team review, or invokes /mex-inbox or $mex-inbox. Also supports existing Spec proposals. Keywords: mex, project memory, CLAUDE.md, team memory, drift, inbox. Do not activate for brainstorming alone, routine GROW upkeep, email inboxes, session logs, or handoffs.

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

Draft and review contributions to existing MEX project knowledge. Use when the user asks to capture a discussion or decision in project knowledge, propose an addition or correction for team review, or explicitly invokes /mex-inbox or $mex-inbox. Also supports existing Spec proposals. Do not activate for brainstorming alone, routine GROW upkeep, email inboxes, session logs, or handoffs.

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

Distill the current conversation into a structured note (decisions made, open questions, file pointers with line numbers, next 1–3 actions) and save to `quality_reports/session_logs/` before auto-compression. Differs from `/checkpoint` (explicit stop-point snapshot) and from auto-compaction (which truncates rather than distills). Use when context is approaching auto-compact threshold, when a long pipeline has accumulated many decisions, or when the user says "compress", "distil this session", "before we hit auto-compact", "structured handoff before context resets".

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

End-to-end Chinese video washing pipeline. Use when the user provides a Bilibili, Douyin, Xiaohongshu, YouTube, web video URL, or local video file and asks for 视频洗稿, 视频二创, 洗稿并制作视频, 链接视频改写, 提取逐字稿后洗稿, or producing a new AI video from a source video. Orchestrates ra-逐字稿提取skill and ra-洗稿, ending at the 01-内容生产/视频工作台/待制作/ handoff queue; production continues through ra-video-production-director only on explicit request (直接制作/直接出片/一条龙).

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

视频脚本洗稿和二创脚本工作流。Use when the user provides an existing transcript, oral draft, viral script, competitor video text, rough topic notes, or wants 洗稿, 二创改写, 爆款视频脚本重写, 逐字稿改成短视频脚本, rewrite with ra-人话, and queue the approved script into 01-内容生产/视频工作台/待制作/ as the handoff contract for video production. If the user provides a video URL or local video file and asks 视频洗稿、视频二创、洗稿并制作视频, use ra-video-wash-pipeline first.

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

Use when generating or auditing a multi-role agent team package with orchestrator, PM Soul, Memory Curator, Policy Gate, workers, eval, QA, handoffs, and runtime adapters.

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

Use when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system.

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

Monitor current news and reaction signals, then decide which are credible newsjacking opportunities for a client. Uses the local monitoring engine for evidence, but the skill owns PR judgment, brand safety, standing, decay, angle fit, and handoff.

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

Shared work-item templates and conventions for ADO and GitHub backlog handoff across the RAI, Security, SSSC, Accessibility, and Privacy planners

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

Requirements authoring guide for BRD and PRD across Discover, Define, and Govern with canonical templates and handoff contracts

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

Security planning and plan-drift analysis for STRIDE, standards, controls, backlog handoff, current findings, and TM7 generation.

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

On-demand RAI planner reference pack covering Phase 1 capture, Phase 2 risk classification and the optional Mural board bootstrap, Phase 5 impact assessment, and Phase 6 review and backlog handoff.

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

Read-only PRD-to-work-item hierarchy planning. Use to turn a PRD into a validated Azure DevOps, GitHub, or Jira handoff.

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

Mutating backlog execution for Azure DevOps, GitHub, and Jira. Use to create one item or apply a reviewed handoff to a confirmed tracker.

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

Produce evidence-labelled UX needs, journey, structure, inclusion, and engineering-handoff assets. Use when a practitioner needs a durable UX artifact rather than coaching.

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

Authoring skill for Architecture Decision Records (ADRs) supporting capture, from-planner-handoff, and adopt-template entry modes with selectable Y-Statement or MADR v4.0.0 output templates, supersession lineage, and ASR trigger evaluation.

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