Evaluating user request

I should clarify what the user wants: a summary, analysis of fit, depth chart, or cap impact? It’s probably best to ask for the player's name since that will guide me. I might suggest a generic analysis template covering how an experienced guard fits with the Lakers’ needs—looking at roster gaps, shooting, defense, and playmaking. Offering scenarios for cap exceptions, like minimums or MLE, will help too. If they haven’t specified a player, I can provide a short general analysis.Drafting analysis options

I can offer to pull advanced stats like on-off and lineup net ratings if the user gives me the player's name or team from last season. I can also propose drafting a news post in three styles: quick news, in-depth analysis, or social media post, complete with placeholders. In the meantime, I’ll provide a quick generic analysis covering points like shooting volume, turnover rate under pressure, and how it affects minutes for Reaves and Russell, while suggesting rotation placeholders. I should keep the current roster details vague to avoid inaccuracies.Asking for details first

I want to ask the user for some specific details to tailor my analysis effectively. First, I’ll clarify which guard they’re referring to and gather information about the contract length and amount, if it’s officially announced or just rumors. I’ll offer several output options, like an instant news release, in-depth analysis on fit and data, salary cap impacts, social media copy, and outlines for shows or podcasts. If the user doesn’t have those details, I'll request the player’s name and recent stats and proceed with a typical template.