Brief import

By the end of this page you will have handed a client's brief to Heimdall, watched it come back as a queue of epics with their stories, requirements, business rules, use cases, glossary terms, personas, stakeholders, risks, assumptions and decisions, and accepted, edited, merged or rejected each one; you will also know what Heimdall reads before it drafts, how a story lands under its epic, what an accepted record remembers about its origin, what the import costs and what it announces.

A brief import is the fastest way from a client's words to a planning record. You give the minimum, a paragraph or the whole brief, and Heimdall does the expanding: it reads the brief against what the project already holds, drafts one suggestion per record a good analyst would write, quotes the passage each one came from, says how sure it is and why, names the records the brief repeats, and adds improvements, the gaps a project of this kind leaves open. Nothing is written to the project by the reading. You decide each suggestion on the review queue, and only an accepted suggestion becomes a record, through the same door the record's own page uses.

The page is Brief Import in the Plan group of the project sidebar. A client guest never sees it.

Before you beginCopy Anchor Link

A brief is plain text or Markdown, at least a paragraph and at most 60,000 characters, pasted or uploaded as a .txt or .md file of up to 2 MB. PDF and Word files join with the knowledge module; until then, paste their text.

Importing a briefCopy Anchor Link

All the fields of a suggestionCopy Anchor Link

What Heimdall reads and how it judgesCopy Anchor Link

Before it drafts, Heimdall is given the project's name and description, every record the project already holds by reference and title (epics, stories, requirements, rules, use cases, RAID items and decisions), the names of its terms, personas and stakeholders, the house stack, and the brief itself. It is told to draft from the brief and not from imagination; where it adds what any product of this kind needs, it says so in the rationale and lowers its confidence. It proposes at most sixty suggestions, the records before the improvements, and names a record of the project as a duplicate when a suggestion repeats it, so you merge instead of doubling. A brief that names another stack gets a decision suggestion recording the choice.

Confidence is how directly the brief supports a suggestion, shown as a percentage: green from 80, amber from 50, grey below. Why is Heimdall's one-line reason. Neither decides anything; they tell you where to look twice.

Where a batch standsCopy Anchor Link

A suggestion is Pending until you decide it, then Accepted, Accepted with edits, Merged, Rejected or, for a note, Dismissed. A decision is never undone: the record it wrote has its own lifecycle, and a merged or rejected suggestion stays on the batch for the record.

Convening the council on a batchCopy Anchor Link

Once a batch is Ready to review or Reviewed, people who may use Heimdall see Convene the Council in its header. Every voice the project seats on the intake scaffold reads the brief and what Heimdall drafted from it, with the decision so far on each row, and says what the drafts get wrong, what a project of this kind needs that neither the brief nor the drafts say, and what the client will be held to; a voice that can draft the missing record does, so accepting its finding writes the record. The Heimdall panel opens on its Council tab to show the sitting as it fills in, and the council page has the voices, the verdict and the cost.

What an accepted record remembersCopy Anchor Link

The record is written through its own create action, so it takes the next number of the project, passes the record's own rules, announces its own created event and starts its history with a first version. That version is written with the reason Imported, by Heimdall and accepted by you, and the activity log says the same, so anyone reading the record later knows where it came from. The suggestion keeps a link to the record, and the record's page shows the history like any other.

What happens nextCopy Anchor Link

• import.started goes out when the brief is handed over; import.ready or import.failed when the queue is done; import.discarded when a batch is dropped.
• import.suggestion_accepted, import.suggestion_rejected and import.suggestion_merged follow each decision, beside the created event of the record an accepted suggestion wrote.
• The reading is filed in the team's AI ledger under Brief imports and counts against the month's budget on Settings → AI; a batch at the cap fails before the model is asked, and Start Again works once the budget has room.
• The sidebar badge on Brief Import counts the batches still reading or waiting for review.
• The brief stays with the batch, so a second import of the same words can be read beside the first and what was already accepted or rejected can be told apart.

From the API and MCPCopy Anchor Link

There is no MCP tool for the review queue on purpose: a brief import spends the budget on a whole brief and fills a queue for people, and an agent never accepts a record on Heimdall's say-so. An agent reads the records people accepted through the planning tools like any other.

PermissionsCopy Anchor Link

Frequently askedCopy Anchor Link

Can I import a PDF or a Word document? Not yet: paste its text, or save it as .txt or .md and upload that. The knowledge module adds the two formats.

What if the brief is longer than 60,000 characters? Split it by topic and import each part; the second import sees the records the first one wrote and names them as duplicates.

Why does a story show no epic? It was accepted before its epic. Set the epic on the story's editor on the Backlog, or accept the epics first next time.

Can I undo an accept? No; delete the record on its own page if it should not exist. The suggestion keeps the link to the record it wrote.

Why did Heimdall propose a decision about the stack? The brief named a technology outside the house stack. Heimdall assumes the house stack unless the brief rules it out, and records the choice as a decision for you to confirm or reject.

Does the import run as me? Yes. The queue reads the brief with your permissions and meters the call to you, so the records Heimdall checks for duplicates are the ones you may see.

RelatedCopy Anchor Link

• Heimdall and the brief import — how the reader thinks and what it costs
• Heimdall research — the other way in: Heimdall reads the web for what the domain demands and leaves research and improvement notes on the project overview
• Epics, Backlog, Functional requirements, Non-functional requirements, Business rules, Use cases, RAID log, Decisions — where the records land
• Glossary, Personas, Stakeholders — the words and the people
• Quality review — read what Heimdall drafted with the same eyes a developer will
• Revisions and versions — the first version an accepted record starts with
• Status reference — batch and suggestion statuses, and the kinds