novus

What novus does, in the publisher's words

From the project README, punctuation lightly normalized · Open the README on GitHub →

Links

• github.com/pendo-io/novus-plugin
• https://novus.pendo.io
• plugin.json (manifest)

Skills · 6

build-impact

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.

build-investment

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 experime…

usage-brief

Use when a builder wants to understand how much a product area is actually used today, and whether the PR or feature they are working on has potential to grow that usage, backed by real Pendo numbers. It leads with current usage, then reads the growth potential and the numbers that would show it w…

ux-review

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 MC…

verify-instrumentation

Use when a decision depends on Pendo/Novus behavioral data and you need to know whether the measured surface is instrumented well enough to trust, before starting work, before reading impact numbers, or as the measurement-trust sub-check for build-impact, build-investment, whats-next, or usage-bri…

whats-next

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 sele…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

MCP servers · 1

novusstreamable-http

https://novus-api.pendo.io/mcp

Read from the plugin's own mcp.json. We list environment variable names, never values.

Category

Code Review & Quality. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.

Keywords

pendo · novus · ux · code-review · product-analytics · planning · roadmap

Related by publisher and keywords

• dev-workflow-v2NTCoding

  Event-sourced workflow state machine for a structured task lifecycle.

• ai-improvecharlesjones-dev

  Audits a codebase across nine categories and writes self-contained implementation plans that another agent or a cheaper model can carry out, each with exact files, steps that end in a check, scope limits and STOP conditions. It also writes a plan from a description or from another audit's report, hands a plan to an executor in a separate git worktree and reviews the result, and keeps the plans up to date as the code changes. It never changes source code itself

• portable-agent-skillsrosslevinsky

  Agent workflow skills that behave the same in Claude Code and Codex CLI, with a portability contract enforced in CI.

• pepper-orchestratorITSalt

  Preview: one orchestrator session runs work across several repositories or parallel streams of one repository, plan, work packages, dispatch with worktrees and locks, PR review with a read-only reviewer agent, owner queue, closing a program when its goal is reached, state in files. Start with /pepper-orchestrator:init <program>, then /pepper-orchestrator:plan <task>.

• feature-workflowmark22013333

  功能開發工作流: 以.spec/ 做本地規劃，涵蓋需求、DB、架構、實作、驗證、審查與結案。

• fk-eng-agentsfurkankoykiran

  Four focused subagents, researcher, planner, code-reviewer, debugger, for deep codebase research, dependency-aware planning, pre-commit review, and root-cause debugging. Adds no skill-listing context cost.