delegating-to-wiki-agent

Delegating Confluence operations to a specialized sub-agent keeps your main context lean while executing wiki tasks remotely. Set up shell wrappers at ~/bin, configure AGENT-INSTRUCTIONS.md for sub-agent behavior, and route read, update, create, and search operations through the wiki delegation pattern to maintain cost efficiency.

Yes. The delegation pattern isolates all API details and credentials in the sub-agent layer, preventing exposure in your main context. The sub-agent handles wiki-update, wiki-create, wiki-search, and wiki-read operations on Confluence pages within the OPS space while you work with structured JSON outputs.

Delegate to a cost-effective sub-agent using the Deli-Gator delegation pattern. Use wiki-read and wiki-update wrappers to operate on Confluence pages, rely on Confluence Storage Format for content integrity, and keep results as structured JSON to minimize main context overhead.

Yes. Shell wrappers must be available at ~/bin, and you'll need AGENT-INSTRUCTIONS.md configured to define sub-agent behavior. With these prerequisites in place, you can route Confluence operations—reading, updating, creating, and searching pages—through the delegation layer.

Delegation moves Confluence API interaction and processing logic to a specialized sub-agent, returning only concise structured results to your main context. This approach preserves content integrity via Confluence Storage Format while minimizing token usage in your primary assistant.

You can delegate wiki-read, wiki-update, wiki-create, wiki-search, and wiki-list-space operations. The sub-agent handles all interactions with Confluence pages in the OPS space, applying the Deli-Gator delegation pattern while producing structured JSON outputs for your workflow.