「team」の検索結果

天涯神贴大神智囊团 — 20位传奇大神组成的多Agent决策系统。 基于ClawTeam多Agent协作原理，实现「一个目标 → 20位大神并行分析 → 综合决策」的完整工作流。 核心机制： - 智能领导者Agent（协调者）接收目标，分配给20位专业大神 - 20位大神并行分析，各自输出专业视角 - 综合决策Agent整合所有视角，输出最终决策 使用方式： - 「启动天涯智囊团」+ 你的问题/目标 - 「召集大神」+ 你的问题/目标 - 「20位大神分析」+ 你的问题/目标 涵盖领域：权谋分析、经济预言、历史解读、文化解构、都市情感、技术分析、 黑帮江湖、盗墓探险、玄幻武侠、都市异能、悬疑推理、法医刑侦、历史穿越等。

日本語の概要は準備中です。原文の説明を表示しています。

Audio implementation team orchestration

日本語の概要は準備中です。原文の説明を表示しています。

Story and dialogue team coordination

日本語の概要は準備中です。原文の説明を表示しています。

Combat system team coordination

日本語の概要は準備中です。原文の説明を表示しています。

Level design team coordination

日本語の概要は準備中です。原文の説明を表示しています。

UI implementation team orchestration

日本語の概要は準備中です。原文の説明を表示しています。

Create agent company packages conforming to the Agent Companies specification (agentcompanies/v1). Use when a user wants to create a new agent company from scratch, build a company around an existing git repo or skills collection, or scaffold a team/department of agents. Triggers on: "create a company", "make me a company", "build a company from this repo", "set up an agent company", "create a team of agents", "hire some agents", or when given a repo URL and asked to turn it into a company. Do NOT use for importing an existing company package (use the CLI import command instead) or for modifying a company that is already running in Paperclip.

日本語の概要は準備中です。原文の説明を表示しています。

Multi-agent team orchestration CLI for spawning agents, managing tasks, and coordinating work through mailbox messaging and git worktree isolation

日本語の概要は準備中です。原文の説明を表示しています。

Data-driven sprint retrospectives from git history — velocity, cycle/lead time, contributor insights, and churn hotspots. Use to run a retrospective, analyze team velocity or throughput, or generate a retro report from commit history.

日本語の概要は準備中です。原文の説明を表示しています。

Adversarial verification for AI-generated legal content. Use when fact-checking legal documents, validating citations, detecting hallucinations, scoring document quality, or assessing distribution readiness.

日本語の概要は準備中です。原文の説明を表示しています。

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, or making architecture decisions.

日本語の概要は準備中です。原文の説明を表示しています。

The canonical way to run agent-relay - self-bootstrap the local broker and autonomously spawn, monitor, and coordinate a team of worker agents without human intervention. Covers infrastructure startup, agent spawning, lifecycle monitoring, message-based reading via the relay MCP, and team coordination.

日本語の概要は準備中です。原文の説明を表示しています。

Assign marketing tasks to team members by role fit and workload. "who should write the Q2 email sequence"

日本語の概要は準備中です。原文の説明を表示しています。

Send a team notification to Slack or Intercom by urgency tier, approval-gated. "ping the team that the campaign launched"

日本語の概要は準備中です。原文の説明を表示しています。

Set up DMP for team use in Cowork: sandbox check, Drive folders, saved routing. "set up DMP for my team in Cowork"

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to test their LLM/agent application for safety and security vulnerabilities — jailbreaks, prompt injection, PII extraction, harmful content generation, or evaluator gaming. Also use when the user mentions security testing, adversarial testing, red teaming, safety evaluation, ASR (Attack Success Rate), or "is my app safe to deploy." Outputs ASR paired with over-refusal rate and an audit document.

日本語の概要は準備中です。原文の説明を表示しています。

Performance scorecard design, post-matter feedback collection, QBR preparation, and firm comparison for in-house legal ops teams evaluating outside counsel. Design a scorecard framework calibrated to your team's maturity level. Produce post-matter feedback forms for supervising attorneys to complete at matter close. Prepare a QBR pack with agenda, data summary, and talking points for structured business reviews. Produce a side-by-side firm comparison for panel decision-making. Trigger on: 'design a performance scorecard', 'how do we evaluate our firms', 'build us a scorecard', 'post-matter feedback form', 'feedback at matter close', 'collect feedback on the firm', 'QBR', 'quarterly business review', 'prep for the firm review', 'what should I raise with the partner', 'compare the firms', 'which firm is performing better', 'rank our panel', 'firm performance data', 'scorecard framework', 'evaluate outside counsel', 'annual firm review', 'how are our firms performing'.

日本語の概要は準備中です。原文の説明を表示しています。

Collaboration platform configuration methodology for legal matter sites. Site architecture, workflow identification, dashboard design, data quality governance, and user adoption for SharePoint, Teams, and equivalent platforms. M365 is the reference implementation — outputs are platform-agnostic enough to brief IT or build simple automations without becoming a Power Automate manual. Use when setting up a matter site, identifying workflows to automate, designing reporting dashboards, managing platform data quality, or driving user adoption. Trigger on: 'set up the matter site', 'configure SharePoint', 'build a dashboard', 'what should we automate', 'brief IT on this workflow', 'nobody is using the platform', 'data quality is poor', 'set up Teams channel', 'matter site structure', 'alerts and notifications', 'user training', 'platform governance', 'status dashboard', 'what workflows can we automate', 'matter site template'.

日本語の概要は準備中です。原文の説明を表示しています。

Expert blueprint for desktop platforms (Windows/Linux/macOS) covering keyboard/mouse controls, settings menus, window management (fullscreen, resolution), keybind remapping, and Steam integration. Use when targeting PC platforms or implementing desktop-specific features. Keywords desktop, Windows, Linux, macOS, settings, keybinds, ConfigFile, DisplayServer, Steam, fullscreen.

日本語の概要は準備中です。原文の説明を表示しています。

Expert blueprint for sports games (FIFA, NBA 2K, Rocket League, Tony Hawk) covering physics-based ball interaction, team AI formations, contextual input, and match umpire/score authority. Broadcast framing routes to godot-camera-systems. Use when building soccer, basketball, hockey, racing sports, or arcade sports games. Keywords ball physics, magnus effect, formation AI, team tactics, contextual controls, steering behaviors.

日本語の概要は準備中です。原文の説明を表示しています。

Create a comprehensive brand standards document — covering logo usage, color, typography, voice, messaging, and application rules. Use when the user says "brand guidelines", "brand standards", "brand book", "style guide", "brand guide", "brand manual", "brand rules", "brand documentation", "brand toolkit", "onboarding designers or copywriters", "need a document for the team", "brand consistency across teams", or wants to codify all brand decisions into a reusable reference document.

日本語の概要は準備中です。原文の説明を表示しています。

Write a brand manifesto — a bold, belief-driven declaration of what the brand stands for, fights against, and exists to change. Use when the user says "brand manifesto", "manifesto", "what we believe", "brand declaration", "brand belief statement", "rally the team around the brand", "inspire the team", "internal brand document", "culture document", "why we exist statement", "brand credo", "brand creed", or wants to write something that goes beyond a mission statement to express the brand's conviction and worldview.

日本語の概要は準備中です。原文の説明を表示しています。

Use when briefing or managing an EXTERNAL agency, freelancer, or production vendor — scope of work, deliverable specs, revision rounds, approval process, USD payment milestones, IP assignment and confidentiality terms, communication rules, and a post-project vendor scorecard. Trigger on 'brief an agency', 'hire a freelancer', 'scope of work', 'the agency is not delivering', 'onboard a new vendor', 'we keep paying for work we have to redo'. Also use when the user is about to sign a supplier with nothing written down. Not for — briefing an internal team member, see `64-team-brief-global`; the campaign brief itself, see `02-campaign-brief-global`; the asset list the vendor produces, see `41-campaign-asset-list-global`.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process review, lessons written back into the playbook and Brand Hub, and action items with owners. Trigger on 'campaign retrospective', 'campaign retro', 'post-mortem', 'campaign debrief', 'what worked and what did not', 'the campaign is over, what did we learn'. Also use when a campaign underdelivered and the team is arguing about why. Not for — a periodic performance report, see `07-marketing-report-global`; diagnosing live numbers mid-flight, see `03-performance-eval-global`; the next period ads plan, see `57-next-ads-plan-global`.

日本語の概要は準備中です。原文の説明を表示しています。