Observer Agent connects to your GitHub repos and surfaces high-signal suggestions by cross-referencing design flows, coded flows, and codebase structure.
Suggestion types
- Missing glue — Backend feature exists, no UI exposed (e.g. API endpoint with no user-facing flow)
- Refactor / Consolidate — Overlapping flows or duplicate patterns across routes
- Expose feature — Capability in code not surfaced in design or main flows
- Debt reduction — Technical/UX debt that impacts flows
Observer Suggestions panel (Spec v4.5)
Each suggestion includes: Title (short, actionable), Type (e.g. missing_flow, refactor, expose_feature, debt_reduction), Evidence (linked flows/screens, file paths/routes, analytics if relevant), Description (why it matters), Proposed Action, Estimated Effort (low/medium/high), and optional related Blue Painter issue IDs.
Use Copy as Markdown to export rows matching your filters (status, type, effort, flow, search; each row includes status and Flow context when set). Filter chips: All, Open, Accepted, Rejected, Done. Type, Effort, and Flow context (including "No flow context") refine the list. Flow context is the first screen label from your latest completed analysis when Observer runs. Search matches title, description, flow, proposed action, and evidence. Each stored suggestion has a Workflow status control (after you Run Observer on a repo). Re-running Observer keeps status when the same type+title+flow context returns. Demo suggestions (no repo) are read-only for status.
How to use
Connect GitHub in Settings. In Project Settings, add repos under Connected Repositories and choose role per repo (frontend, backend, design-system, mobile). Click Run Observer Analysis on the project (or use scheduled batch). Open the Observer Suggestions tab to view, filter, and act on suggestions.
Optional: Expert Review experts can see Observer suggestions, endorse or down-rank them, add commentary, and include them in the action plan.