# Introduction

![](https://1060224550-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LT-3LNTAsA_rjnEu_Uq%2F-LT1-rjZRV47egF117eU%2F-LT10n0jUT8TEEXN380h%2Ftde-playbook-cover.jpg?alt=media\&token=c6310e46-ce93-47c9-8c12-952536a1b94c)

This playbook accompanies our [Guide to Tactical Data Engagement](https://communities.sunlightfoundation.com/methodology/), a guidebook to help cities go beyond open data policies and platforms, to help residents use open data for community problem-solving. Tactical Data Engagement helps data providers like city governments provide better open data and public information that's tailored to community needs.&#x20;

The guide walks cities through finding and refining personas and use cases for open data, or the Discovery phase of Tactical Data Engagement. It also shows data providers how to co-design and implement resident-centered open data solutions with community partners.&#x20;

We designed playbooks to help jumpstart community action, providing stories about how open data advocates have co-designed, collaborated, and solved problems together using open data. The first playbook in our series on [Data User Groups](https://sunlight-foundation.gitbooks.io/playbook-data-user-groups/content/home.html) was released in October 2017. This playbook is the second in our series. Playbooks are versatile, just like the rest of the TDE approach, and should be used creatively.

![](https://1060224550-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LT-3LNTAsA_rjnEu_Uq%2F-LT1-rjZRV47egF117eU%2F-LT10rZLIF0Mf_ksuZTO%2Fwwc-seal.png?alt=media\&token=40014d84-b5fc-479d-a0f7-4fd8bd0277ee)


---

# 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://sunlight-open-cities.gitbook.io/playbook-open-data-scope-a-thon/master.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.
