「planning」の検索結果

Designs PROTACs, molecular glues, and bivalent degraders with explicit handling of E3 ligase choice (VHL, CRBN, IAP, MDM2, KEAP1), linker design (length, composition, rigidity), ternary complex prediction (PRosettaC, DeepTernary, AlphaFold3 with constraints), cooperativity (alpha), DC50 / Dmax characterization, hook effect, and prediction-experiment reconciliation. Use when designing targeted protein degraders, planning linker SAR, predicting ternary complex stability, or building generative degrader workflows.

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

Analyzes chemical libraries by scaffold using Bemis-Murcko scaffolds, generic frameworks, cyclic skeletons, matched molecular pair (MMP) analysis via mmpdb, R-group decomposition, Free-Wilson analysis, scaffold hopping, and chemotype-aware ML train/test splits. Use when identifying chemotype clusters in a library, deriving SAR transformation rules, decomposing series into R-groups, performing scaffold-balanced QSAR splits, or planning analog campaigns.

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

Designs adaptive clinical trials including group-sequential (O'Brien-Fleming, Pocock, Lan-DeMets spending), sample-size re-estimation (blinded Friede-Kieser, unblinded Cui-Hung-Wang, Mehta-Pocock promising zone), seamless Phase 2/3 with treatment-arm selection, population enrichment, and response-adaptive randomisation. Covers FDA 2019 Final Adaptive Designs Guidance, FDA 2022 Master Protocols, and ICH E20 Step 2b/3 draft (June 2025, NOT final). Use when planning interim analyses, sample-size re-estimation, or master/platform-trial designs.

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

Use this skill when the user asks the cost of pulling a Motor Vehicle Record (MVR) in a specific state, or wants to compare MVR fees across multiple states, or is budgeting annual compliance costs for a multi-state fleet. Reference the canonical fee table below; flag that fees change (re-verify with state DMV before annual budget planning).

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

Use when a driver has been involved in a crash — regardless of preventability or injury — and the carrier needs to handle the immediate, post-investigation, and return-to-work phases. Covers trauma response, post-accident testing under 49 CFR 382.303, paid time off, retraining, light duty, and re-entry planning.

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

Use this skill to understand the geographic patterns of FMCSA inspections. Covers high-inspection states, why they're high-inspection, and operational planning.

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

Use when a driver has been disqualified or is at risk of disqualification — major offense convictions (DUI, leaving the scene, drug trafficking with CMV), serious traffic violations, RR-grade-crossing violations, imminent-hazard out-of-service, or Clearinghouse positive-test prohibited status. Also use when planning a return-to-duty pathway, SAP process, or reinstatement timeline. Covers 49 CFR 383.51, Part 40 Subpart O, and Part 391.15.

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

Use when a dispatcher, operations manager, or owner asks how to plan loads to minimize empty (deadhead) miles, sequence freight efficiently, balance regional capacity, design dedicated loops, or build a load-pairing strategy across customers. Covers loaded-ratio math, lane balance, region-pair pricing, and software-supported optimization.

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

Use when a carrier owner, CFO, or controller asks how to build an annual budget, monthly P&L model, cash flow forecast, scenario plan, or break-even analysis for a trucking operation. Covers revenue modeling, cost structures, capital planning, and the discipline of tracking actuals vs budget.

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

Use when a fleet manager or owner asks when to replace tractors and trailers, optimal trade cycle age, total cost of ownership analysis, residual value timing, dealer-vs-auction sale strategy, and how trade cycle affects driver retention and operating cost.

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

Use when a carrier asks about disaster recovery (DR) and business continuity planning (BCP) — cyber incident, natural disaster, terminal loss, key-person departure, financial liquidity event, major customer loss, insurance crisis, or fuel supply disruption. Covers risk assessment, continuity strategy, communication plans, and recovery time objectives.

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

SERP-based semantic topic clustering for content architecture planning. Groups keywords by actual Google SERP overlap (not text similarity), designs hub-and-spoke content clusters with internal link matrices, and generates interactive visualizations. Optionally executes content creation if claude-blog is installed. Use when user says "topic cluster", "content cluster", "semantic clustering", "pillar page", "hub and spoke", "content architecture", "keyword grouping", or "cluster plan".

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

Programmatic SEO planning and analysis for pages generated at scale from data sources. Covers template engines, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention. Use when user says "programmatic SEO", "pages at scale", "dynamic pages", "template pages", "generated pages", or "data-driven SEO".

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

Pre-commitment attack on a plan by an agent that did not write it. Use when presenting a feature-deep-dive plan, assigning vision-to-fleet briefs, moving a register to build mode, ratifying a scope list, or coding a new contract or table. NOT for built work or DONE reports (use subagent-dispatch).

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

Doctrine for auditing an ENTIRE feature and building it to its ideal state. Use on 'deep dive on X', 'audit the X feature', 'figure out everything X does', 'take over X and finish it', 'bring X up to best practices', or when a whole feature needs overhauling, unifying, or finishing, not patching. NOT for one small addition (use build-sub-feature).

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

非自明なタスク（3ステップ以上、アーキテクチャ判断、複数ファイルにまたがる変更）に取り組む際の計画・実行・検証サイクル。タスクの開始時、実装がうまくいかず再計画が必要な時、バグ修正やリファクタリングの着手時にこのスキルを参照する。「計画を立てて」「TODO を整理して」「この機能を実装して」「バグを直して」といったリクエストや、明らかに複数ステップを要するタスクではこのスキルを使う。ただし、大規模な新機能開発（コードベース探索・アーキテクチャ設計・並列レビューが必要な重量級タスク）には feature-dev プラグイン（/feature-dev）の方が適切。

需要予測、安全在庫最適化、補充計画、プロモーション効果推定のための体系化された 専門知識。数百のSKUを管理する15年以上の経験を持つデマンドプランナーの知見に 基づく。予測手法の選択、ABC/XYZ分析、季節変動管理、ベンダー交渉フレームワーク を含む。需要予測、安全在庫設定、補充計画、プロモーション管理、在庫水準最適化 時に使用。

Build reactive, type-safe, production-grade backends. ALWAYS use this skill when the user asks to build, plan, design, or implement backend features, APIs, data models, server logic, database schemas, web apps, full stack apps, or mobile apps. This includes planning and architecture discussions.

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

Comprehensive toolkit for writing high-quality computer science research papers (conference, journal, thesis). Provides narrative construction guidance, sentence-level clarity principles (Gopen & Swan), academic phrasebank, CS-specific conventions, and section-by-section quality checklists. Use when assisting with academic paper writing, revision, or structure planning across all stages from drafting to submission.

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

[30] ANALYZE. Understand how changes impact the system — what's the core, what's affected, what depends on what. Use when planning changes, analyzing systems, debugging issues, or anytime you need to see the full picture of cause and effect. Triggers on "what's affected", "impact analysis", "dependencies", "scope mapping", or when you need to understand ripple effects.

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

[31] ANALYZE. Universal deep thinking methodology for any situation requiring quality reasoning. Use when solving problems, debugging, making decisions, analyzing code, planning, reviewing, or anytime you need thorough thinking instead of surface-level responses. Triggers on "think deeply", "analyze thoroughly", "reason carefully", "deep thinking", "understand completely", or any task requiring careful thought.

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

6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.

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

Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration.

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

The PRIMARY development workflow for the Archon project (remote-coding-agent). Use this skill instead of any PRP skills when working on Archon code. Routes to 10 specialized cookbooks based on what the user is trying to do: RESEARCH — "how does the orchestrator work?", "where is session state defined?", "trace the workflow execution flow", "what is IWorkflowStore?" INVESTIGATE — "should we use Drizzle or Prisma?", "what's the best way to add WebSockets?", "can we migrate to Turso?", "how do other projects handle rate limiting?" PRD — "write a PRD for dark mode", "spec out the notification feature", "product requirements for webhook retry" PLAN — "plan the auth refactor", "design the caching layer", "create an implementation plan for #42" IMPLEMENT — "implement the plan", "execute .claude/archon/plans/auth.plan.md", "build the feature from the plan", "code this up" REVIEW — "review PR #123", "review my changes", "code review the diff" DEBUG — "debug the failing test", "why is streaming broken?", "root cause analysis on the timeout issue" COMMIT — "commit these changes", "commit the auth refactor" PR — "create a PR", "open a pull request for this branch" ISSUE — "report this to gh", "create a gh issue", "log it in github", "file a bug for this", "create a feature request" This skill triggers on ANY development task: researching, investigating, planning, building, reviewing, debugging, committing, or shipping code. NOT for: Running Archon CLI workflows in worktrees (use /archon instead).

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