> 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/introduction/inception-complete-what-now.md).

# Inception Complete, What now?

We create deliverables (depending on the context) that allow us to answer whether to proceed and if so, how.

From an overall ‘project management’ perspective, often the most important deliverable is the scope, plan or roadmap and associated cost. We often turn these into a single statement of work (marked by a star). This is not the case for all type of inceptions - for instance, when we incept a new feature for an existing team, we are often more interested in an assessment of readiness and detailed backlog for the next phase.

![](/files/-M-PB6-eh2enysBRnhdV)

We create a number of intermediate artefacts, before creating these deliverables. These help us achieve alignment by providing background and context, and are often the basis for subsequent work. We will discuss this in detail in later chapters.


---

# 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/introduction/inception-complete-what-now.md?ask=<question>&goal=<endgoal>
```

`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.