Starting Discovery

Starting Discovery takes one prompt. The agent handles the rest of the setup: confirming the system under test, determining which Cycle project to work in, and preparing the questionnaire. This page covers that opening sequence and how to read the hub you land on.

Before you begin, confirm your agent is connected to the Cycle MCP Server and that you are signed in to Cycle. See the Discovery prerequisites.

Starting the flow

Run the begin-discovery prompt from your agent:

/cycle:begin-discovery

The prompt takes one optional value: the system under test. Provide it up front to skip a question:

/cycle:begin-discovery Blue Yonder

Agent hosts surface prompts differently. Claude Code and Cursor list them as slash commands, and other hosts use a prompt picker. See Prompts for how your host presents them.

Confirming the system under test

If you did not name a system, the agent asks before doing anything else.

Blue Yonder proceeds into the flow. Any other answer ends the flow with a message that the system is not yet supported. The agent does not fall back to a general-purpose alternative, and no Discovery work begins.

Resolving the project

Discovery always works inside a Cycle project, because that is where its questions, answers, and output live.

The agent looks in your working folder and its immediate subfolders for a folder containing a .cycproj file. What happens next depends on what it finds:

What the agent finds	What happens
Exactly one project	That project is used. If no user has been recorded for it yet, the agent asks for your username first, then claims the project for you.
Several projects	The agent lists them and asks you to choose one.
No project	The agent asks for a project name and your username, then creates a project for you.

The first time Discovery runs in a project, the agent prepares the questionnaire for the system type. Every question starts unanswered.

Reading the input-source hub

Once the project is resolved, the agent shows you the input-source hub. Return here after every piece of work, so you always know what is done and what remains.

The hub reports two things.

Each input source and its status.

Status	Meaning
not started	No work has been done with this source yet.
in progress	Work has begun but is not finished.
done	The source has been worked. Applies to document ingest.
complete	Every applicable question has been answered. Applies to the questionnaire.

Whether a test plan can be generated. This stays no until every applicable question has been answered. Even after it changes to yes, nothing is generated until you ask. See Making a Test Plan.

Choosing an input source

There is no required order at the hub. Answer questions first, ingest documents first, or move back and forth as material becomes available. Each source is tracked separately, so working one never undoes the other.

Ask the agent for the source you want, and it takes you into that work and returns you to the hub afterward.

Example

You say:

/cycle:begin-discovery Blue Yonder

The agent:

1. Confirms that Blue Yonder is supported and continues.

2. Searches the working folder for a Cycle project, finds none, and asks for a project name and your username.

3. Creates the project after you answer, then prepares the questionnaire with every question unanswered.

4. Shows you the hub:

   Input source     Status
   ---------------  -----------
   document ingest  not started
   questions        not started
   
   Ready to generate a test plan: no

5. Asks which input source you want to work on.

From here you choose a source and begin.

Working your first input source

• Answering Questions: The questionnaire, and the source a test plan is built from.
• Ingesting Documents: Turn test documentation you already have into consistent test specifications.