Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could be improved. Use this when growth has stalled or slowed, when deciding where to spend limited time or budget, when revenue rises but profit does not, when prioritizing growth initiatives, or when a business feels busy without compounding.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
One thing limits growth at any moment. Work on anything else and the effort is absorbed with no output. The entire value of this skill is finding which one.
Walk the chain in order and find the first place it breaks:
The constraint is usually not where attention is. Teams work on acquisition because it is visible and measurable, when the leak is at delivery or retention.
Two tells worth watching for:
Against the identified constraint only, generate moves and rank them by impact ÷ effort × confidence. Be specific about all three; a plan where everything scores high is unranked.
Prefer moves that compound over moves that add. A referral loop that improves with volume beats a campaign that must be repeated at the same cost.
Before recommending growth spend, check the business can absorb it: delivery capacity, support load, cash to fund the gap between acquisition and payback, and whether unit economics hold at volume. Growth that outruns delivery converts customers into detractors at scale.
Track few numbers, chosen against the constraint. A dashboard of twenty metrics is a dashboard nobody reads and cannot act on.
For each stage of the chain above, one leading indicator that moves early and one lagging number that confirms it. Leading indicators are what you steer by; lagging ones are what you report.
Two rules that prevent most dashboard failures:
Watch for metrics that improve while the business worsens: revenue up with margin down, signups up with activation down, traffic up with conversion down. Each means the mix shifted, and the headline number is hiding it.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。