> For the complete documentation index, see [llms.txt](https://trnd-bot.gitbook.io/trnd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trnd-bot.gitbook.io/trnd/trnd-trainer/trading-plan/trading-plan-example.md).

# Trading Plan Example

**Objective**:

To achieve consistent profits in trading by following a set of predefined rules and strategies.

#### **Trading Details**:

* **Trading Style**: Swing Trading
* **Markets to Trade**: US Equities
* **Timeframe**: Daily charts

#### **Entry Criteria**:

1. Identify potential trade setups using **technical analysis**.
2. Look for stocks with a **clear trend** and **good trading volume**.
3. Use **support and resistance** levels to determine entry points (e.g., breakouts or pullbacks).
4. Confirm the entry using momentum indicators like **EQ Cloud** or **Momentum on TO Panel**.

#### **Stop Loss Criteria**:

1. Place the stop loss at a **predetermined level** based on technical analysis.
2. Adjust the stop loss based on **market volatility** and **price action**.

#### **Take Profit Criteria**:

1. Set **profit targets** based on a **risk-reward ratio** of at least **1:2**.
2. Use technical analysis to identify potential **resistance levels** as profit targets.
3. Move the stop loss to **breakeven** once the profit target is reached.

#### **Risk Management**:

1. Risk no more than **2% of account equity** per trade.
2. Determine **position sizing** based on the stop loss level and account equity.
3. Avoid trading during **high-impact news events**.

#### **Review and Analysis**:

1. **Daily Trade Review**: Identify strengths and weaknesses in the trading plan.
2. Maintain a **trading journal** to track trades, emotions, and overall performance.
3. Continuously **analyze and adjust** the trading plan as needed.

#### Few additional considerations you might want to incorporate into your trading plan:

1. **Market Research and Analysis**:
   * Regularly analyze market trends, news, and economic indicators.
   * Stay informed about sector-specific developments that could impact your chosen markets.
2. **Psychological Preparedness**:
   * Trading can be emotionally challenging. Develop strategies to manage stress, fear, and greed.
   * Set rules for handling losses and avoiding impulsive decisions.
3. **Contingency Plans**:
   * What if the market behaves unexpectedly? Have contingency plans for different scenarios.
   * Define exit strategies for adverse situations (e.g., sudden market crashes).
4. **Education and Learning**:
   * Continuously educate yourself about trading techniques, strategies, and market dynamics.
   * Attend webinars, read books, and follow reputable financial news sources.
5. **Adaptability**:
   * Markets evolve. Be open to adjusting your plan as needed based on changing conditions.
   * Learn from both successes and failures.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://trnd-bot.gitbook.io/trnd/trnd-trainer/trading-plan/trading-plan-example.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.