「state」の検索結果

Where a dispatched step puts its output, and how it signals state upstream.

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

Compare explicit design/specification contracts with the implementation in a defined change scope. Use to verify signatures, types, schemas, invariants, and other stated contracts without expanding into general code quality review.

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

Executes SAM Stage 5 — opens an attempt on a single ARTIFACT:TASK, dispatches it to a fresh stateless agent session, runs quality gates, and records an ARTIFACT:EXECUTION with implementation results and verification output on the task. Use when Stage 4 Task Decomposition is complete and tasks are ready for execution, when re-executing a task after Stage 6 returns NEEDS_WORK, or when dispatching a task to a language-appropriate specialist agent via the development harness pipeline.

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

Fetch and report current API syntax, changelog entries, and breaking changes for a specific library or protocol version. One research angle within a parallel technical-research set — runs independently and returns a structured cited report. Invoke when a specific library name and version are the target.

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

Use when the plan_ref returned by add-new-feature is provided. Executes the SAM implementation loop — opens an attempt per ready task, dispatches each to a specialist agent in parallel, settles and judges what comes back, manages bookend tasks (T0 baseline capture and TN verification), and tracks concerns and contract violations per task. Drives task state through the work ledger via the SAM CLI.

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

Analyze the causal system-wide impact of a proposed change across behavior, interfaces, state/data, runtime dependencies, tests, documentation, controls, people/processes, and model/prompt/context behavior. Use before planning when lexical reference search is insufficient to establish blast radius and verification obligations.

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

Grooms a GitHub milestone for parallel execution — batch-grooms ungroomed items, assesses scope gaps, analyzes cross-item dependencies via Impact Radius overlap, builds conflict groups, assigns items to execution waves, and persists the dispatch plan via dispatch_create_plan MCP tool. Calls dispatch_wave_start per wave to register state. Use when preparing a milestone for /work-milestone execution. Pass the milestone number as the first argument. Requires milestone items assigned via /group-items-to-milestone.

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

Use when the PLAN artifact from SAM Stage 2 needs contextualization against actual codebase state — grounds the design plan in reality by performing scope analysis (NEW/MODIFY/COMPLETE classification), conflict detection between plan assumptions and codebase patterns, and resource mapping to concrete file paths and integration points. Produces an updated ARTIFACT:PLAN registered via MCP with a Contextualization section appended.

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

Execute structured acceptance checks and record their observed results for later comparison. Use to capture a pre-change baseline or a post-change verification state without treating expected nonzero baseline results as execution failure.

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

Manages feature implementation task state via SAM MCP tools. Use when querying task status, listing ready tasks, dispatching tasks for execution, updating task timestamps, or coordinating multi-task feature rollout. Activated by the /dh:execution orchestrator to track progress — also activates directly when managing tasks.

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

Build, publish, and verify a Deepline Play as a durable state machine over Customer DB tables, including a small paid pilot. Invoke this skill explicitly when the user asks to build an engine.

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

Start-of-session situational report for a research or code repository. Reads the handoff, log, or status files the project actually keeps, checks live git state, and reports the objective, verified baseline, open tasks, blockers, and next actions, flagging where the documents and the repository disagree. Use when resuming work after time away or before changing anything. Its end-of-session twin is finished.

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

Turns raw captures (dictated braindumps in a deliverable's inbox/, or recent macwhspr dictation-log entries) into proposed planning-wiki changes, shown as one unified diff. Classifies each statement as a decision, evidence claim, question, task, or dropped item, traces it to its capture paragraph, tags unconfirmed names, numbers, and citations UNRESOLVED, and writes decisions only with the author's assent. Edits only the planning wiki, never source files. Use when asked to intake, absorb notes, or process the inbox, or after dictating notes from a talk, meeting, or reading session.

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

End-of-session closure for a research or code repository. Records what changed into the project's own handoff and log files, separating verified work from work merely attempted, and reports what is left uncommitted. Use when wrapping up a session so the next one can resume without re-deriving state. Its start-of-session twin is sitrep.

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

Use when an exact ChatGPT/Codex Plugin artifact has passed local package, brand, and listing gates and you need reviewer-ready submission evidence without confusing preparation, submission, approval, and publication states.

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

Designs multi-country survey experiments, covering case selection with a stated comparative logic, instrument localization and TRAPD translation, stimulus calibration, per-country power, and pooled versus per-country analysis with measurement-equivalence checks. Use when the user fields the same experiment in several countries, asks which countries to include, how to adapt an instrument without breaking comparability, whether to pool, or how large each country sample must be. Question wording goes to survey-design, reporting to methods-reporting, the study plan to pre-registration-writing.

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

Start-of-session report on where a repository stands. Reads the project's own handoff and log files, checks live git state, and reports objective, verified baseline, open tasks, blockers, and next actions. Use when resuming work. Twin of finished.

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

Scaffold or audit a social-science replication package, and audit the manuscript and archived research objects against FAIR. Use when setting up or repairing a package, checking one before submission, or drafting data, code, and materials availability statements. Adapted from Yusaku Horiuchi's replication-package-guide.

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

Turns dictated captures in a deliverable's inbox/ into a proposed planning-wiki diff, classifying and tracing each statement; decisions need the author's assent. Use to intake notes or process the inbox.

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

Use this skill when controlling the AltirraSDL Atari emulator programmatically — driving the simulator from a script, capturing screenshots from a running Atari, injecting joystick/keyboard input, frame-stepping for deterministic testing, reading or writing CPU/memory/chip state, setting breakpoints or watchpoints, profiling 6502 code, loading symbols, or building automated tests against an Atari binary. Triggers on phrases like "AltirraBridge", "AltirraSDL --bridge", "AltirraBridgeServer", "Altirra Python SDK", "headless Atari emulator", "screenshot the Atari", "automate AltirraSDL", "drive the emulator from Python", "Atari debugger over a socket", "altirra_bridge package", as well as on tasks involving the bridge protocol, the Python `altirra_bridge` package, or the C `altirra_bridge.h` SDK.

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

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.

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

This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.

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

Brand strategy, identity, positioning, and voice development. Use when developing brand guidelines, creating positioning statements, defining brand voice, or building brand architecture.

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

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

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