# Delivery Playbook

## Overview

We're currently exploring better ways of delivering products at [Torchbox](https://torchbox.com/) to deliver better outcomes for our clients. As we've scaled to an employed-owned B-Corp company of over 150 people, distributed globally, we thought it was about time we started to share more openly about how we work to the benefit of prospective clients, current and new employees and to help drive the whole industry forward in standards and practices in regards to agile, multi-disciplinary, human-centered delivery. 

We'll be sharing our thinking iteratively, starting with discovery and editing content as we learn more about how project teams are using this and where there are gaps.  

**What type of project is it based on?**

We wrote this guidance with Wagtail re-platforms in mind, rather than bespoke builds. However, we think there will be useful content here for a wide range of projects. Over time we aim to build this out to provide guidance for different types of partnerships and engagements.

## Quick links

{% content-ref url="guidance/discovery" %}
[discovery](https://playbooks.torchbox.com/torchbox-delivery-playbook/guidance/discovery)
{% endcontent-ref %}

{% content-ref url="guidance/design" %}
[design](https://playbooks.torchbox.com/torchbox-delivery-playbook/guidance/design)
{% endcontent-ref %}

{% content-ref url="guidance/build" %}
[build](https://playbooks.torchbox.com/torchbox-delivery-playbook/guidance/build)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://playbooks.torchbox.com/torchbox-delivery-playbook/delivery.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.

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.