Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of authority, insurance, and business continuity. Use this to prepare board or committee materials, record a decision that needs to be minuted, set or check approval authority, review insurance and continuity coverage, establish a retention policy, or work out where a responsibility belongs when it falls between functions.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
The record of what the company decided, who was allowed to decide it, and what happens when something goes wrong. Unglamorous until it is the only thing that matters.
One authoritative place holding: formation and entity documents, ownership and cap table, board and shareholder resolutions, minutes, signed agreements above the review threshold, insurance policies, and material licenses and registrations.
The failure mode is not losing a document; it is not knowing which version is current. Every record carries its effective date, and superseded versions are marked superseded rather than deleted — "what was in force in March" is a question that gets asked in exactly the circumstances where you cannot afford to guess.
Materials go out with enough notice to actually be read — a deck delivered the night before produces a meeting where the deck is presented rather than discussed.
Each item is labeled by what it needs: decide, discuss, or note. Meetings run long because everything is presented as if it needs all three.
Minutes record decisions, who was present, who abstained or recused, and the basis on which a decision was taken. They are not a transcript. Where a decision was contested, that is worth recording — it is evidence the board exercised judgment rather than rubber-stamping.
Write down who can commit the company to what, at which value, and what requires escalation. Cover spending, contracts, hiring, and anything creating a long-term obligation.
Two failures, both common: thresholds so low that everything escalates and the process is routed around, and thresholds nobody wrote down, so authority is whatever was not challenged last time.
Review after any material change in size or structure.
Know what is covered, what is excluded, what the limits are, and who to call. The exclusions matter more than the coverage and are read least.
For continuity: what are the handful of things the business cannot operate without, what happens if each is unavailable for a week, and who decides. An untested plan is a document, not a capability — walk through one scenario annually rather than writing more of them.
A policy naming, per record type, how long it is kept and what happens at the end. Then a mechanism that actually enforces it, because retention by intention keeps everything forever.
Retention periods are set by statute and by what you might need to defend, whichever is longer. Never destroy anything under a legal hold, and know who can place one.
Some responsibilities sit between functions and get dropped. When one appears, do not debate the right home in the abstract — assign it to whoever bears the consequence if it fails, and record the assignment. An owner who is imperfect beats an owner who is undecided.
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.
日本語の概要は準備中です。原文の説明を表示しています。