> For the complete documentation index, see [llms.txt](https://handbook.hackalong.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.hackalong.io/patterns/cocreation/co-create-proposals.md).

# Co-Create Proposals

There are many ways to co-create proposals. They typically follow a similar pattern:

1. Agree on the driver (or problem / opportunity / need)
2. Explore the topic and understand constraints
3. Generate ideas
4. Design a proposal (often done by a smaller group)

One way to co-create proposals is to use S3’s [Proposal Forming](https://patterns.sociocracy30.org/proposal-forming.html) pattern.

![A template for proposals](https://patterns.sociocracy30.org/img/templates/proposal-template.png)

For inspiration for steps 2 and 3, look to classic group facilitation techniques or design thinking activities.

Besides in a face-to-face workshop, you can adapt this process for online meetings. You can even use it asynchronously (and over an extended period of time) to include many people.


---

# 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://handbook.hackalong.io/patterns/cocreation/co-create-proposals.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.