Define

Define is the second stage of the platform workflow. Its purpose is to take the raw ideas and context from Discover and produce a thorough, unambiguous product definition. If Discover is where you think out loud, Define is where you commit.

What it is

Every assumption is surfaced, every requirement is captured, and the output becomes the formal contract that all subsequent work is measured against. The Define workflow runs in two structured layers, each producing a formal artefact stored against the Workflow Run.

Who can use it

Available to all authenticated users with an active subscription (both ORG Admins and ORG Members).

Navigate to Define in the sidebar or go directly to /workflow.

How it works

Workflow Runs

Every product definition is stored as a Workflow Run. A Workflow Run is the container for all artefacts produced in the Define stage. You can have multiple Workflow Runs, one per product or initiative.

From the Define page you can:

• Create a new Workflow Run
• View and navigate all existing runs
• Resume a run that is in progress

Each run progresses through a defined status lifecycle: INTAKE → DISCOVERY → NEEDS_REVIEW → SYNTHESIS → COMPLETE.

Layer 1: Discovery

Layer 1 performs a structured, multi-pass discovery process against your uploaded documents and the conversation history from your Discover session.

What it does:

• Runs multiple discovery passes to extract customer needs, pain points, constraints, and assumptions
• Produces a formal discovery artefact stored on the Workflow Run
• Tracks explicit status stages so you always know where the run is in the process

The discovery artefact captures what the AI has understood about the product from all available context. You should review this output carefully. It is the foundation of everything that follows.

Layer 2: Problem Statement Synthesis

Layer 2 takes the Layer 1 discovery artefact and synthesises it into a concise, structured problem statement.

The problem statement:

• Defines the specific problem being solved
• Identifies who experiences the problem
• Articulates the current state and desired future state
• Captures scope boundaries

Once Layer 2 completes, the Workflow Run status advances to COMPLETE and the definition is ready to be used as the input for the Design stage.

Adversarial Review

Any artefact produced in Define (discovery output, problem statement) can be submitted to an adversarial review. This is an independent AI critique that stress-tests the artefact by challenging its assumptions, identifying gaps, and flagging potential issues.

How to use it:

1. Open the artefact you want to review.
2. Select Adversarial Review (this opens at /adversarial).
3. The critique streams token by token, contextualised to the type of artefact being reviewed.
4. Use the critique output to identify what needs to be amended before moving forward.

Adversarial review is not a blocker. It is an optional quality gate. Use it whenever you want a second opinion from a critical perspective before committing to the next stage.

Planner Chat (Artefact Amendment)

The Planner Chat panel is a side-panel LLM interface available throughout Define (and Design and Build). It is specifically designed for amending the artefacts on your Workflow Run.

Unlike the general Discover chat, Planner Chat is aware of the current run and its artefacts. You can use it to:

• Ask questions about the current artefact: "What assumptions are we making in the problem statement?"
• Request targeted amendments: "Update the problem statement to reflect that the primary user is a warehouse manager, not a logistics coordinator."
• Drill deeper into a specific area: "Expand the customer needs section to include accessibility requirements."

The AI applies your requested changes as diffs to the stored artefact. Planner chat messages are saved separately from general chat sessions. All changes are persisted to the Workflow Run.

How to use it to solve your problem

Running a complete Define workflow

1. Navigate to Define in the sidebar.
2. Click New Run to create a new Workflow Run. Give it a name that reflects the product or initiative.
3. If you have discovery context from the Discover stage, it will be associated automatically via the linked Workflow Run.
4. Trigger Layer 1 to run the discovery process. Wait for the status to advance to NEEDS_REVIEW.
5. Review the discovery artefact. Check that it accurately reflects what you know about the problem.
6. If anything is missing or incorrect, open the Planner Chat panel and describe the amendment needed.
7. Once you are satisfied with the discovery artefact, trigger Layer 2 to synthesise the problem statement.
8. Review the problem statement. Run an Adversarial Review to challenge it if you want a quality check.
9. Amend via Planner Chat as needed until the problem statement accurately reflects the product you intend to build.
10. When the run reaches COMPLETE, the definition is ready for Design.

Amending a completed run

Workflow Runs can be reopened and amended at any time. If requirements change after you have moved to Design or Build, come back to Define, update the relevant artefacts via Planner Chat, and the changes will be available to inform re-runs of the Design workflow.

How it fits the broader picture

Define sits between Discover and Design. Its output, the completed Workflow Run artefacts, becomes the source of truth that the Design workflow is validated against. The Design stage will not produce artefacts that contradict or drift from the product definition, because the definition is explicitly injected into every Design prompt.

This is the critical handoff. A thorough, accurate Define output means the Design stage will produce a solution that actually solves the right problem. Gaps or vagueness in Define will propagate forward.

When your problem statement is complete and reviewed, move to Design.