Engineering intelligence, built on institutional knowledge

The gap I kept running into

Engineering teams know more than they have written down. The reasoning behind a decision lives in a thread. A constraint exists only in one staff engineer’s head. An incident taught a hard lesson that nobody revisits. New engineers spend weeks reconstructing knowledge that already existed.

Why I built Prodigent

Prodigent is my answer to a simple idea: engineering knowledge shouldn’t disappear when the conversation ends. Capture and connect the knowledge surrounding engineering work — systems, decisions, constraints, solutions and people — and make it usable when it matters.

What we are building toward

• Deeper capture from existing tools

  Bring institutional knowledge in from Slack, issue trackers, and other systems engineers already use — without forcing a workflow change.

• Unstructured capture

  Let engineers describe something without deciding what type it is or where it belongs. Prodigent structures it into useful knowledge.

• MCP and agent access

  Access Prodigent’s institutional knowledge from the tools where you work — giving assistants access through MCP. Future direction, not shipped.

• Stronger capture loops

  Make questions, decisions, incidents, solutions, and runbooks strengthen what the organisation can understand over time.