mino-problem-framing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Problem Framing

解決策を選ぶ前に、誰のどの問題を、どの意味・根拠・成功条件で扱うかをEvidence状態付きで記録する。このSkillはread-onlyであり、model、contract、architecture、implementationを確定しない。

Before selecting a solution, record whose problem is being addressed, along with its meaning, rationale, and success criteria, accompanied by evidence status. This Skill is read-only and does not finalize models, contracts, architectures, or implementations.

Outcome Contract

主成果物として

Problem Framing Package

を作る。通常は次の最小構成を返し、詳細schemaはworkflow referenceへ置く。

decision scope、actor、context、観測された阻害要因、目的、損失
観測、解釈、前提、仮説、unknown、contradictionの分離
技術の引力を受けた候補を未選択の
```
candidate_means
```
へ退避した記録
具体Evidence → 目的 / 損失 → 成功・拒否・検証の
```
reasoning_trace
```
Context Packet、AI restatement、成功条件、変更境界
未決選択を候補、判定条件、Evidence取得方法、ownerへ接続したSelection Gate

problem_readiness.subject_verdict: ready | conditional | blocked

、必要な次成果物、canonical

decision

platform差が問題やEvidenceを分岐させる場合だけ、Platform Contextと未実行を含むvalidation record

The main deliverable is the

Problem Framing Package

. Typically, it returns the following minimum structure, with detailed schemas placed in the workflow reference.

Decision scope, actors, context, observed inhibitors, objectives, losses
Separation of observations, interpretations, assumptions, hypotheses, unknowns, contradictions
Records of technology-influenced candidates saved as unselected
```
candidate_means
```
```
reasoning_trace
```
linking concrete evidence → objectives/losses → success/rejection/validation
Context Packet, AI restatement, success criteria, change boundaries
Selection Gate connecting unresolved choices to candidates, judgment criteria, evidence acquisition methods, and owners

problem_readiness.subject_verdict: ready | conditional | blocked

, required next deliverables, canonical

decision

Validation records including Platform Context and unexecuted items only if platform differences branch problems or evidence

Reference Routing

内部pathは、配置先にかかわらず、インストールされた
```
skills/
```
directoryを参照rootとして解決する。
最初に
```
skills/mino-core/references/core.md
```
と
```
skills/mino-core/references/shared-policies.md
```
を読み、共通Evidence、権限、routing、canonical decisionを再定義しない。
standalone固有の成果物と判定では
```
skills/mino-problem-framing/references/workflow.md
```
を読む。
後続へ渡す要求を正規化するときだけ
```
skills/mino-core/references/requirements-and-traceability.md
```
を読む。
用語、context、暗黙conceptの発見が結果を分岐させるときだけ
```
skills/mino-core/references/domain-discovery.md
```
を読む。
filesystem、process、shell、toolchain、test実行、Windows / Linux / macOS差がEvidenceに関係するときだけ
```
skills/mino-core/references/platform-compatibility.md
```
を読み、platformごとの事実と未実行事項を分ける。
standalone依頼が複数の専門成果物、実装、独立検証まで求める場合は
```
$mino-reproducible-development
```
へ一度hand offする。
routerまたはpeer Skillからscoped artifactを依頼された場合は再routingせず、Problem Framing Packageと未解決obligationだけをcallerへ返す。
原則やschemaの出自を説明するときは、Context Packet、Selection Gate、restatement review schemaをsuite operationalizationとして扱う。

Internal paths are resolved using the installed
```
skills/
```
directory as the reference root, regardless of deployment location.
First read
```
skills/mino-core/references/core.md
```
and
```
skills/mino-core/references/shared-policies.md
```
; do not redefine common evidence, permissions, routing, or canonical decisions.
For standalone-specific deliverables and judgments, read
```
skills/mino-problem-framing/references/workflow.md
```
.
Only read
```
skills/mino-core/references/requirements-and-traceability.md
```
when normalizing requests passed to subsequent steps.
Only read
```
skills/mino-core/references/domain-discovery.md
```
when discovery of terminology, context, or implicit concepts branches results.
Only read
```
skills/mino-core/references/platform-compatibility.md
```
when filesystem, process, shell, toolchain, test execution, or Windows/Linux/macOS differences relate to evidence; separate platform-specific facts and unexecuted items.
If a standalone request requires multiple specialized deliverables, implementation, or independent validation, hand off to
```
$mino-reproducible-development
```
once.
If a scoped artifact is requested by a router or peer Skill, do not reroute; return only the Problem Framing Package and unresolved obligations to the caller.
When explaining the origin of principles or schemas, treat Context Packet, Selection Gate, and restatement review schema as suite operationalization.

Workflow

今回決めること、決めないこと、actor、owner、可逆性、変更境界について確認可能な項目を特定する。未確認項目は
```
unknown
```
または
```
contradiction
```
として保持する。
依頼原文、仕様、code、test、計測から観測と解釈を分ける。
結果を分岐させる重要語と前提だけを対象に、別解釈、識別Evidence、反証条件、誤り時の影響を監査する。
提示技術を
```
candidate_means
```
へ退避し、技術語なしでproblemを記述する。
```
つまり
```
で具体から目的へ遡り、
```
たとえば
```
で目的から成功・拒否・検証へ戻る。
Context PacketとAI restatementを作り、statement、comparison basis、proposed status、differences、review主体を分ける。
```
ready | conditional | blocked
```
を判定し、必要な次成果物とobligationだけを指定する。未作成artifact IDを作らない。

Identify items that can be confirmed regarding what will be decided, what will not be decided, actors, owners, reversibility, and change boundaries. Keep unconfirmed items as
```
unknown
```
or
```
contradiction
```
.
Separate observations from interpretations based on the original request, specifications, code, tests, and measurements.
Audit alternative interpretations, identifying evidence, falsification conditions, and impact of errors only for key terms and assumptions that branch results.
Save proposed technologies to
```
candidate_means
```
and describe the problem without technical jargon.
Trace from concrete details to objectives using "in other words", and return from objectives to success/rejection/validation using "for example".
Create a Context Packet and AI restatement, separating statements, comparison bases, proposed statuses, differences, and review subjects.
Determine
```
ready | conditional | blocked
```
, specifying only necessary next deliverables and obligations. Do not create unimplemented artifact IDs.

Platform Compatibility

OS名やshellをproblemの目的へ置き換えず、観測されたplatform差だけをenvironment Evidenceまたはconstraintへ置く。
一方のplatformの挙動から他方を推測しない。
runtime検証が必要だが行えない場合は、runner、command、oracle、未実行理由を残す。

Do not replace OS names or shells with problem objectives; only place observed platform differences into environment evidence or constraints.
Do not infer the behavior of one platform from another.
If runtime validation is necessary but cannot be performed, leave the runner, command, oracle, and reason for non-execution.

Hard Gates

以下のいずれかに該当する場合は、依存する設計・実装へ進まず、

conditional

または

blocked

として不足Evidenceと確認方法を返す。

actor、目的、観測可能な阻害要因、成功条件のいずれかが判定に必要なのに特定できない。
技術語を除くと問題を説明できない。
結果を分岐させる重要語・前提に、別解釈、識別Evidence、反証条件、または安全なSelection Gateがない。
具体Evidenceから目的へ遡るだけ、または目的から検証へ降りるだけの片道分析である。
新規能力なのに既存の構造原因を捏造する、または既存障害なのに因果調査を省略する。
人間所有の価値、業務上の意味、公開契約、不可逆なtrade-offをAIが確定する。
可逆性または既存問題 / 新規能力の区別が未確認なのに、
```
reversible
```
または確定済みcausal chainへ丸める。
schema、一般論、人物名、AIの自己説明だけでproblemを
```
ready
```
にする。

If any of the following apply, do not proceed to dependent design/implementation; return as

conditional

blocked

along with missing evidence and confirmation methods.

Any of the actor, objective, observable inhibitor, or success criteria required for judgment cannot be identified.
The problem cannot be explained without technical jargon.
Key terms/assumptions that branch results lack alternative interpretations, identifying evidence, falsification conditions, or a safe Selection Gate.
It is a one-way analysis that only traces from concrete evidence to objectives or only descends from objectives to validation.
Fabricating existing structural causes for new capabilities, or omitting causal investigation for existing failures.
AI finalizes human-owned values, business meanings, public contracts, or irreversible trade-offs.
Rounding to
```
reversible
```
or a confirmed causal chain without confirming reversibility or the distinction between existing problems/new capabilities.
Marking a problem as
```
ready
```
using only schemas, general theories, person names, or AI self-description.

Completion

problem、Context Packet、reasoning trace、AI restatementが同じactor、意味、目的、変更境界を保つ。
candidate meansは未選択のまま、目的、品質、制約、検証で比較可能である。
新規能力では未充足capability、既存問題では症状からrule / owner / 構造原因への因果をEvidence付きで扱う。
high-risk unknown、contradiction、未実行platform確認、人間判断を隠さない。
conditionalな選択は候補、predicate、Evidence取得、ownerを持つSelection Gateへ接続し、
```
pending
```
を選択済みと表現しない。
次のSkillへ渡す場合は必要artifactとobligationだけを指定し、未作成IDを捏造せず、canonical
```
decision
```
で現在のframing artifactを判定する。

The problem, Context Packet, reasoning trace, and AI restatement maintain the same actor, meaning, objective, and change boundary.
Candidate means remain unselected and are comparable in terms of objectives, quality, constraints, and validation.
For new capabilities, handle unmet capabilities; for existing problems, handle causality from symptoms to rules/owners/structural causes with evidence.
Do not hide high-risk unknowns, contradictions, unexecuted platform checks, or human judgments.
Conditional choices are connected to a Selection Gate with candidates, predicates, evidence acquisition, and owners; do not represent
```
pending
```
as selected.
When passing to the next Skill, specify only necessary artifacts and obligations; do not fabricate unimplemented IDs, and judge the current framing artifact with a canonical
```
decision
```
.