Docs / Engineering

Intents

Intents are lasting outcome statements describing what the system should do. Each one is worked through scenarios, reconciliation and a pipeline.

When to use it

When you want requirements to stay connected to testable scenarios and to delivery, and to record why an outcome changed.

Start here

Click "New Intent", state the outcome, then complete the elicitation to draft scenarios. Use "Edit" later to change it.

How to use it

  1. Click "New Intent". Enter "What" (required) and optionally "Why", pick a "Label" (intent, goal, feature or story), add failure and success scenarios by typing each and pressing Enter, then click "Create Intent".
  2. Select an intent in the list. The "Elicitation" tab opens and the AI asks clarifying questions. Answer every question, then click "Draft scenarios". When drafting finishes you are moved to the "Scenarios" tab.
  3. On the "Scenarios" tab, read each scenario in Gherkin or Narrative view. Optionally tick the items under "Review decisions" and add notes, then click "Approve" or "Request changes". Only the intent's owner or an organisation admin can approve.
  4. Under a scenario, use the "Verification" section. With no repository connected, click "Connect repository" and create one, then click "Run". Each result shows Queued, Running, Pass, Fail or Error, a verified or provisional badge, and a log via "Show log".
  5. Open the "Reconciliation" tab. After you save a plain edit to an intent, proposals appear here within seconds, each labelled Still valid, Needs refinement, Contradicted or Newly required, with "Accept" and "Dismiss" on open ones.
  6. Click "Edit" beside the intent's title, change What, Why, Label or the scenarios, then "Save". A Label-only change saves at once. Otherwise "Save as scope change" (rationale required) makes a new version; "Save without versioning" is a plain edit.
  7. Open the "Pipeline" tab and click "Run Standard Pipeline" or "Lite (tests only)", then "Approve" or "Reject" at a human gate. On "Dependencies", pick "Depends on" intents and click "Add dependency"; the pipeline waits for them.
  8. Open the "History" tab to see earlier versions of the intent, created by scope changes. Select one to see the what, why and scenarios as they were, plus the rationale. With none, it says there is no version history yet.

Good to know

  • Selecting an intent starts elicitation automatically, or resumes an existing session. If elicitation fails, the tab shows "Retry".
  • "Approve" is blocked while coverage gaps exist. The gaps are listed on the scenario; "Request changes" is still available. Only scenarios in the draft state can be approved or sent back.
  • "Run" appears only for scenarios in the spec state and when a repository is connected; otherwise the panel offers "Connect repository". A repository imported from your own source is refused ("disabled until the runner is sandboxed"); one created by name only can run.
  • An intent whose pipeline is waiting shows an amber chip, "Blocked by N" or "Waiting for pipeline slot". Click it to see the upstream intents; the pipeline starts by itself once they are implemented.
  • "Import" opens a separate page where you upload a CSV, XLSX, PDF or DOCX file, or paste text. You answer any questions, review the candidate intents, import them, and can then create stories from them.

Related

Last updated 6 October 2026