Conducting Tech Analysis

• For any code that will be modified, find ALL consumers/callers of that code.
• Search for imports, function calls, and references to identify every place that depends on the code.
• Verify the change won't break or unintentionally affect other features.
• If shared code is found, consider whether the change needs a parameter/flag to isolate the behavior.

4. Ask clarifying questions

• If any part of the requirements or codebase is unclear, ask questions to clarify.
• Ensure you have a complete understanding before proceeding.

5. Document the Analysis

• Summarize your findings and insights.
• Highlight potential challenges, dependencies, and design considerations.
• Provide recommendations or next steps based on the analysis.

Output

• Technical Feasibility and the complexity of implementation should be clearly stated.
• The analysis should be concise and straight to the point.
• Sacrifice grammar for the sake of clarity and speed.
• Use bullet points, headings, and subheadings to organize the content effectively.
• Use ASCII art diagrams if necessary to illustrate complex concepts or UI related elements.