# Page Not Found

The URL `files/MXqUtl60D1KET1Lv104B` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Converting TODOs into issues](https://stepsize.gitbook.io/stepsize-documentation/issues/converting-todos-into-issues.md)
- [How to create an issue](https://stepsize.gitbook.io/stepsize-documentation/issues/how-to-create-an-issue.md)
- [Adding more code and context to your issues](https://stepsize.gitbook.io/stepsize-documentation/issues/adding-more-code-and-context-to-your-issues.md)
- [How to view inline annotations](https://stepsize.gitbook.io/stepsize-documentation/issues/how-to-view-inline-annotations.md)
- [How to resolve issues](https://stepsize.gitbook.io/stepsize-documentation/issues/how-to-resolve-issues.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://stepsize.gitbook.io/stepsize-documentation/issues/converting-todos-into-issues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://stepsize.gitbook.io/stepsize-documentation/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://stepsize.gitbook.io/stepsize-documentation/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/stepsize-documentation/issues/converting-todos-into-issues.md`).

You may also use `Accept: text/markdown` header for content negotiation.