「technology」の検索結果

Executes comprehensive red team exercises that simulate real-world adversary operations against an organization's people, processes, and technology. The red team operates with stealth as a primary objective, employing the full attack lifecycle from initial reconnaissance through objective completion while testing the organization's detection and response capabilities. This differs from penetration testing by focusing on adversary emulation rather than vulnerability identification. Activates for requests involving red team exercise, adversary simulation, adversary emulation, or full-scope offensive security assessment.

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

"Apply network economics to analyze markets with network effects, critical mass dynamics, and platform competition. Use this skill when the user needs to evaluate tipping points, lock-in risks, switching costs, or standards wars, especially in technology platforms and two-sided markets.".

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

"Apply Actor-Network Theory (Latour, Callon) to trace how human and non-human actors (actants) form networks through translation processes. Use this skill when the user needs to map sociotechnical assemblages, analyze how innovations stabilize or fail through network-building, trace the four moments of translation (problematization, interessement, enrollment, mobilization), or when they ask 'how did this technology become accepted', 'who and what holds this network together', or 'why did this innovation fail to gain traction'.".

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

"Corporate innovation-governance toolkit integrating Stage-Gate process, 3 Horizons model, innovation portfolio management, open innovation, corporate venture capital (CVC), innovation KPIs, and intrapreneurship. Use for innovation-portfolio design, second-curve planning, innovation-project review gating, open-innovation evaluation, CVC setup, innovation-KPI design, or managing tension between core and new businesses. Triggers: 『第二曲線』『創新專案怎麼管』『新事業孵化』『收購投資新創』『Stage-Gate』『研發投資組合』『內部創業』『開放式創新』『CVC』『3 Horizons』『創新 KPI』. For Taiwan EMBA innovation-management/strategy/technology-management cases (台大／中山). Startup basics: use Asgard `ux-lean-startup`; innovation theory: use Asgard `grad-disruptive-innovation`, `grad-ambidexterity`; 家族二代接班治理: use `biz-corporate-governance` 或 `ops-talent-strategy`; ESG/淨零策略結合: use `biz-net-zero-transition`.".

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

"Customer relationship management strategy — integrated framework with six pillars: customer segmentation (RFM/CLV), journey orchestration (cross-channel), CDP technology stack, loyalty-program design, B2B key-account management (KAM), and CRM organization/governance. Use for VIP program design, membership-system decision, retail/ecommerce/B2B customer strategy, CDP buy-vs-build, marketing-automation adoption, or key-customer churn. Triggers: 『CRM 系統』『會員經營』『客戶分級』『大客戶策略』『CDP』『行銷自動化』『客戶生命週期』『VIP 方案』『顧客忠誠』『RFM』『CLV』『KAM』『Journey Orchestration』. For 師大 EMBA CRM, 政大 ecommerce, 中山 marketing cases. Complements Asgard `biz-cac-ltv` (tactics) and `biz-customer-journey` (single method) with the strategic integration layer.".

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

Build structured vendor/tool evaluation matrices with weighted scoring, TCO analysis, and recommendation memos. Covers criteria definition, deal-breaker identification, and negotiation points. Use when selecting SaaS tools, evaluating technology vendors, or making build-vs-buy decisions.

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

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

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

Reconnaissance and methodology playbook. Use when mapping assets, discovering endpoints, fingerprinting technology, and building a structured testing plan for a new target.

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

Entry P1 category router for reconnaissance and methodology. Use when mapping scope, discovering assets, fingerprinting technology, building endpoint inventory, and choosing the first high-value security testing path.

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

Use when reviewing or improving frontend accessibility, semantic structure, keyboard support, focus management, ARIA labels, screen reader behavior, WCAG 2.2 issues, touch accessibility, or assistive-technology regressions; Chinese triggers include accessibility, accessibility, a11y, WCAG, screen reader.

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

Use when planning or implementing an intentional migration from JavaScript, jQuery, HTML/CSS, server-rendered templates, MPA legacy frontend code, or older framework code toward a modern frontend stack while preserving behavior. Do not use for routine legacy bug fixes that stay in the old stack; Chinese triggers include legacy projects, technology stack upgrades, jQuery migration.

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

Use when a task needs the judgment of a Computer and Information Systems Manager (IT Manager/Director/CIO-adjacent) — planning IT infrastructure and systems strategy, evaluating a technology vendor or platform decision, allocating an IT budget, or managing IT risk (security, uptime, technical debt) at an organizational level. Broader than the devops-sre or software-engineer roles — this one owns IT as a business function, not a specific engineering discipline.

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

Use when a task needs the judgment of a Compliance Manager — sizing and defending a compliance program's headcount/budget, deciding build-vs-buy on monitoring or case-management technology, choosing a centralized-vs-embedded staffing model, translating a new regulatory obligation into a costed resourcing ask, or reporting program coverage to executives/the board.

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

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

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

Full-spectrum product research pipeline. Runs competitive analysis, technology trend scouting, user feedback analysis, and feature ideation. Triggers: on: research, competitive research, market research, feature discovery, what should we build next.

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

Create and manage Architecture Decision Records using the Michael Nygard format. Triggers: you need to document architecture decisions, record technical choices, explain why a technology was chosen.

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

Audit pharmaceutical yield prediction systems and process analytical technology -- evaluate critical process parameter (CPP) to critical quality attribute (CQA) relationships, design space characterization per ICH Q8(R2) Quality by Design, PAT sensor readiness (NIR, Raman.

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

Analyze airline, airport, cruise, and tour operator systems for ground handling efficiency, aircraft turnaround optimization, disruption management, and GDS integration. Covers IATA/ICAO compliance, IROPS recovery, on-time performance tracking, embarkation logistics, transfer coordination, and NDC implementation for travel technology platforms.

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

Audit e-discovery and litigation document review systems -- data collection pipelines (PST, MBOX, SharePoint, Slack), document processing (OCR via Tesseract/ABBYY, metadata extraction, deduplication), Technology Assisted Review (TAR 1.0/2.0/CAL with recall/precision tracking).

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

Analyze disability services software — IEP and ISP management, person-centered planning workflows, HCBS Settings Rule compliance, accommodation tracking, assistive technology integration, EVV (Electronic Visit Verification), caregiver and DSP scheduling, and outcome measurement.

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

**WORKFLOW SKILL** — Understand before implementing. USE FOR: any task where the agent might rush to code — forces understanding WHY/WHAT FOR/FOR WHOM before defining a solution, activates planning and reasoning discipline, prevents technical debt from shallow requests. Use to validate intent, plan before coding, reason before acting, challenge assumptions, prevent premature implementation. DO NOT USE FOR: deep multi-technology analysis (use contextação), persisting decisions across tasks (use task-map).

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

TechLead (Senior Technical Lead) agent. Reads all BA artifacts and produces system architecture, technology stack, ERD, sequence diagrams, and ADRs. Declares Gate 1: Design Freeze. Part of the Virtual Team Skill pipeline.

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

Comprehensive China expertise debunking sinophobia, explaining phenomenal 40-year progress, technology leadership, realistic challenges, and optimistic future outlook

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

Creates reference documentation structure + smart documents (ADRs/Guides/Manuals) based on TECH_STACK. Only creates justified documents (nontrivial technology choices).

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