3,134 件 ・ 関連度順
概要と使いどころ
Load when asked to create, update, re-baseline, or continue a repository-grounded implementation/technical/refactor plan and its `dev/active/<task>` plan/context/tasks files; not for a product PRD, informal advice, or reviewing an already-written plan.
日本語の概要は準備中です。原文の説明を表示しています。
ISTQB/JSTQB のテスト実装（test implementation）活動を支援するスキル。test-design が導出したテストケースを、実行できる形に具体化する。自動テストなら実行手順（テストコード・テストデータ・テストダブル）をコンパイル/構文レベルの動作確認まで、手動テストなら手順書・テストデータ・環境準備手順を作る。「テストケースを実装して」「テストコードに落として」「テスト手順書を作って」「テストデータ・モックを用意して」と依頼されたときに使う。テスト対象の検証としての実行（結果の解釈・欠陥候補整理）は test-execute の担当でここではしない。単発のテスト作成依頼（単にユニットテストを書きたいだけ）は対象外。/test-implement <テスト対象名> で明示的に呼び出されたときのみ使用する。
Execute a previously created implementation plan — implement, test, document, and close out. Use when a plan file exists and is ready for implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Applies standard AI review policy guidelines for midstream (implementation) phase reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Interactive Domain-Driven Design modeling sessions based on DDD Distilled (Vaughn Vernon) and Domain Modeling Made Functional (Scott Wlaschin). Guides users through strategic and tactical design via 13 phases: discover, storming, contexts, mapping, aggregates, events, validate, glossary, workflows, types, simulate, publish, sync. Phase 13 (sync) reconciles divergences found by --analyze between the domain model and the implementation — judging whether the model or the code is authoritative, then planning and implementing the fix and re-aligning the model. Phases 9-11 take the conceptual model from phases 1-8 and produce workflow pipeline designs, compilable type definitions (TypeScript, Kotlin, Scala, Rust, C#, F#), workflow verification via type-level tests, and automatic UI field enumeration from the domain model. Phase 12 (publish) renders all docs/domain artifacts into one self-contained, cross-linked HTML site (separate files joined by a shared nav). Each phase is an interactive dialogue where AI acts as facilitator and domain expert challenger. Use when: "DDD", "ドメイン設計", "ドメインモデリング", "Event Storming", "Bounded Context", "集約設計", "ユビキタス言語", "コンテキストマップ", "ワークフロー設計", "パイプライン設計", "ステップ分割", "中間型", "型駆動フロー", "型駆動設計", "Domain Modeling Made Functional", "Railway Oriented Programming", "入力画面項目", "フォーム項目洗い出し", "UI 項目抽出", "HTMLにまとめる", "ドキュメントサイト化", "成果物を1つのHTMLに", "publish", "モデルと実装の差異", "差異解消", "実装との乖離", "モデルとコードを一致", "差異の実装計画", "sync", "複数フェーズを逐次実行", "フェーズをまとめて実行", "/ddd run", "サブコマンド一覧", "/ddd list", "/ddd", "ドメイン分析したい", "モデリングしたい", or any domain design / type modeling activity.
Orchestrate concurrent analysis or implementation across independent domains. Use when a task can be decomposed into independent workstreams (e.g., via simultaneous tool calls or background processes) — spec writing, code review, security audit, feature implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Turn an ambiguous factory issue into human-approved product, behavior, design, and implementation slices. Use interactively before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Expert en implémentation CRM (HubSpot, Salesforce, customization, data migration, DZ)
日本語の概要は準備中です。原文の説明を表示しています。
RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimization.
日本語の概要は準備中です。原文の説明を表示しています。
RAG (Retrieval-Augmented Generation) implementation workflow covering embedding selection, vector database setup, chunking strategies, and retrieval optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Translate Figma designs into production-ready SwiftUI code with 1:1 visual fidelity using the Figma MCP workflow. Trigger when the user provides Figma URLs or node IDs and wants iOS/SwiftUI implementation, asks to implement a design or component from Figma for an iOS app, or references Figma selections in the context of an Xcode/SwiftUI project. Also trigger when user asks to inspect Figma designs for iOS planning, fetch design tokens for SwiftUI, or convert Figma assets for Xcode. Requires a working Figma MCP server connection. Do NOT trigger for web/React implementations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: remote team, delegate, delegated lane, delegated implementation, delegated QA, or non-sensitive ticket routing to the remote team's implementation lane.
日本語の概要は準備中です。原文の説明を表示しています。
Solution architect that creates implementation blueprints before building. Maps 2-3 approaches ranked by simplicity, creates phased build plans with rollback points, and checks dependencies. Use when you need to design a solution, create a blueprint, plan before building, or take a task from the audit and need an implementation plan. Part of the architect-system loop. Reads from system/audit-report.md. Outputs to system/blueprints/.
日本語の概要は準備中です。原文の説明を表示しています。
Tests OAuth 2.0 and OpenID Connect implementations for security flaws including authorization code interception, redirect URI manipulation, CSRF in OAuth flows, token leakage, scope escalation, and PKCE bypass. The tester evaluates the authorization server, client application, and token handling for common misconfigurations that enable account takeover or unauthorized access. Activates for requests involving OAuth security testing, OIDC vulnerability assessment, OAuth2 redirect bypass, or aut...
日本語の概要は準備中です。原文の説明を表示しています。
Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.
日本語の概要は準備中です。原文の説明を表示しています。
High-performance reinforcement learning framework optimized for speed and scale. Use when you need fast parallel training, vectorized environments, multi-agent systems, or integration with game environments (Atari, Procgen, NetHack). Achieves 2-10x speedups over standard implementations. For quick prototyping or standard algorithm implementations with extensive documentation, use stable-baselines3 instead.
日本語の概要は準備中です。原文の説明を表示しています。
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
日本語の概要は準備中です。原文の説明を表示しています。
Implement A/B tests with code and analytics. TRIGGERS - Use when user needs help with ab-test-implementation related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Implement 5S workplace organization. TRIGGERS - Use when user needs help with 5s-implementation related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Implement accessibility. TRIGGERS - Use when user needs help with a11y-implementation-guide related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Write the merged Pencil design reference back into a UI implementation Issue's description. Takes the Issue number as argument, resolves the merged design PR on the `cc-ui-design-<Issue number>` branch, collects the `.pen` and snapshot paths it added, and appends (or replaces) the `## UIデザイン` section at the end of the Issue body using a lost-update-safe edit.
Create an implementation plan and a GitHub Issue based on the task description provided as an argument. Use this when the user supplies a natural-language task description (not an issue number) and wants a new implementation-ready Issue. If the input is an existing issue number, use create-issue-from-issue-number (re-analyze) or update-issue (reflect comments) instead.
日本語の概要は準備中です。原文の説明を表示しています。
Keep GPT-5.6 and other coding-agent work proportional to the request by locking scope, choosing the smallest sufficient implementation, matching verification to risk, and stopping when success is proven. Use for implementations, bug fixes, refactors, reviews, or maintenance where scope creep, speculative abstractions, unrelated cleanup, repeated test runs, unnecessary dependencies, or polishing beyond the request are risks.
日本語の概要は準備中です。原文の説明を表示しています。
実装前に参照する設計原則。理解容易性 = 読み手の思考量の少なさを基準に、AI が作りがちな失敗4パターン（引数・依存5個以上、コマンド層肥大・ドメイン貧血症、ポリモーフィズム機会の見逃し、トリッキーな実装）と、実装後セルフチェックの7観点（名称・役割・参照・状態・面積・階層・秩序）を言語化。Use when starting any implementation task, when user says '設計原則', 'design principles', or before writing new entities/commands/repositories.