「plan」の検索結果

When the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.

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

Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.

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

Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.

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

Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical reasons, or assess the people risk in a plan. Also use for onboarding design and retention of key staff.

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

Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.

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

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

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

Plans and executes earned media — press strategy, journalist outreach, announcements, commentary, and crisis response. Use this to plan a press push, write a pitch or release, find and approach the right journalists, prepare for an interview, decide whether something is newsworthy, or respond to a story going badly.

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

Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfillment capacity, or decide whether a bottleneck needs more capacity or better flow.

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

Plans and runs events that produce pipeline — conferences, trade shows, webinars, field programs, and measuring whether any of it worked. Use this to decide whether to sponsor an event, plan a conference presence or webinar, design a field program, or work out why event spend is not producing pipeline.

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

Runs the physical and hybrid workplace — space planning, leases, health and safety, office services, and the operational side of where people work. Use this to plan space, evaluate a lease or office move, set up a hybrid workplace, handle facilities incidents, or decide what office services are worth funding.

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

Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for it to work. Use this when weighing options, when a plan needs challenging before commitment, when you have already decided and want a genuine gut check, when processing meeting notes into decisions, or when competing initiatives need ranking. Distinct from `chief-executive`, which owns direction; this one interrogates a specific decision.

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

Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls, or when a plan's numbers do not reconcile. Also use to decide whether the business can afford something.

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

Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning. Use this when considering an acquisition or being approached about one, when evaluating build-versus-buy at company scale, when running or reviewing diligence, or when planning how an acquired business will actually be integrated.

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

使用 Plankton 实现编写时代码质量强制执行 —— 通过钩子在每次文件编辑时进行自动格式化、代码检查，并由 Claude 驱动自动修复。

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

Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts. Use when the user wants to prototype, wireframe, map a user flow, or plan/run usability testing.

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

Use poster layout planner for other workflows that need structured execution, explicit assumptions, and clear output boundaries.

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

Generates complete two-sample Mendelian randomization research designs from a user-provided outcome, exposure or exposure family, and robustness direction. Use when a study centers on summary-statistics causal inference with instrument selection, harmonization, IVW-primary estimation, complementary estimators, sensitivity analyses, optional multivariable upgrades, and conservative evidence interpretation. Covers five study patterns and always outputs Lite / Standard / Advanced / Publication+ with a recommended primary plan, stepwise workflow, figure plan, validation hierarchy, minimal executable version, publication upgrade path, and strictly verified literature retrieval.

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

Design a structured case-control study framework with explicit source population logic, control selection rules, matching decisions, exposure measurement planning, and bias-control checkpoints.

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

Generates complete FAERS-style pharmacovigilance disproportionality research designs from a user-provided drug class, comparator strategy, adverse-event domain, and patient-group stratification. Always use this skill whenever a user wants to design, plan, or build a spontaneous-report safety signal study using FAERS or a similar pharmacovigilance database, especially when the article logic includes product selection, indication-group stratification, MedDRA-based adverse-event extraction, serious-case filtering, suspect-drug and concomitant-exclusion logic, reporting odds ratio analysis, comparator-drug benchmarking, cross-drug comparison, and cautious signal interpretation without causal overclaiming. Covers five study patterns (single-drug disproportionality workflow, multi-drug class comparison workflow, indication-stratified workflow, comparator-controlled signal screening workflow...

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

Plans confounder control, variable adjustment logic, and bias mitigation strategies at the protocol stage for clinical, epidemiologic, translational, observational, and biomarker studies. Always use this skill when a user needs to identify major confounders, decide which variables should or should not be adjusted for, compare matching/stratification/weighting approaches, anticipate selection or measurement bias, or pressure-test a study design before execution. Focus on bias sensing, causal structure awareness, variable-role classification, and critical design review rather than generic statistical advice.

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

Plans sample size estimation logic, power assumptions, feasibility checks, and fallback enrollment strategies for clinical and translational study protocols.

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

Designs complete single-cell research plans from a user-provided biomedical direction. Always use this skill whenever a user wants to design, scope, or structure a single-cell study — including disease-focused, mechanism-focused, biomarker-focused, translational, perturbation-inspired, or validation-aware projects. It should define the research question, choose the best-fit study pattern, recommend sample grouping logic, suggest reference datasets as examples only, specify the core analysis modules, propose a validation ladder, and output four workload configurations (Lite / Standard / Advanced / Publication+). Never fabricate datasets, sample metadata, accession numbers, cohort availability, cell-type labels, external validation resources, or literature references. Always include the mandatory Dataset Disclaimer immediately before any workflow section that mentions datasets or public resources.

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

Designs complete research plans that integrate clinical variables with multi-omics data from a user-provided biomedical direction. Always use this skill whenever a user wants to design, scope, or structure a study that combines clinical variables with transcriptomics, proteomics, metabolomics, epigenomics, or related omics layers for mechanism interpretation, biomarker development, risk stratification, treatment-response analysis, or translational use. It should define the clinical use case, alignment across data layers, feature-reduction and fusion logic, modeling route, mechanism-interpretation layer, validation ladder, and four workload configurations (Lite / Standard / Advanced / Publication+). Never fabricate datasets, accession numbers, sample counts, metadata completeness, platform coverage, literature references, PMIDs, DOIs, or validation status. Always include the mandatory Dataset Disclaimer immediately before any workflow section that mentions datasets or public resources.

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

Generates complete single-compound network-toxicology research designs from one exposure, one disease or toxic phenotype, and a validation direction. Use when a study centers on one compound–one disease link and needs target collection, overlap construction, enrichment, PPI hub prioritization, docking, optional transcriptomic cross-check, and conservative mechanistic synthesis. Covers five study patterns and always outputs Lite / Standard / Advanced / Publication+ with a recommended primary plan, stepwise workflow, figure plan, validation hierarchy, minimal executable version, publication upgrade path, and strictly verified literature retrieval.

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