> For the complete documentation index, see [llms.txt](https://playbooks.equalexperts.com/inceptions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbooks.equalexperts.com/inceptions/run-an-inception/design/design-inception-agenda.md).
# Design inception agenda
As mentioned earlier, a good agenda has a narrative, a logical flow through which we run activities that give us insight to ultimately fulfil the goals of the inception:
## **1 -** UNDERSTAND THE PROBLEM / OPPORTUNITY
We start with aligning on what the problem, vision and goals are:
* Why are we doing this?
* Where do we want to be?
## **2 -** UNDERSTAND CONTEXT AND DOMAIN
We then analyse the current and future states covering people, process and technology:
* Where are we now and where do we want to be?
* What are we dealing with?
## **3-** IDENTIFY AND DEFINE SOLUTION OPTIONS
We then head into top level to-be solution design: We define scope (usually feature / epic-level overall and story-level for the immediate next sprints) and functional / technical solution design. We agree how to prioritise, identify risks and dependencies, and define ways of working:
* What are potential solution options?
* What will the solution look like?
## **4 -** IDENTIFY DELIVERY APPROACH AND PLAN DELIVERY
Finally, we make a recommendation (continue, pivot or stop).
When we continue, we define a delivery approach, team-shape, plan/roadmap and ultimately an estimate. This results in a statement of work and actionable immediate next steps:
* How do we get there?
* How do we deliver?
{% hint style="info" %}
Most inceptions will follow this high level agenda: this is all that’s needed to confirm desirability, viability and feasibility of the initiative.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://playbooks.equalexperts.com/inceptions/run-an-inception/design/design-inception-agenda.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.