Use when work has genuinely independent streams or distinct builder, evaluator, domain, and integration roles that require bounded multi-agent command scaled from 5 to 100+ agents.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a defined problem needs diverse ideas, cross-domain combinations, and cheap experiments instead of a single untested answer.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
<skill_contract> <input>Defined problem, target user, desired change, constraints, prior attempts, and experiment budget.</input> <output>Three non-equivalent options with scored mechanisms and falsifiable minimum experiments.</output> <done>Each selected option has a hypothesis, smallest artifact, participant, threshold, budget, stop rule, and failure learning.</done> <non_goals>Unbounded brainstorming, novelty without utility, polished prose before diversity, or presenting ideas as validated demand.</non_goals>
Create option value by combining mechanisms, constraints, and analogies, then convert the strongest options into minimum experiments.
Provide: problem, target user, desired change, constraints, existing attempts, and experiment budget. Optional: domains or concepts to combine.
Rewrite the request as For [user], change [state] under [constraints], measured by [signal]. Extract reusable building blocks: actors, assets, mechanisms, channels, incentives, and constraints.
<unknowns_gate>
If no user, problem, or constraint is available, return NEEDS_INPUT with one discriminating probe. Treat market demand, technical feasibility, and user behavior as testable unknowns, not assumptions to hide.
</unknowns_gate>
<execute>Do not optimize prose before option diversity. A useful failed experiment is better than an impressive concept with no falsifier.
</execute> <evaluate>Check that the top three differ in mechanism, fit constraints, expose their largest unknown, and can be tested cheaply. Remove ideas that are only features, slogans, or unsupported scale claims. Recombine once if all finalists share the same failure mode.
</evaluate>NEEDS_INPUT: the problem frame lacks a user or constraint.INSUFFICIENT_EVIDENCE: ranking depends on unavailable market or technical facts; mark provisional and probe.VERIFY_FAILED: finalists are duplicates or have no falsifiable test; regenerate around different mechanisms.BUDGET_STOP: no experiment fits the budget; return the cheapest information-gathering action.Return status, result (idea clusters and top-three experiments), evidence (inputs and scoring basis), unknowns, and next_action.
</skill_contract>
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Use when work has genuinely independent streams or distinct builder, evaluator, domain, and integration roles that require bounded multi-agent command scaled from 5 to 100+ agents.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or refactoring a model-native engineering workflow with bounded autonomy, probes, custom evaluation, durable state, and verified write-back.
日本語の概要は準備中です。原文の説明を表示しています。
Use when property-service operations need an AI plus ontology plus DMAIC design for work orders, dispatch, quotes, evidence, CTQ metrics, and control dashboards.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a personal or team operating system needs a bounded redesign using Four-C, closed-loop controls, 70/30 allocation, 3B creativity, experiments, and prediction-error learning.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a goal must be converted into a repeatable behavior, cue, SOP, review cadence, and identity-aligned reinforcement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when source material must be transformed into a compact, evidence-aware model for learning, decisions, or an Obsidian concept note.
日本語の概要は準備中です。原文の説明を表示しています。