「resume」の検索結果

Use when ending or pausing a Claude Code session whose work must continue in a fresh session — user says "create a handoff", "write a handoff", "I'm ending this session", "prepare for a fresh session", "hand this off", or "/handoff" — or when starting a session in a project that already contains a HANDOFF.md at the root ("resume", "pick up where we left off", "continue from the handoff"). Also relevant when a session shows degradation symptoms — Claude contradicted an earlier decision, re-explored something already established, hallucinated file contents, or the user says the session "feels off", "is getting confused", or "context is running low".

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

Use Codex (CLI + AppServer) as the full agent provider — planning, tool orchestration, native compaction, MCP tools, session resume — in place of the Claude Agent SDK. ChatGPT subscription or OPENAI_API_KEY. Per-group via agent_provider. Distinct from using OpenAI as an MCP tool (where Claude remains the planner).

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

Run a seven-agent adversarial pipeline against a resume and cover letter before submission. Produces channel-conditional verdicts anchored to the realistic applicant pool, separates materials quality from submission expected value, and ends with a contrarian pass that can overturn the verdict.

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

Build a targeted resume and cover letter for a role folder that already has a job description and role analysis. Runs iterative adversarial review rounds until the materials stabilize, then hands off for human review before submission.

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

An adversarial job search that gets better as it goes. Set up a job-search workspace, search a careers board and score roles against the realistic applicant pool, build a resume and cover letter, review them with seven agents that return a verdict per submission channel, then write what the review finds back into the profile. Invoke with /slushpile and name what you want to do.

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

Redesign the resume and cover letter templates into your own house style. Changes typography, palette, and layout while holding the ATS constraints fixed, then proves the result still compiles and still extracts. Run any time; not a pipeline stage.

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

Set up a slushpile workspace. Ingests an existing resume or LinkedIn export, interviews the user to fill the gaps, then writes profile.md, preferences.yaml, and stories.md. Run once per workspace, before any other slushpile skill.

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

Gate resumption of any multi-day LLM batch-scoring campaign that calls an unpinned model alias (deepseek-chat, gpt-*-latest, gemini-*-preview, any provider alias without a pinned version). Use when: (1) resuming a paused or credit-exhausted scoring run days after its last chunk, (2) topping up credits to finish a campaign, (3) extending a cached scoring pipeline with new items. Prevents silently splicing two model versions or serving revisions into one measure. Verified 2026-07-16: for $0.30 caught a serving-revision drift WITHIN DeepSeek v4-flash (same alias, same family, litigation scores systematically shifted across a 2-day gap) before an $83 resume spend.

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

Persistent Codex-style goal tracking for pi. Use when the user explicitly asks to set, continue, audit, pause, resume, complete, or inspect a long-running goal.

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

Orchestrates 6-phase SDLC pipeline (discovery, requirements, architecture, workstreams, implementation, summary) for guided feature development. Use when user runs /core:develop command, requests spec-driven development, wants to create implementation plans with architecture decisions, or mentions "SDLC", "spec-driven", "plan feature", "development pipeline". Supports plan persistence, wave-based resume, autonomous mode, and architecture/implementation verification.

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

Create, import, analyze, resume, or revise an end-to-end Circuit Weaver electronic design from requirements through validated functional KiCad schematics, placement review, and a truthful manufacturing handoff. Use for new designs and for existing KiCad/PCB/Gerber projects that need durable state. Use kicad for one-off file inspection, bom for standalone sourcing, and design-wizard only when the user explicitly requests the slower questionnaire.

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

Create, import, analyze, or resume an end-to-end Circuit Weaver electronic design with durable project state. Load the canonical workflow from skills/circuit-weaver/SKILL.md. Use kicad for one-off file inspection, bom for sourcing, and design-wizard only when explicitly requested.

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

Start a session from what was left - trace saves, briefs, proposals, review reports, issues - and ask what to continue. Never resume or implement automatically.

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

Save where the session stands before ending it, so next can resume it in a clean context. Also reads or records project progress.

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

Create, update or resume a GitHub issue as durable resolution memory when requested.

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

The art-route layer of the Forge skills. route_media.py is the one command that generates an image or an image-to-video clip - through the paid API of any provider whose key is configured (OpenAI, Google Gemini, xAI, BytePlus ModelArk, fal.ai; the configured key is the owner's consent), else through the user's own signed-in Codex or Grok CLI - and prints one JSON line with the route, artifact, sha256 and cost estimate; with no route it answers no-route (codeart2d is then the last resort). Also the capability check (forge_doctor), API key configuration, the spend ledger, resume and Codex image adoption. Use when a Forge skill sends a generation here, for the capability check, or when the user asks about keys, routes or spend. Not for planning, processing or QA of sprites, video frames or maps (generate2dsprite, video2dsprite, generate2dmap) or for code-drawn art (codeart2d).

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

Manage persistent coding sessions across Claude Code, Codex, Antigravity (agy), Grok Build, and OpenCode engines. Use when orchestrating multi-engine coding agents, starting/sending/stopping sessions, running multi-agent council collaborations, cross-session messaging, ultraplan deep planning, ultrareview parallel code review, autoloop autonomous workspace iteration, ultraapp building deployable web apps from a structured Q&A interview, switching models/tools at runtime, exposing the orchestrator's 78 tools as an MCP server to Hermes Agent / Claude Desktop / Cursor / Cline / Continue / Zed / Windsurf / Goose, or running as an Agent Client Protocol (ACP) agent that Zed / JetBrains / Neovim / Emacs / VS Code / dsh can drive directly. Triggers on "start a session", "send to session", "run council", "ultraplan", "ultrareview", "autoloop", "ultraapp", "Forge tab", "build a web app", "one-click app", "AppSpec", "autonomous iteration", "iterate until goal", "auto research", "switch model", "hand off a session", "session handoff", "switch engine", "continue on codex", "continue on claude", "move this session to another engine", "multi-agent coding", "coding session", "session inbox", "grok session", "grok build", "opencode", "mcp server", "clawo-mcp", "hermes mcp", "model context protocol", "ultracode", "dynamic workflow", "fanout", "fan-out", "best-of-N", "steer turn", "interrupt turn", "fork thread", "rollback turns", "acp", "agent client protocol", "clawo acp", "zed agent", "jetbrains agent", "external agent", "dsh subagent", "deepseek harness", "clawo runs", "run ledger", "session cost", "coding-agent token usage", "spend cap", "budget limit", "maxBudgetUsd", "durable workflow", "resume a run", "verify a coding run", "acceptance contract", "evidence bundle", "did the agent's tests actually pass", "protected tests", "agent edited the tests", "human gate", "repair loop", "clawo workflow", "clawo verify", "clawo solve", "clawo fanout", "fix and verify", "solve from the terminal".

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

Resume work on the FIFA Skeletal Tracking Light 2026 challenge using vailá modules (SAM 3, soccer pitch keypoints, calibration, per-frame DLT). Use whenever the user reopens the project after closing the terminal, asks "where did we stop on FIFA?", or wants the next concrete commands to run from `~/data/vaila` with `.venv` already created.

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

Resume Treadmill LC (load-cell GRF) work after the 2026-08-17 English translation. Use when the user reopens treadmill_lc, asks where that work stopped, wants Antigravity/Cursor to continue coding, or mentions COP mediolateral/anteroposterior labels, tare/weight calibration files, or tests/treadmill_lc.

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

Phase 9 of the SRS workflow. Saves all project context to _context/ files so future Claude sessions can resume without re-reading the full SRS.

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

Read and reuse AI coding session context across Claude Code, Codex, Antigravity/agent hooks, Cursor adapters, and compatible AI tools. Use this skill whenever the user asks to read, inspect, resume, compare, or continue another session by name or session ID, asks what happened in the previous session, or starts a new session that should inherit the nearest prior context. The paired provider adapter automatically loads the nearest previous project session at startup and resolves explicit session-read requests.

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

Phase 9 of the SRS workflow. Saves all project context to _context/ files so future sessions can resume without re-reading the full SRS.

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

Use when testing, evaluating, or building regression suites for Agentforce agents: conversation testing in Agent Builder, topic (now subagent) coverage and utterance testing, Testing API and AiEvaluationDefinition metadata, Agentforce DX CLI test runs (sf agent generate test-spec, sf agent test create/run/resume/results/list), evaluation metrics (containment rate, escalation rate, CSAT, topic activation accuracy), and post-deploy analytics via Enhanced Event Logs. Triggers: 'how do I test my Agentforce agent', 'agent routes to wrong subagent', 'write utterance tests', 'regression test after topic change', 'measure agent quality', 'agent containment rate', 'run agent tests from the CLI'. NOT for agent creation, topic design, or action contract design — use agentforce/agentforce-agent-creation, agentforce/agent-topic-design, or agentforce/agent-actions respectively.

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

Flow Orchestration admin: stage configuration, step assignment, background steps, interactive steps, evaluation flows, work items, pause/resume. NOT for approval routing a standard approval process would handle — use admin/approval-processes.

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