401 件 ・ 関連度順
概要と使いどころ
Guides continuous improvement and change management for SMEs adopting AI. Applies Marginal Gains philosophy, Kaizen principles, and structured sprint methodologies to organizational transformation. Use when user asks about change management, continuous improvement, AI adoption strategy, team resistance, transformation roadmaps, or improvement sprints.
日本語の概要は準備中です。原文の説明を表示しています。
Use when comparing this package to a peer / competitor — ours-vs-theirs verdict table, axis selection, adoption queue. Triggers on 'how do we compare to X', 'should we adopt their pattern'.
日本語の概要は準備中です。原文の説明を表示しています。
Maintains repo-local action contracts and harness repositories where product CLI and MCP adapters stay thin over core libraries. Use when adopting or improving steward.yaml actions, capability-level adoption evidence, cold-start proof loops, probes, benchmarks, CLI/MCP/core parity, adapter refactors, packages/core boundaries, or sibling harness layout; use repo-quality-system-lifecycle first for general app/library/tool stewardship baselines.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews a proposal, business case, deck or rollout plan in character as a Frontline Sceptic archetype, the experienced staff member who will live with the change, and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, adoption risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a frontline review", "give me the shop-floor view of this rollout", "pressure-test adoption of this plan" or "what will the team actually say about this". Do not use for employee consultation, monitoring or works council preparation, use works-council-reviewer instead; for people strategy or restructuring, use chro-reviewer; for product evidence, use cpo-reviewer. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews a proposal, business case, deck or product plan in character as a Chief Product Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, product and adoption risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CPO review", "pressure-test this product plan", "what would a CPO say about this", "challenge the user evidence" or "check the roadmap opportunity cost". Do not use for positioning, messaging or launch marketing, use cmo-reviewer instead; for internal staff adoption of a rollout, use frontline-skeptic-reviewer; for what a change asks of paying customers, use customer-advocate-reviewer. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Codeium — codeium (Windsurf) AI coding assistant management and analytics. Covers team seat management, usage tracking, language analytics, editor adoption metrics, security policy configuration, and enterprise deployment review. Use when managing Codeium/Windsurf licenses, reviewing team adoption, or analyzing AI-assisted coding productivity.
日本語の概要は準備中です。原文の説明を表示しています。
Expert en transformation digitale (strategy, change management, technology adoption, maturity assessment)
日本語の概要は準備中です。原文の説明を表示しています。
Expert en customer success avancé (onboarding, adoption, expansion, QBRs, NPS, health scores)
日本語の概要は準備中です。原文の説明を表示しています。
Resolve Swift concurrency compiler errors, adopt approachable concurrency (SE-0466), and write data-race-safe async code. Use when fixing Sendable conformance errors, actor isolation warnings, or strict concurrency diagnostics; when adopting default MainActor isolation, @concurrent, nonisolated(nonsending), or Task.immediate; when designing actor-based architectures, structured concurrency with TaskGroup, or background work offloading; or when migrating from @preconcurrency to full Swift 6 strict concurrency.
日本語の概要は準備中です。原文の説明を表示しています。
Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, macOS-specific APIs, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Use when: 'intake this repo/skill', 'evaluate external skill', 'should we adopt X', a candidate repo URL plus an adoption question, or any external skill/workflow/tool surfaces as a possible fit for Agistra. Structured front-door evaluation of external skills, workflows, and similar capability artifacts before any install, promotion, or adaptation decision. Ends in exactly one classification: Install candidate, Adapt concept, or Reject. Never install first — intake first.
日本語の概要は準備中です。原文の説明を表示しています。
Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, macOS-specific APIs, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
日本語の概要は準備中です。原文の説明を表示しています。
taskboard の MCP tool（health / board_* / task_* / work_* / doc_* / ask_* / review_request / feedback_list / comment_reply / schedule_* / session_* / orchestrator_* / settings_* / inbox_* / prs_* / usage_get）でタスク・作業項目・文書と、案件・定期起動・セッション・受信箱を扱う。自分のセッションに紐づくタスクの列を進める・起票する時、計画の承認後に作業項目を登録し着手・完了・待ちを更新する時、計画書・設計提案を人に読ませて採否やレビューを求める時、ボードの一覧・状態を確認する時、オーケストレーターとして全体の health を見回る時、案件・定期起動・セッションを作る・変える・止める・消す時、依頼に taskboard・タスクボード・kanban・作業項目の語がある時に使用。境界: taskboard の外で始まったセッションをタスクに移すのは taskboard-adopt、pane・tab・agent の操作は herdr、作業ログ・調査記録はメモリディレクトリ、ボードの画面操作はユーザーの領域、新しい定期起動の中身（仕組みの選択・手順書・プロンプト・状態ファイル）の設計は scheduling-jobs。
Cross-company language sweep via Quartr full-text search — date the adoption curve of a term/phrase across the global transcript+filing corpus, identify which companies (and which speaker roles) use it and when they started, and cross-reference against vault theses and graph adjacency to flag terms propagating through supply chains the book owns. Use when user says "sweep", "who is talking about X", "language scan", "adoption curve for X", or "is X inflecting".
日本語の概要は準備中です。原文の説明を表示しています。
Build and scale developer-led adoption through ecosystem programs. Use when deciding open vs curated ecosystems, building developer programs, scaling platform adoption, or designing student program pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Launch new products from idea to first customers. Use when launching products, finding early adopters, building launch week playbooks, diagnosing why adoption stalls, or learning that press coverage does not equal growth. Includes the three-layer diagnosis, the 2-week experiment cycle, and the launch that got 50K impressions and 12 signups.
日本語の概要は準備中です。原文の説明を表示しています。
Guides the practical path from 'we have no design system' or 'we have a mess' to a real, functional design system. Component inventory, design token extraction, headless UI adoption (Radix, React Aria, Headless UI), migration order of operations, and the assessment-to-rollout pipeline. Activate on 'design system from scratch', 'bootstrap design system', 'no design system', 'design system migration', 'headless UI adoption', 'component audit', 'design token extraction', 'design system strategy'. NOT for building specific components once a system exists (use design-system-creator), not for generating token files/configs (use design-system-generator).
日本語の概要は準備中です。原文の説明を表示しています。
本格的な開発に進む前に小さな試作品を動かし、アイデアの実現性や方式の違いを検証して、実行結果を根拠に採用・調整・見送りの判断をまとめるスキル。
Run the ECC engineering process retroactively against an existing project slice. Audit current state, reconstruct past decisions, produce a four-axis gap register (thinking, coding practice, missing features, technology selection), then execute fixes forward through the plan-TDD-review pipeline. Use when adopting ECC mid-project, taking over an inherited codebase, or asking what was missed and what would have been built differently from day one.
日本語の概要は準備中です。原文の説明を表示しています。
新しいスキルを作る前に、ローカル環境やマーケット、GitHub、ウェブから既存候補を探し、用途との一致度や安全性を確認して再利用・拡張・新規作成の判断を助けます。
Swift 6.2への移行や並行処理の設計で、MainActorによる状態の保護、重い処理の明示的なバックグラウンド実行、コンパイルエラーの解消を支援するスキル。
長期プロジェクトの既存文書を、規則・構造・現状・履歴の役割に整理します。エージェントの参照先と更新ルールを整え、文書のずれや削除したものの再作成を防ぐ運用を支援します。
市場規模の推計、競合比較、投資家や技術の調査を、出典付きでまとめるスキル。事実と推測を分け、反証やリスクも含めて事業判断につながる提案を整理します。
機械学習のない既存アプリに、推薦・分類・予測などを追加するための手順を整理します。課題とデータの確認から、最初のモデルの学習・評価・組み込みまでを支援します。