1,692 件 ・ 関連度順
概要と使いどころ
Start or complete a specific refactoring task from a task file. Use when a sub-agent needs to pick up a refactoring task, update its status, implement acceptance criteria, and run verification steps.
日本語の概要は準備中です。原文の説明を表示しています。
Define and develop plugin mission statements — purpose, values, anti-patterns, and trade-offs. Use when creating a new plugin, auditing an existing plugin's alignment, or providing a reference for the alignment check loop to evaluate decisions against. Produces mission.json with [draft] status and writes an interview file for the human to refine it.
日本語の概要は準備中です。原文の説明を表示しています。
Spawn and manage persistent interactive Claude Code CLI sessions with bidirectional communication via tmux. Provides spawn, send, read, status, list, and kill subcommands for orchestrating parallel peer sessions. Uses built-in --worktree and --tmux flags. Sessions stay alive for multi-turn steering. Triggers on "spawn claude session", "launch separate claude", "peer session", "inter-session communication", "shadow clone", "kage bunshin".
日本語の概要は準備中です。原文の説明を表示しています。
Close a completed GitHub milestone. Args: {milestone-number}. Audits open and closed issues, offers to carry forward open items to a new or existing milestone, closes the GitHub milestone, updates Project V2 Status to Done for closed issues, and generates a completion summary. Use when a sprint or release is finished and needs to be officially closed.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Assign backlog items to a GitHub milestone by bridging per-item files to GitHub Issues. Use when populating a sprint or release milestone, after create-milestone, or when a milestone number is specified with optional P0/P1/P2 or title filter. Creates missing GitHub Issues for selected P0/P1 items, assigns all selected items to the milestone, and updates Project V2 Status to Backlog.
日本語の概要は準備中です。原文の説明を表示しています。
Close a completed GitHub milestone and generate a completion summary. Use when a sprint or release is finished and needs to be officially closed. Audits open and closed issues, offers to carry forward open items to a new or existing milestone, closes the milestone, updates Project V2 Status to Done for closed issues, and produces a completion report.
日本語の概要は準備中です。原文の説明を表示しています。
ACCESS-GATED beta. Deepline Monitors are provider event feeds (job posts, email replies, funding, intent) that stream into your warehouse and trigger plays. Only use if you have monitor access: run `deepline monitors status` first; if it reports no access, do NOT use this recipe — tell the user to contact the Deepline team.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
日本語の概要は準備中です。原文の説明を表示しています。
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
日本語の概要は準備中です。原文の説明を表示しています。
Show the active SkillNote collection and the skills synced into this project for Codex. Use when the user says "skillnote", "what skills do I have", "show my collection", or wants a SkillNote status/dashboard.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a product messaging library from your positioning, your website and customer evidence: a description, the status quo and alternatives, pain points with their knock-on consequences, capabilities, functional, emotional and social benefits, branded features, the cost of doing nothing, common objections with responses, and core messaging blocks (tagline, elevator pitch, value props, proof, per-audience lines). Every claim sourced. Triggers: "product messaging", "messaging library", "messaging framework", "value props", "capabilities and benefits", "what are our differentiators in words". Run after /positioning. Not for choosing the position itself (use /positioning).
日本語の概要は準備中です。原文の説明を表示しています。
Разбор extraction-reports со status pending-review — решение R15 (accept/reject/defer) ЖИВЫМ ПИЛОТОМ, запись в Pack, обновление статуса, коммит. Вызывать при Close при наличии N>0 pending-review отчётов.
日本語の概要は準備中です。原文の説明を表示しています。
Управление consent в learning.tracking_consent — opt-in / opt-out / status / revoke. Обязательное условие для работы stage_evaluator worker (WP-253 Блок 2). GDPR-совместимо.
日本語の概要は準備中です。原文の説明を表示しています。
Develop positioning strategy with anchor, differentiators, status-quo alternatives, and a positioning statement. Reads from marketing/icp/ICP.md + marketing/competitors/aggregate.md. Writes to marketing/positioning/positioning.md as the canonical positioning every downstream skill reads. Triggers - "positioning", "category definition", "how do we position", "positioning strategy", "anchor + differentiators"
日本語の概要は準備中です。原文の説明を表示しています。
Build a 10-component messaging library from your positioning + ICP + competitor aggregate. Produces positioning statement, value propositions, key differentiators, taglines, CTA variants, proof points, messaging hierarchy, status-quo alternatives. Writes to marketing/messaging/messaging.md as the canonical messaging library every downstream content / paid / outbound / lifecycle skill reads. Triggers - "product messaging", "messaging library", "value props", "messaging framework", "build messaging", "messaging components"
日本語の概要は準備中です。原文の説明を表示しています。
Run deep research on a single competitor. Produces a dossier with executive summary, position + messaging, status-quo alternatives, key differentiators, pricing position, where-they-win / where-they-lose, threat assessment, and what to watch. Writes to marketing/competitors/MMYY-{competitor-slug}.md. Triggers - "competitor research", "competitive analysis", "research competitor X", "battlecard prep", "analyze [competitor name]
日本語の概要は準備中です。原文の説明を表示しています。
Interactive code review for agent iterations. Captures comments, tracks resolution status, and integrates with git diffs.
日本語の概要は準備中です。原文の説明を表示しています。
Run and manage ad-hoc AI prompts in sgai workspaces without starting a full agentic session. Use when you need to run a one-off AI prompt against a workspace, check the status of a running ad-hoc prompt, or stop a running ad-hoc prompt.
日本語の概要は準備中です。原文の説明を表示しています。
Transition an Incan RFC from one status to the next. Use when the user asks to promote, advance, or finalize an RFC, or says /bump-rfc. Handles Draft → Planned, Planned → In Progress, and In Progress → Implemented transitions.
日本語の概要は準備中です。原文の説明を表示しています。
Safely close out completed Incan work after a PR is merged by verifying merge status, syncing the base branch, removing task-owned local worktrees/assets, deleting merged local/remote branches, pruning refs, and reporting dirty or ambiguous leftovers. Use when the user says /closeout, asks to clean up after a merged PR, or wants local RFC/issue branch/worktree cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Report which local git worktrees under tmp/ are safe to close, need a human look, or are explicitly protected. Use when the user says /fleet-audit, asks what worktrees can be cleaned up, or wants a status check across all Ralph-loop/spike worktrees before running closeout on any of them.
日本語の概要は準備中です。原文の説明を表示しています。
Run SQL against Snowflake — submit statements, poll async handles, fetch result partitions, cancel, and browse warehouses/databases/schemas/tables. Use this whenever the user wants to query Snowflake, ask "what tables are in this schema", check a warehouse's status, or mentions `snowflakecomputing.com`, `/api/v2/statements`, or a Snowflake account identifier (like `xy12345.us-east-1`). Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。