Workflow Authoring

Workflow authoring

Load this skill when workflow JavaScript changes. Running an existing workflow needs no authoring reference.

Choose a branch

Read only what the task needs:

• Write or edit: start with runtime. Add pattern selection for topology, lifecycle for limits or resume, and focused recipes for the matching concern.
• Helper task: read quality helpers only for verify or judgePanel, the retry helper only for retry, and specialized helpers only for completenessCheck, loopUntilDry, gate, or checkpoint.
• Review: use the review checklist, plus only the matching quality or specialized helper contracts.
• Debug: use the debugging map.
• Routing: read registry ownership before using model, tier, phase models, or agentType; use environment-specific names only when context supplies them.
• Exact lookup or portability: start with the generated capability index. Follow its exhaustive-facts pointer only for constraints or support boundaries. Use versions when moving scripts between installations.

Invariants

• Start with literal export const meta = { name, description }; declare phases as an array of used { title } objects and enter each named phase.
• Call agent() at least once, give every call a short unique label, and return plain JSON data explicitly.
• Pair ordered results with stable work IDs before filtering. When one agent consumes another's selected result, include both its stable ID and actual data in the downstream prompt. Treat recoverable null as missing coverage and report it.
• Bound fan-out, loops, retries, agents, and concurrency to the task. Treat invocation-level token and time caps as opt-in user constraints, not defaults.
• Use log() for new code; console is compatibility-only.
• Write plain JavaScript without imports or filesystem modules. Pass nondeterminism through args; Date.now(), Math.random(), and no-argument new Date() are unavailable.