✨ Project Context - Allow per-project contextual profiles to improve sprint review analysis accuracy

[ssw-yakshaver]

Requested by: @suiyangqiu via YakShaver.ai 🦬
cc: @SamBWagner, @bradystroud, @suiyangqiu, @yaqi-lyu, @calumjs, @joshbermanssw

Hi Team!

  🟥  Watch the video (2 min 24 sec)

  Url from screen share: https://dashboards.sswtiiger.com/general/2026-04-16-101031

Pain

SSW.Tiger currently performs sprint review and risk analysis without sufficient understanding of the specific project context, which can result in misleading or low-value insights (e.g., calling out issues that are expected or intentionally discovered through Bench Masters reviews). Introduce a per-project context profile that allows teams to define background information, constraints, goals, and known realities of a project. This context should be automatically provided to the SSW.Tiger agent whenever it performs sprint review, risk radar, or similar analyses, enabling more accurate and relevant insights.

Acceptance Criteria

1. Users can create and edit a context profile for each project in SSW.Tiger
2. A project context profile supports free-text context such as project goals, team structure, known risks, and operating assumptions
3. The defined project context is automatically included in all sprint review, risk radar, and analysis prompts for that project
4. SSW.Tiger analysis output reflects awareness of the provided project context
5. Project context profiles are persisted and reused across multiple analyses
6. If no project context is defined, SSW.Tiger continues to function with existing default behavior

Screenshot

Figure: Risk radar flags 'silent drift' without project context

[bradystroud]

This is more valuable for non-sprint reviews, meetings that could still benefit from insights but are out of the ordinary e.g. Bench Masters meeting