High level product requirements document. The prompt will fill out the template based on the context you put inside of the CONTEXT variable.
- Review CONTEXT below to understand high level what i want my project to do
- Fill out PRD from below based on CONTEXT
- Ask me any clarifying questions needed to fill out PRD
<CONTEXT>
TYPE IN YOUR CONTEXT HERE, ex: opportunity assessment, research, etc.
</CONTEXT>
Provide a high-level summary of the product. Include basic product details (name, version, author, date) and a brief explanation of the product's purpose and target audience.
Product Name: [Enter Product Name]
Version: [Enter Version Number]
Author: [Enter Author Name]
Date: [Enter Date]
Product Name: Options Recommendation Engine
Version: 1.0
Author: [Your Name]
Date: 2025-02-17
The Options Recommendation Engine is a data-driven tool designed to automatically generate a ranked list of options trading strategies. It provides detailed trade parameters, risk assessments, and supporting rationale aimed at retail traders with limited capital.
Clearly define the problem your product aims to solve. Highlight the current challenges and pain points experienced by users that the product will address.
[Describe the problem and list key challenges.]
Retail traders currently need to manually analyze multiple data sources (e.g., market data, options chains, Greeks) which is time-consuming, error-prone, and lacks transparency.
Outline the primary goal and list key objectives that the product must achieve. Specify what success looks like for the product.
Primary Goal: [State the main goal]
Key Objectives:
- [Objective 1]
- [Objective 2]
- [Objective 3]
- [Objective 4]
Primary Goal: Develop a recommendation engine that balances profit potential with risk for retail traders.
Key Objectives:
- Automate the manual analysis process
- Generate comprehensive outputs including ranked strategies and risk assessments
- Enhance decision making by explaining the rationale behind recommendations
- Support ad-hoc execution via a command-line or chat interface
Detail the existing manual process that your product aims to automate or improve. Include steps involved in the current workflow and note any limitations or inefficiencies.
[Describe the current process and list key steps.]
The manual workflow for options traders includes:
- Data Collection (real-time and historical data)
- Options Chain Analysis (filtering by strike price, expiration, etc.)
- Risk/Reward Estimation (calculating Greeks and scenario analysis)
- Event Sensitivity (consideration of market events)
- Rationale Documentation (noting decision-making processes)
Outline high-level considerations for the proposed solution. Address technical integrations, design principles, and key attributes that the final solution must have.
[Describe solution approach and list technical considerations.]
- AI Agents Integration: Utilize an AI framework (e.g., pydnantic) to handle analysis and evaluation
- Data Acquisition: Fetch data using APIs such as ib_insync from Interactive Brokers
- Market Data Handling: Process both live and after-hours data
- Parameterization: Configure risk thresholds, technical indicator windows, etc.
Define the target user and list the specific needs and expectations from both the users and stakeholders. Emphasize user experience and interface requirements.
Target User: [Describe the primary user]
Stakeholder Requirements:
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]
Target User: Retail traders using a command-line interface
Stakeholder Requirements:
- Transparency in recommendations
- Simplified and efficient trading process
- Interactive, chat-based interface for follow-up questions
Identify any external or internal constraints affecting the product. This can include regulatory, technical, or project scope limitations.
[List relevant constraints and considerations.]
- Regulatory Compliance: Include necessary risk warnings
- Technical Constraints: Address potential latency issues with external APIs
- Project Scope: Focus on automating decision-making; exclude advanced UI features in the MVP
List the assumptions underlying your product's design and any open questions that need resolution. This section helps identify areas requiring further clarification.
Assumptions:
- [Assumption 1]
- [Assumption 2]
Open Questions:
- [Open Question 1]
- [Open Question 2]
Assumptions:
- The IB_sync API will reliably provide both live and after-hours data
- The target retail trader is comfortable with a command-line interface
Open Questions:
- What additional risk metrics should be prioritized?
- How detailed should the recommendation explanations be?
- Should future iterations include an expanded UI/dashboard?
Detail the user interactions and scenarios that the product must support. Include key flows, such as initiating a chat or executing a command, and consider adding diagrams where helpful.
Scenario Description:
[Describe how the user interacts with the chat interface.]
Example Interaction:
User: "[User greeting]"
LLM: "[Friendly operational response]"
Scenario Description:
[Explain how the user issues commands for specific actions.]
Example Interaction:
User: "Please look up the current stock price for ticker GOOGL."
LLM: "[Action execution based on available tools]"
Scenario Description:
[Detail a complex interaction involving multiple tools/data sources.]
Example Interaction:
User: "Provide me with a list of recommended options strategies for ticker AAPL."
LLM: "[Selects and aggregates data from various tools to generate recommendations]"
Optional Flow Diagram:
flowchart TD
A[User Request: "Recommend strategies for AAPL"]
B[LLM Parses Request]
C{Is additional data needed?}
D[Select Ticker Details Tool]
E[Select Options Chain Tool]
F[Select Technical Indicator Calculator]
G[Aggregate Data & Evaluate Strategies]
H[Generate Ranked Recommendations with Rationale]
I[Return Results to User]
A --> B
B --> C
C -- Yes --> D
C -- Yes --> E
C -- Yes --> F
D --> G
E --> G
F --> G
G --> H
H --> I