workflow-entry

A unified workflow entry point consolidates routing logic for multiple intents like implement, build, and review into a single deterministic location. You need it to ensure consistent decision-making for target services and sandbox environments across all requests.

To route an implement request, the workflow-entry skill evaluates the input against defined policies and matrices. It then deterministically selects the appropriate sandbox mode and enforces any mandatory approval steps before execution begins.

Yes, you can enforce mandatory approval steps. The workflow routing integrates stop and approval controls directly into the entry logic, ensuring workflow progression pauses safely until required approvals are granted for tasks or builds.

Yes, workflow routing supports deterministic decisions for review and diagnose intents. The unified entry point ensures that the same input always yields the same routing and sandbox decisions, regardless of the specific intent being processed.

The best way to consolidate workflow entry points is using a unified routing skill that processes intents like implement, build, and task. This approach enforces stop and approval controls while deterministically selecting sandbox modes based on defined policies.

You should avoid a unified deterministic entry point if your workflows require highly dynamic, non-deterministic routing paths that cannot be defined by fixed policies and matrices, or if your intents do not need mandatory stop and approval enforcement.