Jira2w ago
Checkout rewrite epic — CHK-210
The scope and acceptance criteria.
See the full context behind any change.
A single feature spans the spec, the threads that shaped it, the tickets that scoped it, and the PRs that shipped it. Virgo assembles that connected history on demand. You start with the whole picture instead of reconstructing it tool by tool.
sourcesPR #214@postmortemPAY-211docs/payments
›
⏎ send · esc to interrupt
The context behind a feature is scattered across your tools
One checkout rewrite lives in the spec, the threads that shaped it, the tickets that scoped it, and the PRs that shipped it. To understand it, you open every tool and rebuild the picture by hand.
The scope
The decision
Slack1mo ago
#payments
Where idempotency keys were decided.
The prior attempt
GitHub3mo ago
An earlier attempt — PR #4827
What was tried before, and why it was reverted.
Understand the checkout rewrite
Every piece is here. It is just spread across six tools.
The spec
Google Docs4mo ago
Checkout spec
The original requirements.
The architecture
Confluence2mo ago
Payments architecture
How the service fits together.
The discussion
Google Meet3w ago
Sprint planning
Where the rewrite was scoped.
Ask once, and Virgo assembles the whole picture.
Virgo connects those same six tools into one reasoning graph. Ask it about the checkout rewrite and it queries every source, pulls the piece each one holds, and returns the connected context, instead of leaving you six tabs to reconcile by hand.
How context retrieval works
Behind one question, Virgo walks the reasoning graph and returns the connected context behind it, already assembled.
›
⏎ send · esc to interrupt
The same context pays off for people and agents
Assembled once, it serves the engineer reading the change and the agent acting on it.
For engineers
Understand a feature, including the reasoning behind it.
The spec, the discussion, the tickets, and the code arrive connected. You see how a change came to be and why it works the way it does before you touch it.
- What it is: the spec and the scope behind it.
- How it works: the code paths and the decisions that shaped them.
- Why it exists: the threads, tickets, and trade-offs on the record.
For AI agents
The agent reasons from the assembled context.
An agent handed a snippet writes against the snippet. Hand it the assembled context (the decision, the constraint, the reverted attempt) and it reasons about the real change. Virgo retrieves across the graph at query time, over MCP, so any agent works from the connected work history.
97%context retrieval accuracy
Up to 97% in early evaluations, versus about 68% for baseline RAG or hybrid search.