Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfillment, and supply risk. Use this to reduce stockouts or excess inventory, plan for a supplier failure, decide reorder points and safety stock, improve fulfillment reliability, or assess concentration risk in a supply base.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Supply chains fail at variability, not at averages. A chain planned on average demand and average lead time will disappoint at both ends: stockouts when either runs long, dead stock when they do not.
Safety stock exists to absorb variation in demand and in lead time. Sizing it needs both the average and the spread — a supplier averaging 20 days at ±2 is a different proposition from one averaging 20 days at ±15, and treating them the same guarantees you are wrong about one.
Set reorder points on lead-time demand plus safety stock, and revisit them when either input moves. A reorder point set once is a reorder point that is now wrong.
Hold inventory where it is most flexible. Stock held as components serves several finished configurations; the same value held as finished goods serves one and obsoletes faster.
Quoted lead time is a marketing number. Plan against your own measured receipt dates, including the bad months. Track the variance explicitly — reliability of lead time usually matters more than its length, because a long predictable lead time can be planned around and a short erratic one cannot.
Map dependencies past the first tier. Two suppliers on paper who share a single sub-supplier, a single port, or a single region are one supplier with extra paperwork.
For each critical input know: who else could supply it, how long qualifying them takes, and whether anything in the design makes switching hard. That answer is worth having before you need it — qualifying an alternate under pressure is where quality problems enter.
Supplier commercial terms and exit rights belong with operations:vendor-management; continuity of
the wider business process belongs with operations:business-continuity-and-resilience.
Measure on-time-in-full, not on-time and in-full separately — partial shipments that arrive on schedule are a way of appearing to hit a target while failing the customer.
Diagnose misses by cause: supply, capacity, information, or process. The remedies do not overlap, and a fulfillment problem attributed to the wrong one gets more expensive rather than better.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
日本語の概要は準備中です。原文の説明を表示しています。
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
日本語の概要は準備中です。原文の説明を表示しています。
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
日本語の概要は準備中です。原文の説明を表示しています。
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
日本語の概要は準備中です。原文の説明を表示しています。
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
日本語の概要は準備中です。原文の説明を表示しています。