Update documentation for command-style microagents with user input support

docs/usage/prompting/microagents-keyword.mdx

@@ -5,26 +5,111 @@ description: Keyword-triggered microagents provide OpenHands with specific instr
 
 ## Usage
 
-These microagents are only loaded when a prompt includes one of the trigger words.
+Keyword-triggered microagents are only loaded when a prompt includes one of the trigger words. There are two types of keyword-triggered microagents:
+
+1. **Standard Keyword Microagents**: Triggered by keywords embedded in text
+2. **Command-Style Microagents**: Triggered by command-style inputs (e.g., `/fix_test`) that can prompt for user input
+
+Additionally, there's a special type of microagent that's always active:
+
+3. **Repository Microagents**: Always active for a specific repository, providing repository-specific context and tools
 
 ## Frontmatter Syntax
 
 Frontmatter is required for keyword-triggered microagents. It must be placed at the top of the file,
-above the guidelines.
+above the guidelines. Enclose the frontmatter in triple dashes (---).
+
+### Standard Keyword Microagents
 
-Enclose the frontmatter in triple dashes (---) and include the following fields:
+For standard keyword microagents, include the following fields:
 
 | Field      | Description                                      | Required | Default          |
 |------------|--------------------------------------------------|----------|------------------|
+| `name`     | The name of the microagent                       | No       | Filename         |
+| `type`     | The type of microagent (`knowledge`)             | No       | Inferred         |
 | `triggers` | A list of keywords that activate the microagent. | Yes      | None             |
-| `agent`    | The agent this microagent applies to.            | No       | 'CodeActAgent'   |
 
+### Command-Style Microagents
+
+For command-style microagents that require user input, include the following fields:
+
+| Field      | Description                                                | Required | Default          |
+|------------|------------------------------------------------------------|----------|------------------|
+| `name`     | The name of the microagent                                 | No       | Filename         |
+| `type`     | The type of microagent (`task`)                            | No       | Inferred         |
+| `triggers` | A list of command triggers (e.g., `/fix_test`)             | No       | `/[name]`        |
+| `inputs`   | A list of input variables the microagent requires          | Yes      | None             |
+
+### Repository Microagents
 
-## Example
+Repository microagents are always active for a specific repository. They provide repository-specific context and tools.
+
+| Field      | Description                                                | Required | Default          |
+|------------|------------------------------------------------------------|----------|------------------|
+| `name`     | The name of the microagent                                 | No       | Filename         |
+| `type`     | The type of microagent (`repo`)                            | No       | Inferred         |
+
+#### Repository Microagent Example
+
+Here's an example of a repository microagent:
+
+```yaml
+---
+# The type field is optional and will be inferred as 'repo' when no triggers are present
+---
 
-Keyword-triggered microagent file example located at `.openhands/microagents/yummy.md`:
+# Repository Guidelines
+
+This repository follows these coding standards:
+1. Use PEP 8 for Python code
+2. Use ESLint for JavaScript code
+3. Write unit tests for all new features
 ```
+
+This microagent is always active when working with the repository and provides repository-specific guidelines.
+
+### MCP Tools Support
+
+Microagents can also provide additional MCP (Model-Code-Prompt) tools to the agent. This is useful for extending the agent's capabilities with custom tools.
+
+| Field        | Description                                                | Required | Default          |
+|--------------|-----------------------------------------------------------|----------|------------------|
+| `mcp_tools`  | Configuration for additional MCP tools                     | No       | None             |
+
+#### MCP Tools Example
+
+Here's an example of a microagent that provides an additional MCP tool (the `fetch` tool for accessing web content):
+
+```yaml
+---
+# The type field is optional and will be inferred as 'repo' when no triggers are present
+mcp_tools:
+  stdio_servers:
+    - name: "fetch"
+      command: uvx
+      args:
+        - mcp-server-fetch
 ---
+```
+
+This microagent is a repository microagent (always active) that adds the `fetch` tool to the agent's capabilities.
+
+Each input in the `inputs` list requires:
+
+| Field         | Description                                      | Required |
+|---------------|--------------------------------------------------|----------|
+| `name`        | The name of the input variable                   | Yes      |
+| `description` | A description of what the input should contain   | Yes      |
+
+
+## Examples
+
+### Standard Keyword Microagent Example
+
+Standard keyword microagent file example located at `.openhands/microagents/yummy.md`:
+```yaml
+---
+# The type field is optional and will be inferred as 'knowledge' when triggers are present
 triggers:
 - yummyhappy
 - happyyummy
@@ -33,4 +118,58 @@ triggers:
 The user has said the magic word. Respond with "That was delicious!"
 ```
 
-[See examples of microagents triggered by keywords in the official OpenHands repository](https://github.com/All-Hands-AI/OpenHands/tree/main/microagents)
+### Command-Style Microagent Example
+
+Command-style microagent file example located at `.openhands/microagents/fix_test.md`:
+```yaml
+---
+# The type field is optional and will be inferred as 'task' when inputs are present
+triggers:
+- /fix_test
+inputs:
+  - name: BRANCH_NAME
+    description: "Branch for the agent to work on"
+  - name: TEST_COMMAND_TO_RUN
+    description: "The test command you want the agent to work on. For example, `pytest tests/unit/test_bash_parsing.py`"
+  - name: FUNCTION_TO_FIX
+    description: "The name of function to fix"
+  - name: FILE_FOR_FUNCTION
+    description: "The path of the file that contains the function"
+---
+
+Can you check out branch "{{ BRANCH_NAME }}", and run {{ TEST_COMMAND_TO_RUN }}.
+
+Help me fix these tests to pass by fixing the {{ FUNCTION_TO_FIX }} function in file {{ FILE_FOR_FUNCTION }}.
+
+PLEASE DO NOT modify the tests by yourself -- Let me know if you think some of the tests are incorrect.
+```
+
+## Using Command-Style Microagents
+
+Command-style microagents are designed to streamline common development tasks by providing structured templates for specific operations. They are triggered using a command-style format and will prompt the user for any required inputs.
+
+### How to Use
+
+1. Type `/` in the chat input to see available command-style microagents
+2. Select a microagent from the dropdown or type its name (e.g., `/fix_test`)
+3. The agent will prompt you for any required inputs
+4. Provide the requested information
+5. The agent will execute the task with your inputs
+
+### Template Variables
+
+In the body of a command-style microagent, you can reference input variables using the `{{ VARIABLE_NAME }}` syntax. These will be replaced with the user-provided values when the microagent is triggered.
+
+### Available Command-Style Microagents
+
+OpenHands includes several built-in command-style microagents:
+
+| Command              | Description                                           |
+|----------------------|-------------------------------------------------------|
+| `/fix_test`          | Fix failing tests by modifying a specific function    |
+| `/update_test`       | Update tests for a new implementation                 |
+| `/update_pr`         | Update a pull request description                     |
+| `/address_pr_comments` | Address comments on a pull request                  |
+| `/add_repo_instruction` | Add instructions to the repository microagent      |
+
+[See examples of microagents in the official OpenHands repository](https://github.com/All-Hands-AI/OpenHands/tree/main/microagents)

docs/usage/prompting/microagents-overview.mdx

@@ -8,7 +8,7 @@ description: Microagents are specialized prompts that enhance OpenHands with dom
 Currently OpenHands supports the following types of microagents:
 
 - [General Microagents](./microagents-repo): General guidelines for OpenHands about the repository.
-- [Keyword-Triggered Microagents](./microagents-keyword): Guidelines activated by specific keywords in prompts.
+- [Keyword-Triggered Microagents](./microagents-keyword): Guidelines activated by specific keywords in prompts, including command-style microagents that prompt for user inputs.
 
 To customize OpenHands' behavior, create a .openhands/microagents/ directory in the root of your repository and
 add `<microagent_name>.md` files inside. For repository-specific guidelines, you can ask OpenHands to analyze your repository and create a comprehensive `repo.md` file (see [General Microagents](./microagents-repo) for details).
@@ -34,7 +34,7 @@ some-repository/
 Each microagent file may include frontmatter that provides additional information. In some cases, this frontmatter
 is required:
 
-| Microagent Type                 | Required |
-|---------------------------------|----------|
-| `General Microagents`           | No       |
-| `Keyword-Triggered Microagents` | Yes      |
+| Microagent Type                                | Required |
+|------------------------------------------------|----------|
+| `General Microagents`                          | No       |
+| `Keyword-Triggered Microagents (all types)`    | Yes      |

microagents/add_agent.md

@@ -1,20 +1,17 @@
 ---
-name: add_agent
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
-  - new agent
-  - new microagent
-  - create agent
-  - create an agent
-  - create microagent
-  - create a microagent
-  - add agent
-  - add an agent
-  - add microagent
-  - add a microagent
-  - microagent template
+- new agent
+- new microagent
+- create agent
+- create an agent
+- create microagent
+- create a microagent
+- add agent
+- add an agent
+- add microagent
+- add a microagent
+- microagent template
+type: knowledge
 ---
 
 This agent helps create new microagents in the `.openhands/microagents` directory by providing guidance and templates.
@@ -38,4 +35,4 @@ For detailed information, see:
 
 - [Microagents Overview](https://docs.all-hands.dev/usage/prompting/microagents-overview)
 - [Microagents Syntax](https://docs.all-hands.dev/usage/prompting/microagents-syntax)
-- [Example GitHub Microagent](https://github.com/All-Hands-AI/OpenHands/blob/main/microagents/github.md)
+- [Example GitHub Microagent](https://github.com/All-Hands-AI/OpenHands/blob/main/microagents/github.md)

microagents/add_repo_inst.md

@@ -1,13 +1,9 @@
 ---
-name: add_repo_inst
-version: 1.0.0
-author: openhands
-agent: CodeActAgent
+inputs:
+- description: Branch for the agent to work on
+  name: REPO_FOLDER_NAME
 triggers:
 - /add_repo_inst
-inputs:
-  - name: REPO_FOLDER_NAME
-    description: "Branch for the agent to work on"
 ---
 
 Please browse the current repository under /workspace/{{ REPO_FOLDER_NAME }}, look at the documentation and relevant code, and understand the purpose of this repository.
@@ -62,4 +58,4 @@ Frontend:
 ```
 
 Now, please write a similar markdown for the current repository.
-Read all the GitHub workflows under .github/ of the repository (if this folder exists) to understand the CI checks (e.g., linter, pre-commit), and include those in the repo.md file.
+Read all the GitHub workflows under .github/ of the repository (if this folder exists) to understand the CI checks (e.g., linter, pre-commit), and include those in the repo.md file.

microagents/address_pr_comments.md

@@ -1,19 +1,15 @@
 ---
-name: address_pr_comments
-version: 1.0.0
-author: openhands
-agent: CodeActAgent
+inputs:
+- description: URL of the pull request
+  name: PR_URL
+- description: Branch name corresponds to the pull request
+  name: BRANCH_NAME
 triggers:
 - /address_pr_comments
-inputs:
-  - name: PR_URL
-    description: "URL of the pull request"
-  - name: BRANCH_NAME
-    description: "Branch name corresponds to the pull request"
 ---
 
 First, check the branch {{ BRANCH_NAME }} and read the diff against the main branch to understand the purpose.
 
 This branch corresponds to this PR {{ PR_URL }}
 
-Next, you should use the GitHub API to read the reviews and comments on this PR and address them.
+Next, you should use the GitHub API to read the reviews and comments on this PR and address them.

microagents/agent_memory.md

@@ -1,10 +1,7 @@
 ---
-name: agent_memory
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
 - /remember
+type: knowledge
 ---
 
 * Repository memory: Use .openhands/microagents/repo.md under each repository root to store and access important information.
@@ -29,4 +26,4 @@ triggers:
   - If you've only explored a portion of the codebase, clearly note this limitation in the repository structure documentation
   - If you don't know the essential commands for working with the repository, such as lint or typecheck, ask the user and suggest adding them to repo.md for future reference (with permission)
 
-When you receive this message, please review and summarize your recent actions and observations, then present a list of valuable information that should be saved in repo.md to the user.
+When you receive this message, please review and summarize your recent actions and observations, then present a list of valuable information that should be saved in repo.md to the user.

microagents/default-tools.md

@@ -1,15 +1,9 @@
 ---
-# This is a repo microagent that is always activated
-# to include necessary default tools implemented with MCP
-name: default-tools
-type: repo
-version: 1.0.0
-agent: CodeActAgent
 mcp_tools:
   stdio_servers:
-    - name: "fetch"
-      command: "uvx"
-      args: ["mcp-server-fetch"]
-# We leave the body empty because MCP tools will automatically add the
-# tool description for LLMs in tool calls, so there's no need to add extra descriptions.
----
+  - args:
+    - mcp-server-fetch
+    command: uvx
+    name: fetch
+type: repo
+---

microagents/docker.md

@@ -1,11 +1,8 @@
 ---
-name: docker
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
 - docker
 - container
+type: knowledge
 ---
 
 # Docker Installation and Usage Guide
@@ -52,4 +49,4 @@ To verify Docker is working correctly, run the hello-world container:
 
 ```bash
 sudo docker run hello-world
-```
+```

microagents/fix_test.md

@@ -1,23 +1,20 @@
 ---
-name: fix_test
-version: 1.0.0
-author: openhands
-agent: CodeActAgent
+inputs:
+- description: Branch for the agent to work on
+  name: BRANCH_NAME
+- description: The test command you want the agent to work on. For example, `pytest
+    tests/unit/test_bash_parsing.py`
+  name: TEST_COMMAND_TO_RUN
+- description: The name of function to fix
+  name: FUNCTION_TO_FIX
+- description: The path of the file that contains the function
+  name: FILE_FOR_FUNCTION
 triggers:
 - /fix_test
-inputs:
-  - name: BRANCH_NAME
-    description: "Branch for the agent to work on"
-  - name: TEST_COMMAND_TO_RUN
-    description: "The test command you want the agent to work on. For example, `pytest tests/unit/test_bash_parsing.py`"
-  - name: FUNCTION_TO_FIX
-    description: "The name of function to fix"
-  - name: FILE_FOR_FUNCTION
-    description: "The path of the file that contains the function"
 ---
 
 Can you check out branch "{{ BRANCH_NAME }}", and run {{ TEST_COMMAND_TO_RUN }}.
 
 Help me fix these tests to pass by fixing the {{ FUNCTION_TO_FIX }} function in file {{ FILE_FOR_FUNCTION }}.
 
-PLEASE DO NOT modify the tests by yourself -- Let me know if you think some of the tests are incorrect.
+PLEASE DO NOT modify the tests by yourself -- Let me know if you think some of the tests are incorrect.