> For the complete documentation index, see [llms.txt](https://cyr1en.gitbook.io/commandprompter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cyr1en.gitbook.io/commandprompter/getting-started/why-commandprompter.md).

# Why CommandPrompter?

CommandPrompter turns **static commands** (like those in DeluxeMenus, ChestCommands, or Citizens NPCs) into **interactive workflows**.

### The Problem

Traditional menu buttons execute fixed, hardcoded commands. You cannot easily prompt a player for dynamic input (such as a target player name, a reason, or an amount) without complex workarounds.

### The Solution

By replacing static arguments with prompt placeholders (e.g., `/ban <Who do you want to ban?> <Reason?>`), CommandPrompter dynamically captures player input at runtime and constructs the final command.

### Use Cases

* **NPC Interaction:** Ask for confirmation before performing actions like teleportation.
* **Announcements:** Let staff broadcast custom messages via a simple menu button.
* **Economy/Shops:** Prompt players for quantities when buying or selling items.
* **Moderation:** Query staff for player names, ban reasons, or mute durations dynamically.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cyr1en.gitbook.io/commandprompter/getting-started/why-commandprompter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
