pendo-io/novus
Novus skills for coding agents: UX review and evidence-backed next-work and portfolio investment decisions, powered by Pendo product analytics.
Use when someone asks whether a shipped change, set of pull requests, launch, experiment, or feature worked, created customer value, should roll out further, should continue, or should be rolled back, including weekly engineering-impact or "code in the wild" reports.
Use when a leader asks whether engineering investment is going to the right goals or product areas, where to invest more or less, or needs a roadmap-versus-reality, planning-cycle, quarterly allocation, or post-ship portfolio review. Not for choosing one builder's next task or designing an experiment for an already selected outcome.
Reviews uncommitted or branch-local code changes for real UX problems before a PR is opened — wrong visual semantics, unpersisted UI state, poor discoverability, missing loading and error states, removal of well-used paths, redundant UI. Backs findings with Novus product analytics when the Novus MCP server is connected, and falls back to code-observable findings when it is not. Use when the user asks for a UX review, a design review, a pre-PR check, or whether their current changes will hurt users.
Use when a builder asks what to build next, whether to finish, continue, narrow, pause, or switch current engineering work, what to defer, or when an autonomous coding agent must steer among bounded work options. Not for team-level portfolio allocation or designing an experiment for an already selected outcome.