custom-plan
Create a structured feature plan using PLAN + WORKING_MEMORY + USER_VERIFICATION (tasklist) files
Update LLM Providers documentation to match llms.txt
How it fires
How this command gets triggered: by you, by Claude, or both.
/docs-llms-txtContext preview
What this command does when you run it.
Update LLM Providers documentation to match llms.txt
description: "Update LLM Providers documentation to match llms.txt" allowed-tools: ["bash", "read", "write", "edit"]
Synchronizes `docs/docs/guides/supported-llm-providers.md` with the source of truth at `docs/static/llms.txt`.
Read the llms.txt file:
cat docs/static/llms.txt
Parse the file to extract:
cat docs/docs/guides/supported-llm-providers.md
For each provider in llms.txt:
**Check if provider exists in documentation:**
**Maintain structure:**
**Built-in Provider format:**
### {Provider Name}
```yaml
llm:
provider: {provider-id}
model: {default-model}
apiKey: ${API_KEY_VAR}**Supported models:**
**Features:**
---
**OpenAI-Compatible Provider format:**
````markdown
### {Provider Name}
```yaml
llm:
provider: openai-compatible
model: {model-name}
apiKey: ${API_KEY}
baseURL: {base-url}
maxInputTokens: {tokens}**{Additional notes or popular models}**
---
### 4. Update Documentation Use the Edit or Write tool to update `docs/docs/guides/supported-llm-providers.md` with all changes. ### 5. Verify Read the updated file to ensure: - All providers from llms.txt are present - Model lists are complete and accurate - Default models are correctly identified - No duplicate entries - YAML examples are syntactically correct - Environment variables section is up-to-date ## Important Notes - **Source of truth:** `docs/static/llms.txt` - **Keep:** Frontmatter, :::tip callout, section headers, "Choosing the Right Provider", "Environment Variables" - **Update:** Provider sections, model lists, default models, features - **Remove:** Providers not in llms.txt - **Format:** Follow existing markdown structure exactly - **Accuracy:** Ensure model names match llms.txt exactly
Agent harness and tookit for building AI agents and agentic applications. CLI and SDKs included
Create a structured feature plan using PLAN + WORKING_MEMORY + USER_VERIFICATION (tasklist) files
Analyze a file or folder for code slop and quality issues compared to main branch
Start the Dexto development server with optional agent file selection
Update Agent Registry documentation to match agent-registry.json
Update MCP Registry documentation to match server-registry-data.json
Extract GitHub review comments from Dexto PRs with powerful filtering options