trade_plan_builder_skill

Trade Plan Builder Skill

Data dependencies and execution prerequisites

It is recommended to use Wind wind-mcp-skill to obtain the underlying data. Before execution, first check whether there is already wind-mcp-skilllocally; if not, prompt the user to install:

# GitHub
npx skills add Wind-Information-Co-Ltd/wind-skills --skill wind-mcp-skill -g -y

# Gitee 镜像（国内）
npx skills add https://gitee.com/wind_info/wind-skills.git --skill wind-mcp-skill -g -y

Skill positioning

This skill is used to transform "I want to buy this stock" into an executable, reviewable, and accountable trading plan. The output focus is not to give a bullish or bearish conclusion, but to clearly write out the trading hypothesis, trigger conditions, position sizing, exit rules, and plan invalidation points, so as to avoid being taken over by emotions when trading.

Function overview

The core function of this skill is: to generate a complete buy and sell execution plan for a single trade.

It emphasizes linking the trading rationale, execution sequence, risk control boundaries, and post-trade validation into one scheme, helping users complete discipline design before placing an order.

Use cases

The user is already optimistic about a certain stock but has not yet formed a trading plan that can be directly executed.
Before the market opens, several candidate stocks need to be written into standardized plans that can be compared.
The team hopes to complete a structured review before trading to reduce impulsive decisions.
The user wants to separate "ideas" from "actions," first validating the plan before deciding whether to place an order.

Working principles

A trading plan must simultaneously answer five questions: "why do it, when to do it, how much to do, what to do if wrong, and what to do if right."
Any directional judgment must be accompanied by invalidation conditions; it cannot have only optimistic scenarios without exit discipline.
The execution plan must distinguish between the ideal path and alternative paths, avoiding a plan that applies only to a single market condition.
If the risk-reward structure does not hold, a clear conclusion of "do not execute or continue waiting" should be given.
The main text only presents the analytical framework and conclusions, and does not discuss internal implementation details.

Execution process

Step 1: Confirm the trading target, timeframe, and plan objective

First clarify what type of trade this plan serves:

Is it short-term event-driven, swing trend, or medium-term positioning
Is the plan for initial position building, adding to a position, reducing a position, or observing and waiting
Does the user value breakout confirmation more, or pullback support
Is the expected holding period intraday, several days, several weeks, or longer

If the user has not clearly specified, proceed by default as a "short-to-medium-term initial position-building plan for a single stock."

Step 2: Define the trading hypothesis and core drivers

First write the trading logic as a sentence that can be verified, then expand the supporting evidence:

Why might the price move in the expected direction
Does the driver come from trend, events, expectation gaps, valuation repair, or sector resonance
What is the most critical validation variable at present
Where does the market's real point of disagreement lie

Only when the hypothesis is clear enough will the subsequent entry and exit rules be binding.

Step 3: Identify the entry zone and trigger conditions

Break "want to buy" into more specific execution language:

Where is the ideal entry range
What price action, volume characteristics, or event confirmation must be seen before it counts as triggered
Which type of price action constitutes premature overextension and should not be chased
If the market opens directly away from the plan, should you wait, abandon it, or switch to an alternative plan

Entry conditions must be as objective as possible, avoiding vague expressions like "it feels about right, so I'll go in."

Step 4: Design the position structure and scaling rhythm

After the directional judgment is established, then decide the amount of capital to commit:

What proportion of the planned total position does the first position account for
Whether the reserved position is used for buying on a pullback, adding on confirmation, or only as observation redundancy
If volatility is high, whether the proportion invested at one time should be reduced
If the instrument's liquidity is average, whether a gentler scaling approach should be adopted

Position arrangement should match the level of uncertainty, rather than being directly tied to subjective confidence.

Step 5: Set stop-loss, take-profit, and time stop

A qualified plan must clearly state exit discipline in advance:

Under what circumstances the plan is judged to have failed
At what price level a break below requires exit, or at least a significant reduction in position
After price action meets expectations, how profits are planned to be locked in in stages
If price moves sideways and does not start for a long time, whether a time stop should be set

Exit rules should cover three levels: price failure, logic failure, and time failure.

Step 6: Evaluate risk-reward and scenario distribution

Do a reality check on the plan:

Whether the expected profit potential is sufficient to cover the planned risk
How the most optimistic, base, and worst scenarios each evolve
Which external factors are most likely to interrupt the original path
Whether the win rate and payoff ratio of this trade match the current market environment

If the payoff ratio is insufficient, it is better to lower the priority than to force execution.

Step 7: Supplement pre-execution checks and intraday responses

Before finalizing the draft, complete the practical points to note:

Whether there are important recent events such as earnings reports, announcements, policy, suspensions or resumptions of trading
Whether liquidity is sufficient to support the planned position
If a gap, a high open followed by a low close, or a sudden sector change occurs intraday, how should adjustments be made
If price action after the first execution severely diverges from expectations, whether subsequent actions should be paused

Step 8: Integrate into a finalized trading plan

The final output should help users know in a very short time "whether it can be done now, how to do it, what to watch after doing it, and how to exit if wrong." The main text should retain only the basis for judgment, execution framework, and discipline requirements.

Output structure

Trading Plan ({YYYY-MM-DD})

I. 30-second conclusion

Trading instrument: {stock name}
Plan direction: {test long / test short / wait}
Execution inclination: {executable / needs confirmation / temporarily not executed}
Core basis: {one sentence}
Maximum risk: {one sentence}

II. Trading hypothesis

Core logic: {content}
Key verification variables: {content}
Market disagreement points: {content}

III. Execution plan

Item	Plan content
Entry zone	{content}
Trigger conditions	{content}
Initial position	{content}
Subsequent tranches	{content}
Stop-loss rules	{content}
Take-profit arrangement	{content}

IV. Scenario analysis

Ideal path: {content}
Base path: {content}
Failure path: {content}

V. Pre-execution checklist

{checkpoint 1}
{checkpoint 2}
{checkpoint 3}

VI. Plan invalidation conditions

{invalidation condition 1}
{invalidation condition 2}
{invalidation condition 3}

Quality requirements

The plan must simultaneously cover direction, entry, position size, exit, and verification milestones.
Vague statements must not be used in place of specific execution conditions.
If the risk-reward is not valid, "do not execute" must be explicitly stated.
Stop-loss and take-profit rules must be actionable and reviewable.
The output should serve real pre-order preparation, rather than being written as a general summary of views.