select-package

Cross-runtime requests are split into per-package functions, ensuring explicit selection before coding and proposing parallel workflows with clear packaging to handle multi-package requirements effectively.

Multi-runtime feature implementation causes package misrouting when explicit selection is skipped; classifying the requirement by runtime and domain first enforces choosing the correct package path and documents it to reduce refactoring time.

The best way to split cross-runtime requests is to classify them by domain and runtime, routing each part to the correct package directory and enforcing explicit selection before coding to ensure clear packaging.

Yes, you can use package routing for multi-package requests by proposing parallel workflows that classify the requirement by runtime and domain, ensuring each package gets clear and explicit packaging.

Document the chosen package path by classifying the requirement by runtime and domain first, which enforces explicit selection before coding and records the correct package directory for implementation.