「kpi」の検索結果

Ongoing vendor privacy compliance monitoring program. Covers annual reassessment procedures, continuous monitoring signals, contract renewal privacy triggers, performance metrics, KPIs, and vendor governance reporting dashboards.

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

Design short cinematic encounters that move from calm observation to an impossible close appearance, a readable startle response, and a restrained truce gesture for MiniMax H3 or Seedance 2.0. Use when a user wants fantasy-versus-technology contrast, cockpit or window eyelines, pursuit compressed into 4–15 seconds, non-lethal escalation, identity-reference continuity, or a tense scene that resolves through performance instead of injury or dialogue exposition.

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

Full Ads Funnel Architect. Builds a complete advertising funnel across TOFU, MOFU, BOFU, and Retargeting stages with platform-specific templates, audience targeting, ad formats, copy angles, landing page requirements, KPIs, and budget allocation for Meta, Google, and LinkedIn.

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

Build supplier performance scorecards with KPIs, quality metrics, delivery performance, cost management, and improvement plans

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

Generate comprehensive marketing analytics reports by collecting KPIs, analyzing trends, and delivering actionable insights with attribution modeling and funnel analysis. Use when the user requests analytics reporting or provides relevant inputs for this workflow.

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

Content-derived infographic poster — reads the source file and builds a statistical poster from the facts already in it. Not a dashboard, not a CV, not an AntV template. Uses common-scale encodings (Cleveland–McGill floor), ISOTYPE unit counts (Neurath), custom data glyphs (Lupi/Fragapane), and a lossless data table. Palette, glyphs, and composition are derived from the source's own content. No pies, donuts, gauges, 3D charts, or fabricated KPIs. Part of the reimagine-it Content-Derived Design suite.

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

Thesis report synthesis — turn a thesis's markdown artifacts into its letter-size thesis-report.html, then OPTIMIZE it against real page renders. Four-step loop — pack (deterministic Python bundle of all sources + report/metrics.json), author (the LLM writes report/content.html — narrative, KPI tiles, badges, timeline, tables and citations are LLM judgment), assemble (deterministic validation, template injection, Q50 pins, Q47 overflow gate), render + optimize (Chrome headless per-page PNGs — the LLM reads them and iterates until every page is visually clean). Spec 046 Q46–Q50.

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

Trading as a business, performance review process, trade journaling, capital allocation discipline, business infrastructure for traders, KPI tracking for trading operations

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

Qualitative stock analysis, management operating plan MOP assessment, key performance indicator KPI identification, catalyst identification and classification, earnings call transcript analysis, qualitative evidence gathering for investment thesis

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

Think and work like an expert Clinical Embryologist. Use when a task calls for Clinical Embryologist judgment. Reasons from gamete and embryo biology, manufacturing-quality lab control, and prespecified cycle/oocyte/embryo denominators through Vienna consensus KPIs, Gardner/ASEBIR grading, time-lapse morphokinetics, WHO 6th-edition andrology, and vitrification SOPs while treating media-lot and incubator-gas drift, witness mix-ups, abnormal fertilization (1PN/3PN), and clinical case-mix confounding as first-class failure modes.

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

Map user missions from trigger to value moment, organizing features into coherent paths during PRD v0.4 User Journeys. Triggers on requests to map user journeys, define user flows, describe how users accomplish goals, or when user asks "map user journeys", "define user flows", "user missions", "how do users accomplish X?", "journey mapping", "what steps do users take?", "pain to value flow". Consumes PER- (Persona Definition), FEA- (Feature Value Planning), KPI- (Outcome Definition). Outputs UJ- entries with step flows, pain points, and value moments. Feeds v0.4 Screen Flow Definition.

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

Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model. Triggers on requests to define features, prioritize capabilities, scope MVP, map features to pricing tiers, identify parity vs. delta features, or when user asks "what features do we build?", "what's in MVP?", "which features matter?", "feature priority", "parity features", "what's our delta?". Consumes KPI- (Outcome Definition), BR- (Pricing Model, Moat), and CFD- (Market Moat Analysis) from v0.3. Outputs FEA- entries with strategic traceability and BR-FEA- governance rules. Feeds v0.4 User Journeys.

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

Establish baseline → snapshot → compare → history monitoring for any KPI, config, or metric that can drift during PRD v0.8 Deployment & Ops. Triggers on requests to monitor drift, baseline a value for later comparison, or when user asks "how do we track if X changes?", "baseline this", "config drift", "performance regression", "metric drift", "compare to last week", "is this getting worse?". Outputs MON-DRIFT-* entries with baseline + comparison rules.

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

Define, track, and act on QA metrics: test coverage percentage, flakiness rate, defect escape rate, MTTR, test execution time trends, automation ROI, quality gates, and SLAs for test suites. Includes metric formulas, realistic targets by company stage, and the action to take when each metric goes red. Use when: "QA metrics," "test metrics," "quality KPIs," "test health," "flakiness rate," "defect escape rate." Not for: building the dashboard UI (Allure/Grafana) — use qa-dashboard; measuring coverage gaps and mutation score — use coverage-analysis. Related: qa-dashboard, coverage-analysis, ci-cd-integration, release-readiness, quality-postmortem.

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

Build and visualize QA dashboards and reports with Allure Report, Grafana, and ReportPortal. Covers test execution visualization, stakeholder-facing quality reports, trend/flakiness panels, release-readiness gates, alerting, and CI integration for automated report generation. Use when: "test dashboard," "Allure," "test report," "quality dashboard," "Grafana," "ReportPortal," "test results visualization." Not for: defining which KPIs to measure or how to interpret them — use qa-metrics (this skill builds the panels; qa-metrics decides what they should show). Related: qa-metrics, ci-cd-integration, ai-bug-triage.

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

Measure and improve test coverage meaningfully. Covers Istanbul/V8/coverage.py configuration, coverage gap analysis by risk, coverage-as-ratchet in CI (never let it decrease), PR coverage diff checks, mutation testing for assertion quality, and distinguishing meaningful from vanity coverage. Use when: "code coverage," "coverage gap," "Istanbul," "coverage threshold," "coverage report," "branch coverage." Not for: writing the tests that raise coverage — use unit-testing; coverage as a tracked KPI trend over time — use qa-metrics. Related: unit-testing, ci-cd-integration, qa-metrics, ai-qa-review.

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

Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers, and timeline planning. Output is an actionable strategy document, not a shelf document. Use when: "test strategy," "QA strategy doc," "testing approach," "QA roadmap," "multi-quarter QA direction." Not for: a single-sprint or single-release plan — use test-planning. Not for: identifying which areas carry the most risk — use risk-based-testing first. Related: risk-based-testing, qa-metrics, release-readiness, test-planning, test-reliability.

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

Create polished HTML technical reports and multi-page documents for consulting deliverables. Features a professional design system with dark cover pages, warm cream content pages, Switzer + Cartograph CF typography, and a curated component library (KPI cards, data tables, callout boxes, recommendation cards, priority banners). Outputs standalone HTML that prints cleanly to PDF.

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

Create polished HTML technical reports and multi-page documents for consulting deliverables. Includes a customizable design system with dark cover page, warm cream content pages (8.5x11 portrait), professional typography, and a curated component library (KPI cards, data tables with severity coloring, callout boxes, recommendation cards, priority banners). Trigger on report, audit report, technical document, written report, assessment, or multi-page document. Outputs standalone HTML files exported to PDF via Chrome headless.

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

行銷策略全流程：受眾分析、GTM 規劃、A/B 測試設計、KPI 設定、競品定位。適合在規劃行銷活動、制定上市策略、或設計成長實驗時使用。

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

Define UX metrics and KPIs that connect design decisions to measurable business and user outcomes.

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

Strategic product leadership toolkit for Head of Product covering OKR cascade generation, quarterly planning, competitive landscape analysis, product vision documents, and team scaling proposals. Use when creating quarterly OKR documents, defining product goals or KPIs, building product roadmaps, running competitive analysis, drafting team structure or hiring plans, aligning product strategy across engineering and design, or generating cascaded goal hierarchies from company to team level.

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

Revenue-Centric Design (RCD) — evidence-backed principles for making a SaaS or startup product convert, retain, and monetize. Use when the user works on a landing page or CRO ("my page isn't converting"), onboarding/activation ("users sign up but don't stick"), churn/retention ("customers keep canceling"), pricing/monetization ("how should I price this"), checkout/forms ("dropdowns kill conversion", "annotated checkout"), dashboards/data viz ("cognitive load", "KPI shortlists"), positioning/ICP/go-to-market, feature scope, A/B-test rigor, or AI-era differentiation — or asks for the behavioral-science mechanism behind a design choice. Also use when another skill needs the principle or evidence behind a conversion/retention/pricing/checkout move. Never apply to gambling, betting, or casino products.

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

Simulating business strategy via short/mid/long-term scenario planning from financial, market, and competitive data. Applies SWOT/PESTLE/Porter, KPI forecasting, roadmaps. Does not write code.

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