Data Dependencies and Execution Prerequisites
It is recommended to use Wind wind-mcp-skill to obtain the 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 live trading. The output focus is not a general discussion of breakout patterns, but rather clarifying what to watch before the breakout, how to confirm it at the moment of breakout, how to follow up after the breakout, and how to retreat quickly once it fails.
Feature 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 follow a breakout near a key resistance level.
- Before the market opens, candidate breakout stocks need to be written into specific execution plans.
- During intraday trading, a rapid volume-driven surge appears, and it is necessary to judge whether to follow and how to follow.
- The team needs to unify the confirmation criteria and retreat rules for breakout trading.
Working Principles
- Breakout execution must first distinguish between “approaching a breakout” and “an effective breakout.”
- Price moving above a key level is only the beginning; volume absorption and environmental alignment are equally important.
- Breakout trading must have a clear upper limit for chasing price; one cannot chase indefinitely.
- The failed-trade retreat plan must be written at the same time as the entry plan.
- 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 is the key resistance level or the upper edge of the platform
- Is the current setup a box breakout, platform breakout, cup-with-handle breakout, or some other release after consolidation
- Is the structure mature enough, or is it still relatively early
- Is the current price close to the trigger level, too far, or already overextended in advance
Step 2: Judge whether the environment supports chasing strength
The success rate of a breakout depends to a large extent on the environment:
- Do the index and sentiment allow high-level expansion
- Is there an obvious strong core in the sector
- Does the market currently favor following new highs, or is it more prone to spiking and pulling back
- How successful have similar breakouts been recently
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:
- What price conditions must be met for an intraday trigger
- Is simultaneous confirmation from volume expansion, turnover, and absorption needed
- If it gaps up and directly crosses the key level, is it still an executable opportunity
- If it pulls back immediately after the breakout, when is it judged invalid
Step 4: Design entry pacing and price-chasing boundaries
Breakout trading fears most “chasing too late and retreating too slowly.” It is necessary to clarify in advance:
- Should the first position enter right at the trigger, or wait for a pullback confirmation
- What is the allowable price band for chasing and the maximum deviation
- Should it be completed in one go, or must it first be verified 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 written clearly 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 firm by the end of the day, 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 price falls back below the key level
- If there is no follow-through after a high-volume surge, must the position be reduced
- 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 action can be taken, to what extent one should not 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 price upper limit | {content} |
| Failure boundary | {content} |
III. Intraday and after-hours tracking
- Key intraday observations: {content}
- End-of-day 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
- It is necessary to clearly distinguish the three stages: before breakout, during breakout, and after breakout.
- Trigger conditions, chase price boundaries, and failure boundaries must all be present at the same time.
- When the environment does not support it, one must be willing to give a do-not-chase conclusion.
- Failure handling must be specific down to the sequence of actions.
- The output should directly serve real live trading execution, rather than generalized technical commentary.