Inline assists
Ask Heimdall beside any long field of an epic, story, requirement, rule, use case, RAID item, decision or dictionary entry: draft it, improve it, shorten it, make it testable or rewrite it as Given, When, Then, then take the draft or drop it.
By the end of this page you will have asked Heimdall to draft an empty field from a title, to sharpen a paragraph you wrote in a hurry, and to turn a requirement into steps a tester can tick, and you will know what Heimdall sees when it does, what it costs, and why nothing changes until you save.
An inline assist is one bounded rewrite of one field. Beside every long field of a planning record's editor, Ask Heimdall opens a short menu; pick an assist and the draft appears under the field, with a line on what Heimdall assumed or left open. Replace puts the draft in the field's place, Add Below keeps your words and adds the draft after them, Discard drops it. Nothing reaches the record until you save the form as you always do. The fields that offer it are the rich-text ones: an epic's summary, value and measures; a story's description and a bug's steps and results; a requirement's statement and rationale; a rule's statement and exceptions; a use case's conditions; a RAID item's description, mitigation and contingency; a decision's context, decision and consequences; a data entity's description; a glossary definition.
Before you begin
| You need | Where it comes from |
|---|---|
ai:use | The permission that opens Heimdall; the staff roles have it, a client guest never does. |
| Heimdall assists on | The project setting Heimdall assists in project settings, on by default. |
| Room in the month's budget | The team's AI budget under Settings → AI; an exhausted budget refuses the assist. |
Ask for a draft
- Open a record for editing, or press New on its page.
- Under the field, press Ask Heimdall and pick an assist. Draft it works on an empty field from the record's title; the other four need words in the field to work on.
- Wait a few seconds. The draft appears under the field with a Heimdall notes line when there is something you should know.
Take it or drop it
- Replace puts the draft in the field. Read it once more: Heimdall keeps every fact and reference it was given, but it cannot know what you left out.
- Add Below keeps your words and adds the draft after them, for a second scenario or an alternative you want to compare.
- Discard drops it; asking again gives a fresh draft.
Then save the form. Because a draft was taken into it, the version written is marked Drafted by Heimdall: Heimdall as the author of the words, you as the person who accepted them, and the activity row saying it came through an inline assist. A save with no draft taken is your own version, as before; opening another record forgets any draft you took and did not save.
The five assists
| Assist | What Heimdall does |
|---|---|
| Draft it | Writes a first version from the record's title, the facts it was given and the project's purpose; names every assumption in the notes. |
| Improve it | Keeps the meaning and sharpens the words: plain, specific, one idea per sentence, every fact and reference kept. |
| Shorten it | Says the same in roughly half the words, dropping repetition and hedging, never substance. |
| Make it testable | Replaces vague words with measurable ones and splits compound statements; an unknown measure becomes a placeholder named in the notes. |
| Given, When, Then | Rewrites the words as acceptance scenarios, each a short title with Given, When and Then lines, inventing no behaviour. |
What Heimdall sees
Only what the assist needs: the field's label and current words, what the record is and its title, the project's name, and a few facts the page adds (a decision's kind, for instance). It does not read the rest of the form, the record's history, other records or your conversation in the panel, and it holds no memory from one assist to the next. Every assist carries the house stack (Laravel and Livewire) so examples match how the team builds.
What it costs
Each assist is one model call, metered like a turn in the panel: the budget is checked before the call and the usage filed after it under the Inline assist feature of the usage statement. When the team crosses its warning line the owners are told; when the cap is reached the assist is refused until the month turns or the cap is raised.
Safety
- Heimdall writes nothing to the record. The draft lives under the field until you replace, add or discard it, and only your save writes a version; that version says Heimdall drafted it and you accepted it, so the record's history never hides where the words came from.
- The draft is sanitised to plain paragraphs, lists and emphasis before it is shown; a model cannot smuggle markup or links into a record.
- The call runs inside the same metering gate as every other model call in Zuse Bifrost: without the budget check and the usage line there is no way to the model.
- A provider that does not answer is reported as unavailable; nothing is filed and nothing changes.
Permissions
| Action | Permission |
|---|---|
| See Ask Heimdall | ai:use, on a project whose Heimdall assists setting is on; never a client guest |
| Take or drop a draft | The same; saving the record then needs its own update permission |
Frequently asked
Related
- The panel — Heimdall in conversation, with tools
- Usage and budgets — where each assist shows up
- Safety and permissions — what Heimdall may and may not do
- Project settings — the Heimdall assists switch
How is this guide?
Last updated on
Start a Project in Conversation
Tell Heimdall about a client and what they need; it creates the client and the project, writes the record as drafts, asks only for what it cannot infer, and convenes the council on the result inside the conversation.
Quality review
What Heimdall reads before it judges a record, how it grades and codes a finding, why the score is arithmetic, what a review costs and where it stops: it never writes to the record.