「handoff」の検索結果

Maintain stewardship protocol continuity and tool/personality boundaries. Use when a repo agent needs steward-mode threshold checks, self-model update decisions, delegation hygiene, boundary violation review, or handoff-safe continuity context without overclaiming steward personality.

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

Use when a HyperFrames composition needs a punch-in, punch-out, zoom, reframe, Ken Burns treatment, camera move, visual match/whip handoff, or other seek-safe 2D/3D keyframes; also for GSAP, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.

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

Generate reusable multi-step agent workflow blueprints. Use for trigger/action orchestration, deterministic workflow definitions, and automation handoff artifacts.

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

Operate the WeChat Official Account AI-application workflow for articles, weekly digests, rich formatting, draft-box updates, and local handoff. Use for Agents, MCP, Skills, tool calling, workflows, and open-source AI updates; exclude Xiaohongshu and Xianyu.

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

Use when the 文档/交付 role maintains client-facing project delivery document packages, especially Word/DOCX deliverables such as delivery lists, demo scripts, acceptance forms, change confirmations, quote notes, contract-adjacent materials, README/docs indexes, and internal handoff notes.

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

Use when splitting content work between a raw drafting model/window, an editor-in-chief, and the user's final taste review. It keeps prompts loose enough for judgment while preserving facts, account boundaries, and publish gates.

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

Capture a POC's signed-off behaviour into its spec ledger (`<poc>/spec.json`) — the structured, walkable behaviour contract graduation freezes as authoritative. Run at the moment a behaviour gets signed off ("ok, this works"), while it's fresh — the same trigger as the HANDOFF.md update, but capturing the *behaviour as a testable entry* rather than the *decision as prose*. Use when a POC behaviour is approved, or asked to "capture this spec", "write the spec entry", "log this to the ledger".

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

At the close of an epic (or a difficult issue), post a postmortem roundup comment — what went well, what was hard (backed by evidence), and 1–3 concrete proposals to improve the skills/flows — then offer to turn accepted proposals into their own `workflow`-labeled tasks, and end with a `🔭 Next` handoff (a paste-ready next-session prompt + the next epic to start). Use at epic close, after the "verify the whole thing" rollup, or when asked to "do a retro", "postmortem this epic", "what did we learn", "how do we improve the workflow".

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

Emit a blocking question the owner can read in ~10 seconds and answer in one reply — the scannable, recommendation-first handoff every agent posts when it hits a fork it can't own. Leads with the one decision + a recommendation, carries the 🤖 provenance header, doubles as the

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

Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.

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

Use when work needs Scrum roles, ceremonies, backlog refinement, sprint planning, story delivery, release readiness, or role handoffs.

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

Use for project memory, decisions, handoffs, genome, knowledge index, changelog, and patterns that must persist across sessions.

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

Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.

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

Set up notebook-connector configuration for Exasol AI workflows through the Secrets Python API. Covers secure config store (`scs`) creation, the `AILabConfig` and `StorageBackend` key sources, backend-specific config values such as `db_host_name`, `db_schema`, `storage_backend`, and `huggingface_token`, Python validation, and handoff to downstream notebook-connector skills.

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

Generate a context-rich briefing prompt for an external agent (Claude Code, Cursor, etc.)

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

Use when designing, reviewing, implementing, or validating UI/UX and frontend experiences for web, mobile, responsive apps, design systems, Figma-to-code handoff, frontend stack/library selection, personas, UX mapping, information architecture, UI patterns, accessibility, interaction design, UX research, usability testing, theme/token application, or XR/spatial interfaces.

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

別セッションのエージェントが会話文脈なしで読んで下流タスクに着手できる、自己完結な引き継ぎドキュメントを書く。要件定義・基本設計・引き継ぎ書・PRD・README など、別セッションのエージェントへ渡して作業を継続させる成果物を書く・仕上げるときに使う。

Use when the user starts a non-trivial coding/building task in Claude Code (e.g. "帮我做个 X", "help me build Y", "add feature Z", "搭一个 Z"). Layers an AI-native pedagogical coat over normal coding work — surfaces implicit assumptions in user intent, annotates non-trivial design decisions inline with brief concept-scaffolding for terms the user may not know, and replaces "should I run it?" handoffs with rigorous AI self-verification plus a clean list of what only the user can verify. Skip for pure Q&A, single-line edits, read-only investigation, or refactoring along an existing pattern.

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

Load when executing or resuming an approved plan from `dev/active/<task>/` or `.worktrees/<task>`, including phase commits, verification, PR creation, and handoff; not for plan authorship or review.

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

Baut aus einem Chatverlauf oder aus bestehenden Automatisierungs-Prompts (z. B. eines anderen Agenten-Systems) eine selbstlaufende, user-neutrale Workflow-Automatisierung: einen wiederkehrenden Prompt bzw. Automations-Skill für Cron/Schedule/Loop. Alias: automations-extractor. Nutze diesen Skill bei „mach daraus eine Automatisierung", „das soll regelmäßig/nächtlich laufen", „extrahiere Workflows aus diesen Chatverläufen/Automationen", „Automation aus dieser Session bauen", oder bei `/workflow-extract`. Ergänzt fehlende Automations-Bausteine (Rotations-Auswahl, Check-Registry, Idempotenz, Log-Hygiene, Freigabe-Gate, Eskalations-Handoff, Monitor-Meldedisziplin) systematisch. Enthält auch den Fleet-Audit-Modus: bestehende Automations-Flotten auf Silent-Failures, Redundanz, Drift und Lücken prüfen („prüfe meine Automatisierungen/Scheduled Tasks/Cron-Jobs"). Soll stattdessen ein abrufbarer Skill (Fähigkeit auf Zuruf) entstehen, den Schwester-Skill skill-extractor nutzen.

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

Print a ready-made /compact line in a canonical handoff format, so the operator pastes it as the next message and shrinks working memory without losing the thread. Use at the end of a long session. Triggers: "/cc", "compact", "finish via compact".

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

Agentic design-to-build pipeline that turns a Figma design into a built WordPress site using the Figma MCP server (read side) and the Elementor MCP server (write side) attached as MCP Apps on an NV oOS assistant. Covers the 7-stage pipeline (Scope → Read → Plan → Tokenize → Build → Verify → Handoff), the normative stage rules (get_design_context first, tokenize before build, drafts only, never publish, Figma read-only), the build-manifest contract (schema + example in reference/build-manifest.md), the design-file contract (frame/section/variable naming in reference/design-file-contract.md), assistant wiring (figma + elementor MCP Apps, OAuth + application passwords, host allowlist), safety rules, and troubleshooting. Use when asked to build or create a site, page, or landing page from a Figma design, to wire Figma MCP or Elementor MCP for design-to-build work, to approve or produce a build manifest, or to debug a failed design-to-build run.

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

Use when a user provides a GitHub URL and the planner needs to converge that repo plus the user's goal into a concrete project blueprint for later execution. This skill handles GitHub-input project intake, Phase 1 intent convergence, and downstream project handoff structure. It does not generate teaching material packages.

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

Use when the user asks to "plan my site structure", "design the page hierarchy / navigation / URL taxonomy", "fix internal linking", or "find orphan pages"; runs two modes — architecture (hierarchy, nav, URL patterns, hub/spoke clusters, Mermaid site maps) and linking (link graph, authority flow, anchor text, orphan disposition, source/target/anchor plan) — and outputs a structure score /100 plus a handoff summary. Not for external backlinks — use offsite-signal-analyzer; not for XML sitemap or indexation issues — use technical-seo-checker. 网站架构/信息架构/站点地图/内链优化

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