Writes down what is being built so a team can build it and know when they are done — problem and success measure before solution, scope stated by exclusion, user-visible behavior including the states everyone forgets, acceptance criteria someone can test, and the open questions named rather than buried. Use this to write a specification, review one that is causing rework, or work out why a delivered feature technically matched the request and still was not what anyone wanted.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
A specification exists to prevent expensive rediscovery — of decisions already made, of scope already agreed, and of the edge cases that are found either now on a page or later in production.
Open with who has the problem, what it costs them today, and what you expect to change if this ships — expressed as a measure with a target and a date. A document that starts with a solution invites the team to optimize the wrong thing and gives you no way to tell afterward whether it worked.
Decide the success measure before building, not at launch. A number chosen afterward is chosen to be met.
Everyone reads what is in scope and assumes the rest is coming. An explicit "not in this" list is the cheapest thing in the document and prevents most scope arguments — including the ones that arrive as clarifications rather than as requests.
Say what is deferred versus what is rejected. Those are different, and conflating them means the rejected thing comes back.
Write what the user experiences and what the system guarantees. Leave the how to the people who will own it — a specification that dictates implementation gets a worse implementation and blurs who is accountable for it.
The states nobody writes down are where the rework comes from. Empty, loading, error, partial, permission-denied, offline, and the first-run case with no data. Also: what happens to records that already exist, what happens at the limits, and what happens when two people do it at once. Most "that wasn't what I meant" traces back to one of these.
Each one should be a statement someone can evaluate as true or false without asking you. "Fast" and "intuitive" are not criteria; a response-time budget and a task someone completes unaided are.
If a criterion cannot be tested, it is either a principle — say so and move it — or it is not finished being thought about.
Every specification has unknowns. Listing them, with an owner and a date needed by, is what separates a document that is honestly incomplete from one that is quietly wrong. Buried uncertainty gets resolved by whoever hits it first, usually at the least convenient moment and without anyone noticing a decision was made.
A specification that diverges from what was built becomes a trap for the next person. Either update it as decisions change, or mark it as-of-a-date and point at wherever the truth now lives. The worst outcome is a document that looks current and is not.
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.
日本語の概要は準備中です。原文の説明を表示しています。