orch-dynamic-workflow

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

Apply [architecture](../../docs/architecture.md) in the top-level coordinator. Explicit workflow or primitive selections own the process; never wrap or replace them. Children follow their assignments without starting this workflow.

Use core `orchflows` guidance for planning and applicable [core task guidance](../../guidance/) for work and review, without library extensions. User and repository instructions still apply; task sources remain evidence. Planning itself needs no authoring review.

Establish the result and checks. Before dependent work, gate each joined result with independent review unless a mistake would be cheap to undo or your checks would catch any consequential one; checks the maker writes share its reading of the requirements. Say why you skipped a gate. Unavailable reviewers do not make work trivial.

Briefly plan coherent units, dependencies, guidance, gates, bounds and stopping conditions. Preserve component contracts; an existing review counts only when candidate, criteria and scope match. Planning grants no new resource allowance.

Run independent assignments concurrently through [orch-work](../orch-work/SKILL.md), with clear ownership. Do clear work directly when settings permit. Join required outcomes before review and dependent work; adapt within declared gates and bounds.

At each gate, use [orch-review](../orch-review/SKILL.md) once on the stable joined candidate with requirements, sources and all applicable task guidance. After its completed report, make at most one necessary repair pass, honoring settings and scope. Apply architecture's review, checks and handoff rules; add no second review or automatic approval pause.

When asked to create or save reusable workflows or guidance, apply [orch-build-workflow](../orch-build-workflow/SKILL.md). Its authoring review satisfies that unit's gate without a wrapper review. Return results, checks and gaps, distinguishing reviewed from delivered states.

From DanMcInerney/orchflows, MIT.

More from DanMcInerney/orchflows