> For the complete documentation index, see [llms.txt](https://en.wiki.zks.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://en.wiki.zks.org/governance/proposal-requirement-and-template.md).

# Proposal Requirement and Template

**All ZKSwap Improvement Proposals should follow the template guidelines:**

### **1.Proposal Requirement：**

1: The title should be concise and the proposal should only be written in English or Chinese.

2: Start the proposal with a short summary or bullet points.

3: Provide an explanation: Clearly describe what will be implemented if the proposal is executed.

4: Give the motivation: Reason for your proposal.

5: Add specifications: Provide a further explanation if necessary.

6: Give the Pros and Cons of your proposal.

7: Option to include a poll for voting.

Please carefully consider your proposal before posting on our [forum](https://forum.zks.org/), thank you!

### **2.Proposal Template：**

**Title：**

**Summary：**

**Explanation：**

**Motivation：**

**Specifications：**

**Pros：**

**Cons：**

**Poll：**


---

# 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://en.wiki.zks.org/governance/proposal-requirement-and-template.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.