Orlix Dynamic Workflows

Use when Orlix work benefits from explicit workflow packets, authorized subagent orchestration, or independent research, implementation, test, and review tracks.

rudironsoni 8affd3e 1.0 KB Updated

File contents

Orlix Dynamic Workflows

Use orchestration when work has independent tracks, crosses ownership boundaries, needs separate skeptical verification, or the user explicitly requests delegation. Do not spawn agents unless the user or current environment authorizes it.

Store reusable workflow mechanics in the owning skill and current packet state in structured task envelopes under Build/AgentHarness/. Record the required PR #228 recovery checkpoints in IMPLEMENT.md. Do not create parallel workflow journals or copied evidence logs.

Every packet names its objective, required canonical pages and reports, owning layer, allowed and forbidden scope, expected output, verification, and integration point. Keep packets disjoint, then verify the integrated result against the original objective and current structured evidence.

rudironsoni/orlix/tree/main/.agents/skills/orlix-dynamic-workflows commit 8affd3e2cd

Frequently asked questions

npx skillmds@latest add rudironsoni/orlix-dynamic-workflows