Prompting Panel
The slash command composer that drafts issues, sprints and documents for your review
The composer in Elixion, the platform for Engineering Intelligence™, turns a sentence into trackable work: issues, epics, sprints, milestones and documents. It is not a chat window. It generates a set of artifacts, shows you exactly what they would be, and writes nothing until you tick the ones you want.
Opening it
| Route | How |
|-------|-----|
| Keyboard | Cmd+J or Ctrl+J from anywhere in the app |
| Sidebar | Prompting, under AI Workspace |
| Command palette | Cmd+K, then the Ask Elixion AI row |
| From a search | Cmd+K, type something, then Ask AI about "...", which carries the text over |
| From an issue | The assist on an issue's page, which preselects /task and that issue as the parent |
Writing a prompt
The box reads "Describe what you want built. Type / for a command."
Type a leading / and the command palette opens under the box and filters as you type. Enter or Tab takes the highlighted command; Escape dismisses it without choosing. The chosen command appears as a pill above the box, with a control to remove it.
Beside the box is a Project selector, which names where the work will be created. When you are inside a project it is pinned rather than chosen.
Submit with the Generate button, or Cmd+Enter from anywhere in the box.
The commands
| Command | What it drafts |
|---------|----------------|
| /story | A user story |
| /task | A task under a story |
| /epic | An epic |
| /bug | A bug |
| /sprint | A sprint composed from the backlog |
| /doc | A document |
| /folder | A folder |
| /milestone | A milestone |
| /spec | An addition to the project spec |
| /project | A project |
/sprint appears only for projects that run sprints.
You can also type with no command at all. Elixion reads the intent and answers either with artifacts to review or with a navigation or search result.
Review before anything is written
This is the part that matters, and it is deliberate.
Generating produces a Review list under the heading "Nothing here exists yet. Review what will be created, untick anything you don't want, then confirm." Under it, a line naming the destination: "Will be created in Payments."
Each proposed item has a checkbox. Items that depend on another item are grouped under it, so ticking a story takes its tasks with it. Select all and Select none are above the list.
The footer reads Create N items and Discard, with the standing note "Nothing is written until you confirm." Pressing Create writes only what is ticked. Discarding writes nothing.
A preview is held for thirty minutes. Leave it longer than that and confirming tells you the preview expired and to run the prompt again. Nothing was written in the meantime.
The Prompting page
Prompting (/prompting) is the composer's own page, headed "Ask the team, humans and agents". It puts a set of curated commands on the left and your recent prompting threads on the right, so you can pick up where a previous prompt left off.
The curated set is /spec, /story, /sprint and /milestone, each with worked examples, for instance /story add capacity badges to the planner or /sprint goal: ship billing v0.
Writing prompts that come back useful
- Name the outcome, not the mechanics. "/story let users invite teammates from the inbox" produces a better story than "/story invite modal".
- Say what done looks like. The generated acceptance criteria are only as specific as the sentence they came from.
- Put scope in the prompt rather than editing it out afterwards. "/sprint goal: ship billing v0" narrows the proposal; "/sprint" invites everything.
- Read before you confirm. The review list exists because generated work is a draft, and unticking a wrong item is cheaper than archiving it later.
- Check the project pill. The destination is named on the review screen for exactly this reason.