using-documents

To route document tasks, the system inspects the requested output artifact and selects the narrowest matching child skill across Word, PDF, PowerPoint, and Excel formats. It uses boundary rules and children.json to ensure accurate, auditable handoffs to specialized workflows.

Handling multi-format document requests is best done via a control plane that evaluates the input and routes to the most specific child skill available. This prevents generic operations by enforcing a single primary child for the target format.

Document format routing keeps the original source artifact as a guide but prioritizes routing to the output artifact format. This avoids weak indirect work by shifting execution to the specialized child skill matching the desired output.

Yes, you need the relevant child skills installed. If no suitable child exists for the requested format, the router enforces a fallback and instructs you to install the appropriate specialized skill for the workflow.

Document routing processes one primary child at a time by selecting the most specific match for the requested output artifact. It does not perform generic operations or process multiple formats simultaneously, ensuring strict workflow boundaries.

Document workflows route to a generic handler when references/children.json lacks the correct boundary definitions or the specific child skill is missing. The system requires installed child skills to route to the narrowest correct format.