「team」の検索結果

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`.

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

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 someone outside the marketing team has to film — a customer for UGC, an employee for EGC, or a paid creator or KOC — and needs a brief: talking points, shooting guide, do and do-not list, usage rights, deliverables, and batch management. Trigger on 'UGC brief', 'creator brief', 'KOC brief', 'brief for employee videos', 'what do I tell the influencer', 'we hired a creator to film'. Also use when the user asks how to get customers to make videos for the brand. Not for — a script the team writes and shoots itself, see `04-script-video-global`; edit direction for footage already shot, see `44-video-editor-brief-global`; posting inside communities, see `38-community-seeding-global`.

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

Use when a team wants to design, audit, or operate an AI Marketing OS — a Brand Hub source of truth, role-based AI projects for leader, content, design, performance, and knowledge, skill chains, ChatGPT plus Claude plus NotebookLM workflows, MCP connectors, a Notion or Drive second brain, ads data loops, SOPs, weekly reviews, and handoffs. Trigger on 'AI marketing OS', 'set up our marketing AI system', 'Brand Hub', 'AI workflow for the team', 'MCP for ads data', 'how do I make AI actually useful for marketing'. Not for — one campaign brief, see `02-campaign-brief-global`; the weekly report, see `07-marketing-report-global`; the brand visual rules, see `46-brand-guideline-global`; the product context file, see `product-marketing-context-global`.

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

VP Engineering perspective - org design (team topologies), process improvement, cross-team dependencies, engineering culture, OKRs, incident management maturity, platform strategy, DX optimization, release management at scale

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

Install a .NET SDK locally for safe preview testing, specific-version pinning, or reproducible team setups — without modifying the system-wide installation. USE FOR: trying .NET previews safely, testing specific SDK versions, installing MAUI or other workloads on a preview, updating or replacing an existing local SDK, creating reproducible team/CI install scripts, configuring global.json paths. DO NOT USE FOR: system-wide SDK installs, .NET hosts older than 10, runtime-only installs, or projects not using SDK-style commands.

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

LLM and AI application security testing — prompt injection, jailbreak resistance, OWASP LLM Top 10 (2025), RAG and agent/tool-use security, model supply chain, and AI red teaming for authorized assessments

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

System hardening, detection engineering, security baseline monitoring, patch management, defense-in-depth architecture, and security posture improvement

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

Use when running a full red-team engagement end-to-end — initial access, persistence, privilege escalation, defense evasion, C2 infrastructure, EDR bypass, living-off-the-land

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

Use when red-teaming an agentic AI / LLM application — indirect & zero-click prompt injection, MCP tool poisoning, persistent memory poisoning, excessive-agency tool abuse, multi-turn jailbreaks, PyRIT/Garak/Promptfoo harnesses

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

Use when hunting threats or engineering detections — ATT&CK Detection-Strategies, Sigma + correlation with Detection-as-Code CI, Windows endpoint hunting (Sysmon/ETW/LSASS/LOLBins), network C2 hunting (JA4+, beaconing, DNS tunneling), cloud-identity hunting, Atomic Red Team purple-team validation

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

Detect domain from context and find appropriate team member

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

Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.

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

Applies modular monolith with enforced internal boundaries. Use when teams want service-level autonomy without distributed system overhead.

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

Generates structured OKR plans (Objectives and Key Results) for teams and companies following Google/Intel methodology. Takes company goals, team function, quarter, and current metrics to produce a comprehensive okr-plan.md with objectives, key results, scoring criteria, alignment mapping, tracking cadence, and retrospective templates.

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

End-to-end Android APK red-team pipeline

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

Run structured AI red team exercises for jailbreak resistance, data exfiltration risk, harmful output controls, and agent tool abuse resilience.

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

Applies the reasoning, principles, and mental models of Sebastian Thrun (robotics and self-driving cars pioneer, founder of Google X, Waymo, Udacity, Stanford University). Reach for this skill whenever Claude is asked to advise on hardware/software systems engineering, autonomous vehicles, moonshot ideation, probabilistic robotics (SLAM), or leading high-stakes engineering teams. Trigger this skill for discussions on democratizing education, regulating AI, transitioning from academic research to product development, or managing technical teams with empathy. Use it to shift focus from incremental component debates to end-to-end execution and audacious goals.

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

Generate concise, structured summaries of requirements for quick team understanding. Use when analyzing requirements from text documents (MD, TXT, DOCX) or technical specifications to create bullet-point summaries that highlight core functionality and dependencies/constraints. Ideal for sprint planning, stakeholder updates, team onboarding, or any situation requiring rapid comprehension of requirement documents.

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

Configure multi-tenant organizations, manage members and invitations, define custom roles and permissions, set up teams, and implement RBAC using Better Auth's organization plugin. Use when users need org setup, team management, member roles, access control, or the Better Auth organization plugin.

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

Use when a task may benefit from a bounded subagent for implementation, large-codebase discovery at task start, independent review, requested or pre-commit code simplification, or expert work on complex decisions, modeling, automation, or repeated failures. The main agent chooses whether to delegate and accepts the result. Do not use for simple questions or short work with no meaningful review or delegation.

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

Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings. Use when defining red-team rules of engagement, assessing prompt injection or excessive agency, testing tool and identity boundaries, evaluating memory or cross-agent attacks, scoring a campaign, or verifying remediation in an approved environment.

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

The telemetry each Active Directory technique generates and what alerts a defender: Kerberoasting produces Event 4769 with RC4 encryption (0x17) and an MDI alert, DCSync produces Event 4662 with the DS-Replication-Get-Changes GUID, AS-REP roasting produces Event 4768 with no pre-auth, LSASS dumping is blocked by EDR, plus a lateral-movement telemetry table by protocol (SMB/WMI/WinRM/RDP/DCOM). Use this whenever you run or plan an offensive AD technique and need to know what noise it makes, when writing the engagement's detection notes, or when a defender wants to know what to monitor. Teaches red teamers what is loud and blue teamers what to watch. Standard-tooling knowledge, no vendor engine.

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

Research startups and emerging companies with funding data, team composition, product positioning, market traction, and news coverage. Combines Apollo firmographics, LinkedIn team data, and web intelligence for comprehensive startup due diligence.

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