Discovery

Discovery answers the Learn loop’s question: are we building the right thing?

It is where a project stops being an idea and becomes something the rest of Taiga can act on. Everything downstream reads what you settle here.

The conversation

Discovery starts as a conversation. You describe what you want to build, in your own words, and Taiga assembles a structured specification from what you say.

You do not need to prepare anything or learn the vocabulary first. The one thing worth doing deliberately is saying when something is undecided, rather than picking an answer to move things along. An open question is visible later. A guess is not, and everything generated afterward is built on it.

Your progress is saved as a draft, so you can leave and come back.

The specification

The specification is Discovery’s main output. It is built in seven sections, worked through in order:

Section	What it settles
Vision and purpose	The core problem, your vision for the solution, and how you will measure success.
Users and stakeholders	Primary users, their roles, and their permissions.
Capabilities	The core features and workflows.
Data and information	Key data entities and the relationships between them.
Technical context	Integration requirements and technical constraints.
Compliance and security	Security and regulatory requirements.
Timeline and priorities	Timeline, milestones, and what comes first.

The result is structured and machine-readable.

Machine-readable is the point. It is not a document written for people that agents happen to read. It is the input every later step is generated from.

Each section carries its own completion status, so you can see what is still thin rather than discovering it when something downstream comes out vague. You can export it as a PDF.

Publishing, and changing your mind later

Publishing the specification is what unlocks the rest of the project.

It is not a final commitment. Specifications are versioned: you can create a new version later, either starting fresh or copying the current one as a base. The version you have published is the one agents work from.

The rest of the document set

With a specification published, Discovery is also where the remaining project documents are generated from it, one at a time.

Do this in the order Taiga offers rather than in bulk. The documents feed each other, so an assumption you accept early is one you have accepted everywhere. Project documents covers the set and the order.

What Discovery does not decide

Discovery describes the product, not the work.

Turning it into things that can be built is a separate step, and it happens after the document set is complete. See your first project for that path end to end.