7,695 件 ・ 関連度順
概要と使いどころ
Design production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
日本語の概要は準備中です。原文の説明を表示しています。
n8n workflow automation knowledge base. Provides n8n node information, node functionality details, workflow patterns, and configuration examples. Covers triggers, data transformation, data input/output, AI integration, covering 10 nodes. Keywords: n8n, workflow, automation, node, trigger, webhook, http request, database, ai agent.
日本語の概要は準備中です。原文の説明を表示しています。
Expert Clay platform consultant for B2B data enrichment and workflow automation. Use when the user asks about Clay tables, waterfall enrichment, Clay credits, Clay AI columns, Claygent, enrichment workflows, Clay integrations, Clay exports, Clay table design, lead scoring in Clay, or building data pipelines in Clay. Also triggers on "Clay table", "enrichment waterfall", "Clay credits", "Claygent", "Clay AI column", "Clay export", "Clay providers", "enrich in Clay", "Clay column", "Clay formulas", "find emails", "email waterfall", "phone waterfall", "lead scoring", "Clay debugging", "Clay troubleshoot". Do NOT use for general CRM questions without Clay context, cold email copy (use cold-email-copy-playbook), or signal routing (use buying-window-signal-workflow).
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses failing GitHub Actions runs by reading logs, identifying the root cause, and suggesting fixes. Use this skill whenever a user shares a GHA run URL, pastes runner log output, mentions a failing workflow, asks why a CI job is broken, or says anything like "my GHA is failing", "workflow failed", "can you check my run", or "CI is broken". Also trigger when raw log text is detected in the conversation that appears to come from a GitHub Actions runner. Do NOT use for general GHA workflow authoring questions, YAML formatting help, or passing runs with no failure context.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Idea to PBI workflow for turning an idea — or a raw product vision/problem — into prioritized PBIs and stories (single-PBI deep mode, or multi-opportunity discovery mode).
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Write Integration Tests workflow for spec-first integration test authoring. Also covers converting existing test specs into integration test code and verifying integration test stability (repeat-run verification).
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Visual Diagram workflow for create visual excalidraw diagrams from codebase investigation or web research.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Review Current Changes workflow for review, fix, and re-review recursively until all issues resolved.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Integration Test Green workflow — drive an integration-test suite to fully green with a bounded convergence loop: verify the whole system (or the named target), adjudicate every failure with /debug-investigate + /integration-test-review before any edit, fix at the owning layer, /changes-review each round's fix diff, re-verify from scratch, then sync spec TCs, the integration-test reference doc, and feature docs.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Code Refactoring workflow for restructure and improve existing code without changing behavior.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Research & Synthesis workflow — research a topic via web sources, then synthesize per --output={synthesis|business-eval|marketing|course} (knowledge report, business evaluation, marketing strategy, or course material).
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Spec to PBI Backlog workflow to convert canonical tech-free Feature Specs into complete, prioritized, dependency-aware PBIs and stories.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Seed Test Data workflow for idempotent QC happy-path seeders.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Test Spec Update (Post-Change) workflow for update test specs and feature docs after code changes, bug fixes, or pr reviews.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Greenfield Project Init workflow for full waterfall project inception from idea through implementation with integration testing.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Big Feature workflow for large or ambiguous research-driven feature work.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the E2E testing workflow to generate, update, or maintain Playwright/E2E tests. Pick mode with --source={changes|recording|update-ui}.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Feature Implementation workflow for implement a well-defined feature with investigation, planning, implementation, and review. Also covers TDD/test-first development and spec-driven feature implementation with test specs written before code.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Business Feature Documentation workflow for 8-section tech-free feature docs.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Bug Fix workflow for systematic debugging with root cause investigation, fix, and verification.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating code-to-spec development — author/maintain the single canonical Feature Spec FROM existing code, keeping spec, implementation, and tests synchronized. For idea→spec (no code yet) use workflow-idea-to-spec.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when activating the Architecture Audit workflow to review the whole project's architecture, run an architecture health check, or check production readiness/scalability in one pass — read-only, produces one consolidated Architecture Health Report.
日本語の概要は準備中です。原文の説明を表示しています。
Generate reusable multi-step agent workflow blueprints. Use for trigger/action orchestration, deterministic workflow definitions, and automation handoff artifacts.
日本語の概要は準備中です。原文の説明を表示しています。