2,682 件 ・ 関連度順
概要と使いどころ
Recommend architecture patterns (monolith, microservices, serverless, modular monolith) based on scale, team size, and constraints. Use when cto-architect needs to select the right architectural approach for a new system or migration.
日本語の概要は準備中です。原文の説明を表示しています。
Team-theory primitives for cooperative agents: what each subagent sees, when to communicate, aggregation, Shapley credit, coalition topology. Use when organizing subagents.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses stalled teams or agent hierarchies with Beer's VSM and Ashby's Law. Use when orchestrators overload, escalations pile up, or team boundaries need redesign.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, and qa-tester to design, implement, and validate a combat feature end-to-end.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the UI team through the full UX pipeline: from UX spec authoring through visual design, implementation, review, and polish. Integrates with /ux-design, /ux-review, and studio UX templates.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.
日本語の概要は準備中です。原文の説明を表示しています。
Recommends team composition based on outcomes and mode. Invoked by launch commands during team setup.
日本語の概要は準備中です。原文の説明を表示しています。
Writing mode operational spec for the team lead. Returns lead identity, facilitator identity, ownership boundaries, editorial baseline, suggest-members guidance, and phase arc for writing-mode teams.
日本語の概要は準備中です。原文の説明を表示しています。
🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"
Act as the team's Scrum Master of record, or copilot to a human one: plan sprints, run daily pulses, close sprints, prepare and follow up retrospectives, track and escalate impediments, and detect process anti-patterns across sprint history. Use whenever the user asks for Scrum or agile process help, in any language — "plan the sprint", "chuẩn bị retro", "how is the sprint going", "our velocity dropped", "track this blocker", "the same problem keeps coming back" — even without the word "Scrum", and whenever `_project/scrum-master/` exists and the question touches sprints, ceremonies, impediments, or team process health. Not for delivery dates and budget (project-manager) or deciding what to build (product-manager).
日本語の概要は準備中です。原文の説明を表示しています。
Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.
日本語の概要は準備中です。原文の説明を表示しています。
Design and run OKR program — company objectives, team key results, cascade design, and quarterly review cadence. Use when asked to "design our OKRs", "are our OKRs good", "cascade goals to teams", or "run a quarterly OKR review".
日本語の概要は準備中です。原文の説明を表示しています。
Document and strengthen company culture - values articulation, team norms, communication protocols, and culture health diagnostics. Use when asked to "define our values", "document how we work", "diagnose culture health", or "write team norms".
日本語の概要は準備中です。原文の説明を表示しています。
Design or review org structure - spans of control, reporting lines, role clarity, headcount plan, and team topology. Use when asked to "design our org", "should we restructure", "what is the right team structure", or "plan headcount for next year".
日本語の概要は準備中です。原文の説明を表示しています。
Outlook の予定表・送受信メール・Teams チャットから営業活動を抽出し、Dataverse CRM の営業活動と商談の「次のアクション」へ差分だけ登録する日報・週報スキル。 Use when ユーザーが「今日の営業報告をして」「日報を CRM に登録して」「今週の商談活動を CRM に反映して」「会議の内容を CRM に記録して」と依頼したとき。 Dataverse MCP コネクタ（describe / read_query / search_data / create_record / update_record）を使用する。
目的特化型の Copilot Cowork プラグイン（M365 アプリパッケージ）を開発する。Agent Skills（SKILL.md）と Dataverse MCP コネクタをセットにし、Entra ID の OAuth 2.0 認可コードフロー認証を構成して Teams 開発者ポータルで registrationId を取得、M365 管理センターのエージェント画面からアップロード・公開して Cowork から Dataverse を利用可能にする。
メール、Teams チャット、予定表から現場の進捗・課題・決定事項を抽出し、現場コックピットへの反映案を作る。 Use when ユーザーが「今週の現場情報を取り込んで」「メールとチャットを現場に反映して」と依頼したとき。