「plan」の検索結果

Use when the user asks to "plan the participation ramp before we promote", "how much account history or karma do we need in this community", or "design entry incentives and member lifecycle for our own Discord"; produces the per-community pre-promotion warming plan — account-history/tenure expectations (Estimated, named sources), a give-before-ask ledger spec, a per-community etiquette + rule digest with last-verified dates, and the warming → active graduation criteria that channel-registry requires as state-transition evidence — plus the owned-community variant (entry paths + member lifecycle for your own Discord/Slack/forum/企业微信私域). Not for launch-day submissions or T-0 threads — use community-launch-runner. 社区预热/先给后取/账号养成/毕业标准

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

Use when the user asks to "launch on Product Hunt / Hacker News", "prepare community or directory launch submissions", or "plan the launch submission waves"; produces per-platform submission packages — a Product Hunt tagline / gallery / first-comment skeleton, a factual Show HN title and text, per-subreddit posts with a self-promotion rules table, tiered directory waves, and a regional channel matrix including Chinese communities — plus a platform red-line check (never solicit votes or organize voting rings) and T-0 submission-status lines for the launch registry. Not for paid amplification — use content-amplifier; not for creator channels — use campaign-planner; not for launch telemetry readouts — use launch-monitor; not for ongoing community presence or pre-launch karma-building outside the launch window — use participation-warmup-planner. 社区发布/PH提交包/Show HN/目录波次/平台红线/中文渠道

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

Use when the user asks to "pick a bid strategy", "set a tCPA/tROAS target", or "plan the learning-phase entry"; produces a bid-strategy choice (tCPA / tROAS / max-conversions / manual CPC), the starting target math, a portfolio grouping map, and a learning-phase entry plan. Not for splitting the budget across campaigns — use budget-optimizer; not for in-flight pacing/scale moves — use budget-pacing-monitor; not for scoring the account — use ad-account-auditor. 出价策略/tCPA目标/tROAS/学习期

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

Implement load testing, auto-scaling, and capacity planning for Claude API. Use when running performance benchmarks, planning for traffic spikes, or configuring horizontal scaling for Claude-powered services. Trigger with phrases like "anthropic load test", "claude scaling", "anthropic capacity planning", "scale claude api".

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

Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth. it uses the capacity-planning-analyzer plugin to assess current utilization, forecast growth trends, and recommend scaling strategies. use this skill when the u... Use when analyzing code or data. Trigger with phrases like 'analyze', 'review', or 'examine'.

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

Plans the stack, database schema and API for an app clone, from the recon map replica-recon wrote. Picks boring, managed tech, turns the inferred data model into real SQL with indexes and access rules, lists every route by flow, and orders the build as a thin vertical slice first. Use when the user says "plan the clone", "what stack should I use", "design the database", "write the schema", "plan the API", "architecture for my version of X", or after /replica-recon finishes.

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

Formulate evidence-bounded scientific questions, candidate hypotheses, rival explanations, causal or associational claims, discriminating predictions, measurements, and preregistration-ready analysis plans. Use when turning observations or preliminary findings into transparent, testable research plans without treating hypotheses as facts.

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

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or "make it resilient". Also trigger when designing resilient microservices, planning zero-downtime deployments, or capacity-planning for peak load. Covers stability patterns, capacity planning, deploy/release decoupling, and observability. For data systems, see ddia-systems. For system architecture, see system-design.

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

Build a complete marketing plan covering the full customer journey from stranger to raving fan. Use when the user mentions "marketing plan", "marketing strategy", "target market", "USP", "lead nurture", "customer lifetime value", "PVP Index", or "I dont know where to start with marketing". Also trigger when building a marketing plan from scratch, choosing acquisition channels, or designing end-to-end customer-lifecycle campaigns. Covers the PVP Index, channel selection, and advocacy systems. For brand messaging, see storybrand-messaging. For conversion optimization, see cro-methodology.

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

Semantic topic cluster planning and automated execution engine for claude-blog. Performs SERP-based keyword research, groups keywords by search intent and SERP overlap, builds a hub-and-spoke cluster architecture, generates an interactive SVG cluster map, and executes the full cluster by orchestrating blog-write calls with shared cluster context and automatic internal-link injection. Fills the strategy-to-execution gap: blog-strategy plans the blueprint, blog-cluster builds the house. Use when user says "blog cluster", "topic cluster", "content cluster", "cluster plan", "cluster execute", "pillar content", "hub and spoke", "content ecosystem", "cluster map".

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

Create a content brief for ONE planned post: target and secondary keywords, search intent, template choice, competitor gaps from the live SERP, sourced statistics to include, section plan, internal-link targets, and distribution ideas. Use when the user says "content brief", "blog brief", "SEO brief", "article brief". Not a skeleton only (blog-outline), a multi-post plan (blog-strategy, blog-calendar, blog-cluster), or the article itself (blog-write).

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

SERP-informed outline generation with H2/H3 heading hierarchy, competitive content gap analysis, section-by-section word count targets, chart and image placement markers, optional FAQ question planning, and internal linking zones. Skeleton only: structure, H2/H3 hierarchy, word counts, optional FAQ slots. Use blog-brief instead if you need full competitive analysis, statistics research, and image suggestions. Lighter than a full content brief, generates article skeleton and structure only, ready for /blog write to consume. Use when user says "outline", "blog outline", "content outline", "structure blog", "plan sections", "article skeleton", "heading structure", "SERP analysis", "competitive outline", "plan article".

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

Semantic topic cluster planning and automated execution engine for claude-blog. Performs SERP-based keyword research, groups keywords by search intent and SERP overlap, builds a hub-and-spoke cluster architecture, generates an interactive SVG cluster map, and executes the full cluster by orchestrating blog-write calls with shared cluster context and automatic internal-link injection. Fills the strategy-to-execution gap: blog-strategy plans the blueprint, blog-cluster builds the house. Use when user says "blog cluster", "topic cluster", "content cluster", "cluster plan", "cluster execute", "cluster map".

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

Keeps production assets available — ranking equipment by consequence of failure, setting preventive and predictive intervals, sizing spares, and moving a plant off reactive maintenance. Use this to build or fix a maintenance program, decide what to put on a PM schedule, diagnose repeat failures on one asset, justify spares inventory, or work out why a plant that maintains everything still has unplanned downtime.

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

Moves data from one system to another without losing it or corrupting it — profiling the source before mapping, deciding between big-bang and parallel-run cutover, reconciling counts and values rather than assuming, handling the records that will not map cleanly, and planning a rollback that is actually executable. Use this to plan or run a migration, assess a migration plan someone else wrote, work out why a completed migration is producing wrong numbers, or size how long one will really take.

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

Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.

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

Designs a coordinated multi-channel campaign or product launch around one story — objective, message, channel sequencing, timeline, assets, and the checklist that gets it out the door. Use this to plan a launch or campaign, sequence a go-to-market push, pressure-test a campaign before committing budget, or turn a product change into a coordinated set of activity. For ongoing channel programs rather than a bounded push, use `marketing-planning`.

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

Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.

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

Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and the sensitivities that show where a plan breaks. Use this to model a decision's financial consequence, build a forecast or long-range plan, evaluate an investment or hire, or pressure-test someone else's model before relying on it.

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

Amap (Gaode) Maps comprehensive service for POI search, route planning, travel planning, nearby search, heatmap visualization, and geocoding. Use when user wants to search locations, plan routes, find nearby places, or visualize geographic data.

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

Generates complete process-related diagnostic biomarker bioinformatics research designs from a user-provided disease context, gene-family or pathway theme, and validation direction. Use when a study centers on process-related genes, DEG and WGCNA integration, machine-learning feature selection, nomogram-based diagnostic modeling, immune infiltration, regulatory-network analysis, and optional external or experimental validation. Covers five study patterns (process-DEG discovery, co-expression-module integration, machine-learning biomarker selection, diagnostic model/nomogram workflow, immune-regulatory interpretation and validation) 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.

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

Generates complete phenotype-scoring bioinformatics research designs for any disease context and any user-defined phenotype, pathway, process, signature, or molecular program. Use when a study centers on gene-set or feature-set definition, intersection with DEGs or candidate features, phenotype scoring, feature selection, diagnostic or stratification assessment, immune or cellular-resolution interpretation, network analysis, and optional orthogonal validation. Covers five study patterns (signature discovery, phenotype scoring, feature selection, immune/cellular interpretation, multi-layer validation) 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.

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

Generates complete reference-grounded single-drug adverse-effect network-pharmacology research designs from a user-provided drug, adverse event, and desired evidence depth. Always use this skill when a user wants to design, plan, or upgrade a conventional network-pharmacology study centered on one fixed drug and one fixed adverse-effect endpoint, using drug-target prediction, adverse-event target collection, overlap analysis, PPI hub prioritization, enrichment interpretation, molecular docking, and optional orthogonal transcriptomic or literature validation. Covers five study patterns (canonical hub-first, cardiotoxicity or electrophysiology-oriented, immune-inflammatory adverse effect, organ-toxicity pathway context, translational validation) and always outputs four workload configs (Lite / Standard / Advanced / Publication+) with a recommended primary plan, dependency/evidence map, step-by-step workflow, figure plan, validation strategy, minimal executable version, publication upgrade path, verified-reference pack, and self-critical risk review.

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

Generates complete comorbidity-oriented shared-biomarker bioinformatics research designs from a user-provided disease pair and validation direction. Use when a study links two clinically related diseases through shared DEGs, enrichment, PPI hub genes, machine-learning feature selection, public diagnostic validation, gene-regulatory networks, immune infiltration, and optional downstream follow-up. Covers five study patterns (shared-DEG discovery, hub-gene prioritization, machine-learning biomarker selection, immune/regulatory interpretation, multi-layer validation) 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.

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