01
Research the accounts
Accounts · leads · deals
Brain
Al
Byerley
Supernova's agents
Specific jobs for AI. Review stays with your team.
Supernova brings project documents, client conversations and delivery plans into one workspace. AI agents use those records to draft specifications, plans and updates for your team to review. The roster contains 48 available agents and 1 retired agent. Explore what each reads and produces below.
An example of the work
48 available agents. People review the results.
- 01
Responsible for this step
Jane
Jane drafts the proposal.
Jane reads a discovery-call transcript and drafts the proposed scope, effort and milestones. A person reviews the proposal before sharing it with the client.
What you get
The team has a proposal to review.
- 02
Responsible for this step
Tony
Tony extracts the agreed scope.
Tony reads proposals and signed agreements to identify product areas and requirements. The technical lead checks the extracted scope against the documents.
What you get
The agreed work becomes a structured starting point.
- 03
Responsible for this step
Andrew
Andrew describes the users.
Andrew uses the client documents and product requirements to describe the people using the product, their needs and responsibilities.
What you get
The team can check who each feature serves.
- 04
Responsible for this step
Powell
Powell checks a use case.
A separate agent, Elvex, drafts use cases. Powell compares those drafts with their source documents and flags unsupported claims or scope gaps. This check supports the human review; it does not guarantee correctness.
What you get
The reviewer can see what needs attention.
- 05
Responsible for this step
Reviewer
A person approves the plan.
The reviewer can approve, return or correct a draft. Project review records show the decision so the team can see what was accepted and by whom.
What you get
The team knows which plan it can use.
Two teams of available agents
Support for sales and delivery.
Sales agents help research customers and draft proposals. Delivery agents help turn agreed requirements into plans, designs and tests. Both use the project records available to them.
The deal desk
11Sales agents
Research the accountPrepare the dayRead the dealDraft the replyAnswer in contextWrite the proposal
The delivery floor
37Delivery agents
Extract the scopeMap the interfacesModel the dataWrite the storiesPlan the buildVerify the result
The operating map
Examples of where agents help.
These examples group selected agents by job. They are not a fixed sequence or the full roster; a project uses the steps it needs.
Example Sales workflow · 9 agents
Research the accounts, sum up the day, then turn what the company knows into a next step.
02
Sum up the day
Briefing · scrum
Multivac
Nestor
03
Turn context into action
Reply · proposal · answers
Cal
Jane
Norby
Sammy
01
Defined jobs
Each agent has a specific task, such as drafting a proposal or checking a use case.
02
Controlled access
Agent tools use access checks. Ask about the permissions configured for your team.
03
Structured results
Generated plans have expected fields so teams can review and reuse them.
04
Human review
Review generated work before accepting it or sharing it with a client.
05
Run limits
Generation limits help stop work that runs too long or returns incomplete results.
06
Review history
Run and approval records help teams inspect how a result was produced.
The complete roster
Find an agent by the job you need.
Search by name, job, input or output. Counts include retired agents, which are labelled separately.
49shown of 49
Seldon
AvailableDiscover features from code
- Reads
- Stored source code and complete call chains
- Produces
- Use-case names, detailed descriptions and source references
Technical name and naming reference
create-code-use-cases
Named after Hari Seldon — Foundation.
Dors
AvailableExplain an implemented feature in detail
- Reads
- One use case and its complete source evidence
- Produces
- A detailed use-case description and named user stories
Technical name and naming reference
decorate-code-use-case
Named after Dors Venabili — Prelude to Foundation.
Daneel
AvailableDefine user permissions
- Reads
- Reviewed user types, use cases and product areas
- Produces
- Suggested roles and what each role can do
Technical name and naming reference
generate-roles
Named after R. Daneel Olivaw — The Caves of Steel.
Andrew
AvailableDescribe the people using the product
- Reads
- Client documents and reviewed product requirements
- Produces
- User profiles with needs and responsibilities
Technical name and naming reference
generate-personas
Named after Andrew Martin — The Bicentennial Man.
Cutie
AvailableMap the product data
- Reads
- Reviewed use cases
- Produces
- Data entities, fields and relationships
Technical name and naming reference
generate-ontology
Named after QT-1 — Reason.
Elvex
AvailableDescribe how features should work
- Reads
- The agreed scope of work
- Produces
- Use-case drafts with steps, rules and exceptions
Technical name and naming reference
generate-use-cases
Named after Elvex — Robot Dreams.
Speedy
AvailableMap user journeys
- Reads
- Use cases and shared screens
- Produces
- Step-by-step paths through the product
Technical name and naming reference
generate-journeys
Named after SPD-13 — Runaround.
Tony
AvailableExtract the agreed product scope
- Reads
- Proposals and signed agreements
- Produces
- Product areas, scope items and design requirements
Technical name and naming reference
generate-interfaces
Named after TN-3 — Satisfaction Guaranteed.
Robbie
AvailableBreak requirements into stories
- Reads
- Detailed use cases
- Produces
- User stories for the delivery backlog
Technical name and naming reference
generate-backlog
Named after Robbie — Robbie.
Dave
AvailablePlan developer tasks
- Reads
- Stories and the product data model
- Produces
- An ordered task plan with dependencies
Technical name and naming reference
generate-dev-tasks
Named after DV-5 — Catch That Rabbit.
Herbie
AvailableAnswer questions about a project plan
- Reads
- A question and the current project records
- Produces
- An answer or a suggested change for review
Technical name and naming reference
analyze-ask-plan
Named after HRB-34 — Liar!.
Giskard
AvailablePropose changes from feedback
- Reads
- Reviewer feedback and existing plans
- Produces
- Suggested edits for a person to confirm
Technical name and naming reference
analyze-cascade-feedback
Named after R. Giskard Reventlov — Robots and Empire.
Calvin
RetiredClassify scope for estimation (retired)
- Reads
- A scope document
- Produces
- Formerly produced effort categories; replaced by Baley
Technical name and naming reference
estimate-scope
Named after Susan Calvin — I, Robot.
Baley
AvailableMatch scope to known features
- Reads
- A scope document and the feature catalogue
- Produces
- Feature matches and unmatched requirements
Technical name and naming reference
match-features
Named after Elijah Baley — Mirror Image.
Bogert
AvailableFind unanswered scope questions
- Reads
- A scope matched to the feature catalogue
- Produces
- Questions about missing requirements and quantities
Technical name and naming reference
interrogate-scope
Named after Peter Bogert — Liar!, Little Lost Robot.
Easy
AvailableExtract project milestones
- Reads
- Project documents
- Produces
- Proposed milestones with source excerpts
Technical name and naming reference
extract-milestones
Named after EZ-27 — Galley Slave.
Bard
AvailablePrepare project kickoff documents
- Reads
- Sales-to-delivery handoff records
- Produces
- Draft kickoff slides, requirements and a project plan
Technical name and naming reference
generate-handoff-artifacts
Named after The Bard — Someday.
Lenny
AvailablePrepare a review knowledge check
- Reads
- The current project planning stage
- Produces
- Questions for the technical lead before approval
Technical name and naming reference
generate-stage-quiz
Named after LNE — Lenny.
Brain
AvailableResearch a client account
- Reads
- Available company records about the account
- Produces
- An account summary
Technical name and naming reference
antino3-accounts
Named after The Brain — Escape!.
Al
AvailableResearch a potential customer
- Reads
- Available records about a lead
- Produces
- A lead research summary
Technical name and naming reference
lead-research
Named after AL-76 — Robot AL-76 Goes Astray.
Byerley
AvailableReview a sales opportunity
- Reads
- Deal records and conversations
- Produces
- Deal status, decision makers, concerns and next steps
Technical name and naming reference
deal-research
Named after Stephen Byerley — Evidence.
Sammy
AvailableAnswer a question about a deal
- Reads
- The question, deal history, emails and notes
- Produces
- An answer based on that deal’s records
Technical name and naming reference
deal-chat
Named after Sammy — The Caves of Steel.
Multivac
AvailablePrepare a salesperson’s daily briefing
- Reads
- Commitments, deals and meetings
- Produces
- A daily summary and action list
Technical name and naming reference
antino3-home
Named after Multivac — The Last Question.
Nestor
AvailableSummarise daily team calls
- Reads
- Recorded daily team meetings
- Produces
- One combined summary
Technical name and naming reference
scrum-digest
Named after NS-2 — Little Lost Robot.
Cal
AvailableDraft a follow-up reply
- Reads
- An existing email conversation
- Produces
- A reply draft for review
Technical name and naming reference
draft-writer
Named after Cal — Cal.
Jane
AvailableDraft a client proposal
- Reads
- A discovery-call transcript
- Produces
- Proposed scope, effort, milestones and presentation
Technical name and naming reference
generate-proposal
Named after JN-5 — Feminine Intuition.
Susan
AvailableWrite a project case study
- Reads
- Completed project records and work logs
- Produces
- A client-facing case-study draft
Technical name and naming reference
generate-case-study
Named after Susan Calvin — I, Robot.
Norby
AvailableAnswer questions from company records
- Reads
- A question and available account or project records
- Produces
- A contextual answer
Technical name and naming reference
ask-antino
Named after Norby — Norby, the Mixed-Up Robot.
Max
AvailableSuggest a visual direction
- Reads
- Client moodboards
- Produces
- Proposed design choices based on the references
Technical name and naming reference
generate-design-from-moodboard
Named after Max — Light Verse.
Madarian
AvailableBuild design guidelines
- Reads
- Brand references and approved design choices
- Produces
- Colours, typography, components and usage patterns
Technical name and naming reference
generate-design-system
Named after Madarian — Feminine Intuition.
Donovan
AvailablePropose lessons from review corrections
- Reads
- Corrections to the checking agent’s findings
- Produces
- A suggested checking rule for approval
Technical name and naming reference
distill-lessons
Named after Mike Donovan — Runaround, Reason, Catch That Rabbit.
Powell
AvailableCheck a generated use case
- Reads
- The use case and its source documents
- Produces
- Findings about unsupported claims and scope gaps
Technical name and naming reference
verify-artifact
Named after Gregory Powell — Runaround, Reason, Catch That Rabbit, Liar!.
Jander
AvailableCreate a clickable prototype
- Reads
- Screens, approved components, data and roles
- Produces
- A prototype for a client workshop
Technical name and naming reference
generate-mock
Named after R. Jander Panell — The Robots of Dawn.
Mentor
AvailableExplain how similar work was delivered
- Reads
- Records from completed projects
- Produces
- A suggested method for building a capability again
Technical name and naming reference
capability-precedent
Named after The Mentors — the Norby Chronicles.
George
AvailableDraft test cases
- Reads
- A story’s acceptance criteria
- Produces
- Test cases describing expected behaviour
Technical name and naming reference
generate-test-cases
Named after The JG series — “…That Thou Art Mindful of Him”.
Black
AvailableRun tests and report failures
- Reads
- Test cases and an application to test
- Produces
- Test results and bug reports
Technical name and naming reference
execute-test-cases
Named after Gerald Black — Little Lost Robot, Risk.
Lanning
AvailableRevise part of a case study
- Reads
- One case-study section and editing instructions
- Produces
- A revised section
Technical name and naming reference
edit-case-study-block
Named after Alfred Lanning — I, Robot.
Rodney
AvailableDraft a first contact message
- Reads
- Research about a new lead
- Produces
- An outreach draft for review
Technical name and naming reference
lead-draft-writer
Named after Rodney — Christmas Without Rodney.
Kallner
AvailableIdentify plans affected by a change
- Reads
- A change and related project records
- Produces
- Suggested items for a reviewer to inspect
Technical name and naming reference
cascade-judge
Named after Kallner — Feminine Intuition.
Urth
AvailableGroup reviewer notes
- Reads
- A round of project feedback
- Produces
- Suggested groups and order for applying changes
Technical name and naming reference
cascade-seeder
Named after Dr Wendell Urth — the Wendell Urth mysteries.
Ebling
AvailableBuilds the product vocabulary from the code's own identifiers, and groups the candidate terms so a human can accept or reject a lexicon rather than a word list.
- Reads
- See the agent’s workflow for required project records.
- Produces
- See the agent’s workflow for its result and review requirements.
Technical name and naming reference
code-vocabulary-agent
Named after Ebling Mis — Foundation and Empire.
Arkady
AvailableSweeps a whole indexed repository for product capabilities, then consolidates the per-area findings into one non-overlapping candidate set.
- Reads
- See the agent’s workflow for required project records.
- Produces
- See the agent’s workflow for its result and review requirements.
Technical name and naming reference
project-code-discovery
Named after Arkady Darell — Second Foundation.
Gaal
AvailableFrames raw code findings as product use cases — the step from what the repository contains to what the product does.
- Reads
- See the agent’s workflow for required project records.
- Produces
- See the agent’s workflow for its result and review requirements.
Technical name and naming reference
frame-project-use-cases
Named after Gaal Dornick — Foundation.
Yugo
AvailableExpands a code-backed use case along its complete call chains — the body pass, the scenario pass and the review pass that checks each against the source it claims.
- Reads
- See the agent’s workflow for required project records.
- Produces
- See the agent’s workflow for its result and review requirements.
Technical name and naming reference
code-use-case-expansion
Named after Yugo Amaryl — Prelude to Foundation.
Fastolfe
AvailableWorks one exact operation at a time in four phases — create, decorate, verify, repair — so a claim about the code is checked and mended rather than restated.
- Reads
- See the agent’s workflow for required project records.
- Produces
- See the agent’s workflow for its result and review requirements.
Technical name and naming reference
code-operation-agent
Named after Dr Han Fastolfe — The Robots of Dawn.
Pelorat
AvailableWrites the product-level description of a code area from its stored symbols and chains, preserving the prose a human has already approved.
- Reads
- See the agent’s workflow for required project records.
- Produces
- See the agent’s workflow for its result and review requirements.
Technical name and naming reference
code-product-agent
Named after Janov Pelorat — Foundation's Edge.
Bayta
AvailableNames one cluster of resolved call chains from the evidence in the cluster itself — a feature-level label a person can recognise.
- Reads
- See the agent’s workflow for required project records.
- Produces
- See the agent’s workflow for its result and review requirements.
Technical name and naming reference
name-call-chain-cluster
Named after Bayta Darell — Foundation and Empire.
Hardin
AvailableTurns a complete call-chain cluster into detailed user stories, each citing the chains that evidence it.
- Reads
- See the agent’s workflow for required project records.
- Produces
- See the agent’s workflow for its result and review requirements.
Technical name and naming reference
extract-cluster-stories
Named after Salvor Hardin — Foundation.
Vasilia
AvailableReviews generated code against the story it claims to implement, binding each review to the exact output it read.
- Reads
- See the agent’s workflow for required project records.
- Produces
- See the agent’s workflow for its result and review requirements.
Technical name and naming reference
review-code-generation
Named after Dr Vasilia Aliena — Robots and Empire.
The important part
Review the work before using it.
AI output can contain mistakes. Use the source records, checking results and your team’s review process to decide what to accept.