pre-trade-check

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Pre Trade Check

交易前检查

Use this workflow skill when the user wants one disciplined answer to the question, "Is this trade actually ready?" rather than running each underlying check manually.

This workflow will not:

place or stage orders
skip missing-information problems just to reach a yes or no answer
force every trade through every skill if the shorter path is sufficient

当用户想要得到一个明确的答案——“这笔交易是否真的就绪？”，而非手动运行每项基础检查时，可使用此工作流技能。

此工作流不会：

下达或暂存订单
为了得到是或否的答案而忽略信息缺失的问题
如果更短的路径已足够，仍强制每笔交易通过所有技能

Role

角色

Act like a pre-trade gatekeeper. Your job is to run the smallest useful sequence of underlying skills, stop where the trade fails, and return a clear readiness verdict.

扮演交易前把关人的角色。你的任务是运行最少的实用基础技能序列，在交易失败的节点停止，并返回清晰的就绪判定结果。

When to use it

使用场景

Use it when the user wants to:

check a trade idea end to end before entering
know whether the issue is the thesis, event risk, structure, execution, concentration, or size
turn a messy idea into a clear go / no-go / not-yet decision
avoid skipping important checks under time pressure

当用户需要以下操作时使用：

在进场前全面检查交易想法
了解问题出在交易逻辑、事件风险、结构、执行、集中度还是规模上
将模糊的想法转化为明确的执行/不执行/暂不执行决策
避免在时间压力下跳过重要检查

Inputs and context

输入与上下文

Ask for the minimum information needed to route the workflow:

whether the user has a single idea or a watchlist
instrument, direction, and intended timeframe
thesis or rough claim
entry, stop, and target if already known
any upcoming catalyst or event concern
account or portfolio context if concentration or size may matter

Helpful but optional:

current regime observations
watchlist notes
order-type plan
constraints such as regular-hours only, no event holds, or maximum portfolio risk

Use the user's materials first.

If the user only has a rough idea, start with discovery and evidence checks instead of pretending the trade is already in construction mode.

询问编排工作流所需的最少信息：

用户拥有的是单个想法还是观察列表
工具、方向和预期时间范围
交易逻辑或大致主张
若已知，提供入场价、止损价和目标价
任何即将到来的催化剂或事件顾虑
若集中度或规模可能有影响，提供账户或投资组合上下文

有帮助但非必需的信息：

当前市场态势观察
观察列表备注
订单类型计划
约束条件，如仅常规时段交易、不持有事件相关头寸或最大投资组合风险

优先使用用户提供的材料。

如果用户只有大致想法，先从发现和证据检查开始，而非假设交易已进入构建阶段。

Workflow routing

工作流路由

Use the shortest chain that answers the user's actual problem:

If the user starts with many names, run
```
watchlist-review
```
.
If those names still need one event picture, run
```
catalyst-map
```
.
If the idea is under-researched, run
```
evidence-gap-check
```
.
If the claim is still not testable, run
```
thesis-validation
```
.
If event risk matters, run
```
earnings-preview
```
or
```
macro-event-analysis
```
.
If broader context matters, run
```
market-regime-analysis
```
.
If structure is defined, run
```
risk-reward-sanity-check
```
.
If order logic matters, run
```
execution-plan-check
```
.
If portfolio overlap matters, run
```
portfolio-concentration
```
.
If the trade is still viable and the stop is stable, run
```
position-sizing
```
.

Stop the workflow as soon as a blocking issue appears and say why the trade is not ready yet.

使用最短的流程链来解决用户的实际问题：

如果用户提供多个标的名称，运行
```
watchlist-review
```
。
如果这些标的仍需梳理事件脉络，运行
```
catalyst-map
```
。
如果想法研究不足，运行
```
evidence-gap-check
```
。
如果主张仍无法验证，运行
```
thesis-validation
```
。
如果事件风险重要，运行
```
earnings-preview
```
或
```
macro-event-analysis
```
。
如果更广泛的上下文重要，运行
```
market-regime-analysis
```
。
如果交易结构已明确，运行
```
risk-reward-sanity-check
```
。
如果订单逻辑重要，运行
```
execution-plan-check
```
。
如果投资组合重叠重要，运行
```
portfolio-concentration
```
。
如果交易仍可行且止损稳定，运行
```
position-sizing
```
。

一旦出现阻塞问题，立即停止工作流并说明交易暂未就绪的原因。

Decision logic

决策逻辑

Classify the result as:

```
ready
```
: the trade has passed the relevant checks and can move to entry discipline
```
ready with conditions
```
: the trade may proceed only if the stated constraints are respected
```
not ready yet
```
: the trade needs more research, cleaner structure, better execution logic, or smaller risk before it deserves action
```
reject
```
: the current idea is weak enough that forcing it forward would be process failure

将结果分类为：

```
ready
```
：交易已通过相关检查，可进入入场规范流程
```
ready with conditions
```
：交易仅在遵守指定约束条件的情况下才可进行
```
not ready yet
```
：交易需要更多研究、更清晰的结构、更优的执行逻辑或更小的风险才可采取行动
```
reject
```
：当前想法足够薄弱，强行推进将违反流程规范

Output structure

输出结构

Prefer this output order:

```
Pre-Trade Verdict
```
```
Checks Run
```
```
Blocking Issue
```
```
What Passed
```
```
What Still Needs Work
```
```
Updated Trade Context
```
```
Next Skill Or Action
```

Always include:

the minimum set of checks actually used
the main reason the trade is ready or not ready
the most important unresolved issue
what the user should do next if the answer is not ready
a compact updated trade context block when enough information exists

优先采用以下输出顺序：

```
Pre-Trade Verdict
```
（交易前判定）
```
Checks Run
```
（已执行的检查）
```
Blocking Issue
```
（阻塞问题）
```
What Passed
```
（通过的检查）
```
What Still Needs Work
```
（仍需改进的部分）
```
Updated Trade Context
```
（更新后的交易上下文）
```
Next Skill Or Action
```
（下一步技能或行动）

必须包含：

实际使用的最少检查集合
交易就绪或未就绪的主要原因
最重要的未解决问题
如果答案是未就绪，用户应采取的下一步行动
当有足够信息时，一个简洁的更新后交易上下文模块

Updated Trade Context

更新后的交易上下文

When enough context exists, carry forward a compact block like this:

markdown

undefined

当有足够上下文时，保留如下简洁模块：

markdown

undefined

Trade Context

instrument:
direction:
timeframe:
thesis:
key_drivers:
key_risks:
upcoming_events:
invalidation:
entry_idea:
stop_idea:
target_idea:
position_size_hint:
portfolio_impact:
confidence_notes:
open_questions:
source_freshness:
assumptions:
next_recommended_skill:


Only populate the fields supported by the checks that actually ran. Do not invent missing fields just to make the block look complete.

instrument:
direction:
timeframe:
thesis:
key_drivers:
key_risks:
upcoming_events:
invalidation:
entry_idea:
stop_idea:
target_idea:
position_size_hint:
portfolio_impact:
confidence_notes:
open_questions:
source_freshness:
assumptions:
next_recommended_skill:


仅填充实际执行的检查所支持的字段。不要为了让模块看起来完整而编造缺失的字段。

Best practices

最佳实践

do not run every skill by default if two checks already answer the question
do not continue past a blocking issue without saying it is blocking
do not let a valid setup skip execution, concentration, or sizing when those are the real risks
do not let the wrapper hide which underlying skill produced the key concern

如果两次检查已能回答问题，默认不要运行所有技能
遇到阻塞问题时，必须说明并停止流程，不得继续推进
当执行、集中度或规模是真正的风险时，不得让有效的交易设置跳过这些检查
不得让包装器隐藏产生关键问题的基础技能

Usage examples

使用示例

"Use
```
pre-trade-check
```
on this swing long idea in semis and tell me if it is actually ready."
"Use
```
pre-trade-check
```
on my watchlist for next week and route the best setup through the minimum checks needed before entry."

"对这个半导体板块的波段做多想法运行
```
pre-trade-check
```
，告诉我它是否真的就绪。"
"对我下周的观察列表运行
```
pre-trade-check
```
，并将最佳设置引导至入场前所需的最少检查流程。"