Insights

Insights answer system questions that are hard to check by hand: what has no fallback, what everything depends on, and what has become a single point of failure. An analysis walks the board and anchors insights to the elements they concern.

What an insight is

An insight is the result of running an insight skill over a board's scope. Each run produces a batch of insights anchored to the nodes and edges they concern. A batch is a grouping key, not a separate title or report.

That anchoring makes insights part of the board instead of a separate report. Open an element to see its insight. A batch has no narrative of its own. For a batch from chat, the conversation provides the narrative; after a plugin push, the insights stand on their own. Insight Skills covers authoring skills.

The four signals

Every insight has a signal that says what kind of thing it is:

Strengths matter because they show what to protect when you refactor.

How an analysis starts

Start an analysis from chat, /insights in a repo, or /discover. The plugins' graph-first /discover pass files its insights under the Architecture Highlights skill and draws context boards beside them. There is no Run button on the canvas.

/insights runs inside your coding session and needs no model provider. Chat runs in the portal, on trial credits or a connected model provider. Both publish a batch of insights to the same board.

The Insights Bar

The Insights Bar lists a board's own insights, plus how many continue below it in the tree. It does not start an analysis. Open an insight to read it. On a command center, the hub's Insights card is the rollup view across the whole tree, newest analysis first.

Expand

1. 1

   Traced paths

   A route the analysis followed through the architecture — an insight's own trail, shown alongside it rather than filed separately.

2. 2

   Signal, priority, and confidence

   Opening an insight shows its signal, priority, and confidence in the header.

Reading an insight

The Insights Bar groups a board's insights by how they relate to the board you're viewing: ones whose trail starts here, and ones that only run through it from elsewhere.

An insight can include two supporting details.

Suggested graph changes are structural proposals with reasoning attached. Traced paths show routes the analysis followed, such as a request path, blast radius, or dependency chain.

From an insight to an intent

An insight you agree with should become work. Create an intent from it so a developer can pull it into the repo with the analysis attached.

Each insight has an inline coverage chip showing where delivery stands: No intent yet, In delivery, Delivered, or Needs attention. You see the delivery state next to the insight that raised the work.

Review status

Every insight carries its own review status, not a shared one for the batch it arrived in: Draft, Ready, In Review, Approved, then Published or Archived. Insight Skills explains what each state means.

Where to go next