941 件 ・ 関連度順
概要と使いどころ
Cut a kolu release — tag master, promote the Unreleased changelog entry, publish a GitHub release. ONLY invoke when the user explicitly types `/release` or `$release`; never auto-select from a natural-language request.
日本語の概要は準備中です。原文の説明を表示しています。
Runs Fable 5 and OpenAI Codex as co-founders on the Rocket Fuel operating system. Fable is the Visionary (vision, plan, standards, final review); Codex is the Integrator (filters the plan, executes the build, reports). Context-routed, one entry point, four functions: KICKOFF a new project, CLARITY BREAK to refactor an existing one, SAME PAGE MEETING to pressure-test a plan, BUILD A ROCK to hand Codex a scoped task. Use when the user says /rocket-fuel, wants to start or refactor a project with Codex, wants a plan reviewed by a second model, or wants to delegate a build to Codex.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct rigorous, citation-backed desk market research: quick go/no-go market scans, market sizing (TAM/SAM/SOM), competitor analysis, customer demand signals, and trend/macro (PESTEL) analysis. Use this skill whenever the user wants to research, size, validate, or enter a market — "is there a market for…", "how big is the market for…", "who are the competitors of…", "should I build/launch/sell…", "validate this business idea", "market research for…", "market entry" — in any language and for any country's market (e.g. "nghiên cứu thị trường", "étude de marché", "市場調査", "análisis de mercado"), even when the user never says the words "market research". Also use it when another skill or workflow (strategy-board, design-thinking, a product brief) needs external market facts delivered into its fact base or research folder.
日本語の概要は準備中です。原文の説明を表示しています。
A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.
日本語の概要は準備中です。原文の説明を表示しています。
The alphabetical-sort invariants the hyperlane-registry CI / CodeRabbit enforces on warp route YAML (deploy.yaml and config.yaml) — top-level chain entries sorted by chain name, and keys within each entry in strict alphabetical order — plus the canonical per-file key orderings and a verification pass. Referenced by any warp deploy/update skill that writes or edits a registry YAML file.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain the durable, per-ticket run log that warp deploy/update skills append to at every milestone — a Linear-document-by-title primary with single-writer discipline and a local-file fallback, a machine-parseable per-chain row plus prose entry shape, and a surface-the-URL-as-proof hard gate. Referenced by any warp deploy/update skill that must leave a retrospective trail across worker restarts.
日本語の概要は準備中です。原文の説明を表示しています。
Design or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".
日本語の概要は準備中です。原文の説明を表示しています。
Insert or read behavior log rows in the local database (behavior_logs). Use when recording a good/bad behavior entry, attaching a Pavlok API response JSON, adding a coach comment, or fetching recent logs via scripts/behavior_log.py.
日本語の概要は準備中です。原文の説明を表示しています。
Helper text, placeholders, validation and submit behaviour. Use when designing or reviewing a form, input field or data entry UI.
日本語の概要は準備中です。原文の説明を表示しています。
Provides quick-start guidance and a unified entry point for Vector features, SDK usage, and integrations. Use when users ask how to work with Vector, its TS SDK, features, or supported frameworks.
日本語の概要は準備中です。原文の説明を表示しています。
Static human-browsable catalog of the Zephyr RTOS skill set. Skill selection is handled by the zephyr-agent-skills entry point and by zephyr-cli skills suggest; this index is a reference listing only, not a task skill.
日本語の概要は準備中です。原文の説明を表示しています。
Configures pyproject.toml and Python packaging using PEP 517/518/621/660/723 standards. Use when creating or updating pyproject.toml, selecting a build backend (hatchling/setuptools/flit), configuring ruff, ty, mypy, pytest, or coverage tool sections, setting up dependency constraints or optional extras, defining CLI entry points, configuring pre-commit hooks, establishing src-layout directory structure, or preparing a package for PyPI publishing.
日本語の概要は準備中です。原文の説明を表示しています。
Entry point for refreshing the DH workflow graph. Use when skills, agents, Mermaid flowcharts, MCP tools, or artifact flows change and docs/dh-workflow-graph.json must remain current.
日本語の概要は準備中です。原文の説明を表示しています。
Generates one worker task prompt conforming to the CLEAR + selective CoVe task design standard and swarm-task-planner structure. Use when creating or rewriting a single task entry or task block inside a plan — providing a title and brief description as input.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews browser-rendered HTML, CSS, JSX, TSX, JavaScript, and TypeScript for accessibility, XSS, forms, focus, rendering performance, styles, and lifecycle cleanup. Loaded by dh:code-reviewer when source or framework entrypoints establish frontend execution; composes with TypeScript checks.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews Node.js runtime behavior in JavaScript or TypeScript, including server entrypoints, route handlers, middleware, streams, processes, dependencies, and environment configuration. Loads alongside language and CLI checks when applicable; investigates blocking I/O, backpressure, injection, lifecycle leaks, and misleading failure signals.
日本語の概要は準備中です。原文の説明を表示しています。
Routes to the correct dh skill entry point by intent. Use when unsure which development-harness skill to invoke, starting a development workflow, or invoking /dh directly. Covers capture, groom, plan, execute, single task, quality gates, and milestone routing.
日本語の概要は準備中です。原文の説明を表示しています。
Produces a structured, end-to-end linear walkthrough of an unfamiliar codebase by orchestrating parallel subagents across four phases — discovery, tracing, validation, and synthesis. Use when onboarding to a new repository, understanding execution paths from entry points, generating navigable codebase documentation, or needing fact-checked coverage of architecture, deployment, testing, and operations.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate research entry lifecycle in ./research/ — create, batch-import, refresh stale entries, and validate structure. Use when asked to add a tool, research a URL, document a library, refresh research, validate entries, or given any tool or library URL. Supports --batch (parallel multi-URL), --rerun (refresh one or all entries), and --validate (structural check with auto-fix of error-severity issues).
日本語の概要は準備中です。原文の説明を表示しています。
Transforms validated /linear-walkthrough artifacts into one presentation-ready deck outline per major codebase component. Use when the user asks to create a presentation, prepare a walkthrough deck, build an onboarding deck, produce an architecture review deck, or summarize a codebase for a technical audience. Requires walkthrough directory output -- reads unified walkthrough, per-section files, validation reports, coverage maps, entry points, and open questions -- then orchestrates four parallel agent phases to produce slide outlines with speaker notes, evidence references, and suggested visuals.
日本語の概要は準備中です。原文の説明を表示しています。
Manages the research/ knowledge base of verified tool and library research entries via knowledge-explorer.py. Commands — list (browse by category or SDLC layer), fetch-github (draft entry from GitHub repo), add (validate and route to category dir), update-append (append dated revision), generate-descriptions (repair missing or low-quality descriptions), migrate (convert inline-header entries to frontmatter). Use when browsing KB topics, adding or updating research entries, fetching GitHub repo metadata, generating descriptions in parallel via Haiku subagents, or migrating old-format entries to skill-spec frontmatter.
日本語の概要は準備中です。原文の説明を表示しています。
Validate and iterate on the SDLC Layer Separation Architecture implementation across the check categories defined in its Evaluation Checklist — cross-references, doc completeness, knowledge-explorer layer filters, research entry metadata, integration points, and plan consistency. Produces a structured findings report and optionally applies safe fixes. Use when validating a first-pass implementation, before claiming layer work complete, auditing layer docs or schema, or running --dry-run to preview findings without changes.
日本語の概要は準備中です。原文の説明を表示しています。
Design, create, update, and verify Vapi Squads and documented handoff tools through the public API. Use for choosing a single assistant versus a multi-assistant Squad, persistent or transient members, entry-member ordering, specialization boundaries, context engineering, variable extraction, model-specific handoff patterns, assistant-version pins, and safe Squad updates.
日本語の概要は準備中です。原文の説明を表示しています。
Maps your company's GTM motion (PLG, SLG, or Hybrid) to concrete funnel stages with inputs, outputs, and qualification criteria per stage. Detects motion type from website + Exa research, then produces pre-close + post-close stage definitions, the FETE mapping (Fit / Engagement / Tier / Eligibility), and closed-lost re-entry paths. Triggers - "funnel strategy", "funnel stages", "pipeline stages", "sales process", "lead qualification", "GTM motion mapping", or any work defining how leads flow through the business. Upstream - recommended company-context, icp-research. Downstream - feeds lifecycle-marketing, outreach-emails, content-strategy. NOT for lead scoring logic (use /lead-scoring) or lifecycle email campaigns (use /lifecycle-marketing).
日本語の概要は準備中です。原文の説明を表示しています。