breakout_trade_execution_skill

Breakout Trade Execution Skill

Data Dependencies and Execution Prerequisites

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

# 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 turn "this stock may be about to break out" into an execution plan usable in real time. The output focus is not a general discussion of breakout patterns, but rather clarifying what to watch before the breakout, how to confirm during the breakout, how to follow up after the breakout, and how to retreat quickly once it fails.

Function Overview

The core function of this skill is: to develop a practical execution plan for breakout trading.

It emphasizes connecting structural judgment, volume confirmation, market environment, entry pacing, and failure correction, helping users turn chasing strength from an emotional action into a disciplined action.

Use Cases

• The user is preparing to do breakout following near a key resistance level.
• Before the market opens, candidate breakout stocks need to be written into specific execution plans.
• A rapid volume surge and upward push appears intraday, and a judgment is needed on whether to follow and how to follow.
• The team needs to unify the confirmation criteria and retreat rules for breakout trading.

Working Principles

1. Breakout execution must first distinguish between "approaching a breakout" and "valid breakout."
2. Price moving above a key level is only the beginning; volume absorption and environmental alignment are equally important.
3. Breakout trading must have a clear upper limit for chasing price and cannot chase indefinitely.
4. The failure retreat plan must be written down at the same time as the entry plan.
5. The main text outputs only the execution framework and does not discuss internal implementation details.

Execution Process

Step 1: Define the breakout structure and key levels

First clearly define the breakout target of this trade:

• Where the key resistance level or upper edge of the platform is
• Whether the current move is a box breakout, platform breakout, cup-with-handle breakout, or another release after consolidation
• Whether the structure is already mature enough or still relatively early
• Whether the current price is close to the trigger level, too far away, or has already been front-run

Step 2: Judge whether the environment supports chasing strength

The success rate of a breakout depends largely on the environment:

• Whether the index and sentiment allow high-level expansion
• Whether the sector has an obvious strong core
• Whether the market currently prefers following new highs or is more prone to spiking and then pulling back
• What the recent success rate of similar breakouts has been

If the environment does not support it, execution aggressiveness should be actively reduced.

Step 3: Set trigger conditions and confirmation levels

Break the breakout trigger down into more rigorous levels:

• Which price conditions must be met for an intraday trigger
• Whether synchronized confirmation such as volume expansion, turnover, and absorption is required
• If it gaps up directly past the key level, whether it is still an executable opportunity
• If it pulls back immediately after the breakout, when it is judged invalid

Step 4: Design entry pacing and price-chasing boundaries

The biggest fear in breakout trading is "chasing too late and retreating too slowly." It needs to be clarified in advance:

• Whether the first entry is made right at the trigger or after waiting for a pullback confirmation
• What price band for chasing is allowed and what the maximum deviation is
• Whether to complete it in one go or first verify with a small position
• If the first buy point is missed, is it permissible to wait for a second opportunity

Step 5: Establish post-position follow-up and add-on rules

Once executed, the next step must also be clearly written in advance:

• Which price action indicates the breakout is genuinely valid
• Which pullback is a healthy confirmation, and which decline is a danger signal
• Whether adding to the position after confirmation is permitted
• If it fails to hold steady by the close, is holding overnight still reasonable

Step 6: Design retreat actions for a failed breakout

The most critical thing in breakout trading is not how many successes you catch, but how few failures you take:

• How to handle it when it falls back below the key level
• Whether reducing the position is mandatory when a high-volume spike has no follow-through
• If it gaps down and loses the level the next day, what is the sequence of actions
• Whether keeping a small position to wait for a rebuild is permitted

Step 7: Form the final breakout execution draft

The final output should let the user know "when to act, to what extent not to chase, what to watch after the breakout, and how to retreat when it fails." The main text retains key levels, execution conditions, and retreat discipline.

Output structure

---

Breakout Trading Execution Plan ({YYYY-MM-DD})

I. 30-second conclusion

• Trading target: {stock name}
• Breakout type: {content}
• Environment fit: {high / medium / low}
• Execution bias: {actively follow / conditionally follow / do not chase for now}
• Maximum risk: {one sentence}

II. Breakout execution framework

Item	Content
Key level	{content}
Trigger condition	{content}
Confirmation signal	{content}
Entry pace	{content}
Chase limit	{content}
Failure boundary	{content}

III. Intraday and after-hours tracking

• Key intraday observations: {content}
• Closing confirmation point: {content}
• Next-day verification point: {content}

IV. Failure retreat plan

• {action 1}
• {action 2}
• {action 3}

V. Risk warnings

• {risk 1}
• {risk 2}
• {risk 3}

---

Quality requirements

1. It must clearly distinguish the three stages: before the breakout, during the breakout, and after the breakout.
2. Trigger conditions, chase boundaries, and failure boundaries must all be present at the same time.
3. When the environment does not support it, one must dare to give a no-chase conclusion.
4. Failure handling must be specific down to the sequence of actions.
5. The output should directly serve real live trading execution, rather than generalized technical commentary.