SuperAPI AI Directory

trade_plan_builder_skill

General & other

View repository

Updated 10-16 09:55

About this 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 a local wind-mcp-skill; 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 directly executable trading plan.
  • 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

  1. 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 how to handle it if right."
  2. Any directional judgment must be accompanied by invalidation conditions; it cannot have only optimistic scenarios without exit discipline.
  3. The execution plan must distinguish between the ideal path and alternative paths, avoiding a plan that applies to only a single market condition.
  4. If the risk-reward structure does not hold, a clear conclusion of "do not execute or continue waiting" should be given.
  5. 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:

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

If the user has not clearly specified, proceed by default with "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 basis:

  • Why the price may move in the expected direction
  • Whether the driver comes from trend, events, expectation gaps, valuation repair, or sector resonance
  • What the most critical validation variable currently is
  • Where the market's real point of disagreement lies

Only when the hypothesis is clear enough do the subsequent entry and exit rules have binding force.

Step 3: Identify the entry zone and trigger conditions

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

  • Where the ideal entry range is
  • What price action, volume characteristics, or event confirmation must be seen to count as a trigger
  • Which entry approach constitutes premature overextension and should not be chased
  • If the market opens directly deviating from the plan, should you wait, abandon, 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 size of commitment:

  • What proportion of the total planned position does the first tranche represent
  • Whether the reserved position is used for pullback absorption, confirmation add-ons, or merely as observational redundancy
  • If volatility is high, whether the single-commitment proportion should be reduced
  • If the instrument's liquidity is average, whether a more gradual 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 write out exit discipline in advance:

  • Under what circumstances the plan is judged to be invalid
  • At what price level a break below must trigger exit, or at least a significant reduction in position
  • After the trend meets expectations, how profits are planned to be locked in tranches
  • If the price moves sideways and fails to launch for a long time, whether a time stop is set

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

Step 6: Assess 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 intended path
  • Whether the trade's win rate and payoff ratio match in the current market environment

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

Step 7: Supplement pre-execution checks and intraday response

Before finalizing the draft, fill in the practical operational points:

  • Whether there are important recent events such as earnings, announcements, policy, or trading suspensions/resumptions
  • Whether liquidity is sufficient to support the planned position
  • If a gap, high open then low close, or sharp sector change occurs intraday, how to adjust
  • If the trend after the first execution seriously deviates from expectations, whether to pause subsequent actions

Step 8: Integrate into a finalized trading plan

The final output should help the user know in an extremely 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 target: {stock name}
  • Plan direction: {test long / test short / wait}
  • Execution inclination: {executable / need confirmation / not execute for now}
  • Core basis: {one sentence}
  • Biggest 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 condition {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. Conditions for plan invalidation

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

Quality requirements

  1. The plan must cover direction, entry, position sizing, exit, and validation checkpoints simultaneously.
  2. Vague statements must not be used in place of specific execution conditions.
  3. If the risk-reward does not hold, "do not execute" must be explicitly stated.
  4. Stop-loss and take-profit rules must be actionable and reviewable.
  5. The output should serve real pre-order preparation, rather than being written as a general summary of views.