Workflow

Skill alirezarezvani/gaios/.claude/skills/workflow

Open-source AI Operating System (AIOS) blueprint for Claude Code & Codex — turn any agent into your personal second brain + Chief of Staff: skills, self-verifying workflows, a second-brain wiki, and deterministic tools. Fork it for any role or domain.

Install

npx -y skills add alirezarezvani/gaios --skill workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Use to run a dynamic, goal-driven workflow — orchestrate a multi-step goal by composing skills, tools, and MCPs, with a quality gate and verification at each step. Trigger on "/workflow", "run the <name> workflow", "orchestrate X", or a multi-step recurring goal ("draft the investor update", "give me my morning brief"). Follows references/sops/dynamic-workflows.md and the wf-*.md cards. Respects the autonomy/cadence gate (auto on reversible/internal, draft-then-approve on external/regulated).

SKILL.md

2.4 KB, 466 tokens by cl100k_base, as published. Nobody here has run it

Workflow — run a dynamic workflow

Orchestrate a goal end-to-end: plan → route → compose skills/tools/MCPs → gate each step → verify → fail safe. The engine for speed + quality. Pattern: references/sops/dynamic-workflows.md. Named workflows: references/sops/wf-*.md.

How to run

Resolve the goal. Named workflow (/workflow investor-update) → load its wf-*.md card. Free-form goal → first run /structure to get Context · Outcome · Goal · Success criteria, then plan the steps.
Check the autonomy gate per step. Internal/reversible/no-PHI → may run unattended. External/irreversible/regulated → stop and have the user approve (draft-never-send; never to a sensitive recipient without approval).
Execute step by step. For each: run the action (a /skill, a tools/*.py, or an MCP call) → run its gate/verify check → branch on the result (e.g. missing data → flag + ask, don't guess). Reuse existing capabilities; don't rebuild.
Fail safe. On error: read it, retry/repair if trivial, else escalate to the user with what's blocked. Never silently drop a step.
Verify done. Confirm the success criteria are met (evidence, not assertion) before reporting complete.
Deliver. Internal → your sanctioned cloud / chat. External → draft to the user. Log meaningful decisions to decisions/log.md.

Build / refine a workflow

New recurring multi-step goal that composes ≥2 capabilities and has a definable "done"? Author a references/sops/wf-<name>.md card (format in dynamic-workflows.md) and add it to the inventory. Don't workflow-ify one-offs (Simplicity). Don't overwrite a workflow card without asking.

Guardrails

All of CLAUDE.md. Especially: the autonomy gate per step, quality gate before "done", cite-don't-invent, no confidential data persisted, draft-never-send external.