custom-plan
Create a structured feature plan using PLAN + WORKING_MEMORY + USER_VERIFICATION (tasklist) files
Update Agent Registry documentation to match agent-registry.json
How it fires
How this command gets triggered: by you, by Claude, or both.
/docs-agent-registryContext preview
What this command does when you run it.
Update Agent Registry documentation to match agent-registry.json
description: "Update Agent Registry documentation to match agent-registry.json" allowed-tools: ["bash", "read", "write", "edit", "glob"]
Synchronizes `docs/docs/guides/agent-registry.md` with the source of truth at `agents/agent-registry.json`.
Read the agent registry JSON file:
cat agents/agent-registry.json
Parse all agent entries and extract:
For each agent, read its YAML configuration to extract:
cat agents/{source}/{main}or for single-file agents:
cat agents/{source}cat docs/docs/guides/agent-registry.md
For each agent in the registry:
**Check if agent exists in documentation:**
**Entry format:**
## {name}
{description}
**Author:** {author}
**Tags:** {comma-separated tags}
### Features
- Feature 1
- Feature 2
- Feature 3
### Configuration
{high-level overview of LLM, MCP servers, tools}
### Installation
```bash
dexto install {id}---
### 5. Update Documentation Use the Edit or Write tool to update `docs/docs/guides/agent-registry.md` with all changes. ### 6. Verify Read the updated file to ensure: - All agents from registry are present - No duplicate entries - Consistent structure - Installation commands are correct - Tags and descriptions match registry ## Important Notes - **Source of truth:** `agents/agent-registry.json` - **Keep:** Frontmatter, introduction, usage instructions - **Update:** All agent entries based on JSON + YAML config - **Remove:** Agents not in JSON registry - **Format:** Follow existing markdown structure exactly - **Details:** Extract actual config details from YAML files, don't just copy description
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 MCP Registry documentation to match server-registry-data.json
Extract GitHub review comments from Dexto PRs with powerful filtering options