home / skills / oimiragieo / agent-studio / workflow-updater

workflow-updater skill

safe

This skill refreshes workflows safely by validating gates, ensuring idempotent transitions, and running regression tests.

npx playbooks add skill oimiragieo/agent-studio --skill workflow-updater

Review the files below or copy the command above to add this skill to your agents.

Files (10)

SKILL.md

1.1 KB

---
name: workflow-updater
description: Refresh existing workflows with phase-gate regression checks and idempotency validation.
version: 1.0.0
model: sonnet
invoked_by: both
user_invocable: true
tools: [Read, Write, Edit, Glob, Grep, Bash, Skill, MemoryRecord, WebSearch, WebFetch]
args: '--workflow <name-or-path> [--trigger reflection|evolve|manual]'
error_handling: graceful
streaming: supported
---

# Workflow Updater

Refresh existing workflows safely with explicit gate validation, transition integrity checks, and idempotency regression tests.

## Iron Law

No workflow refresh without proving gate correctness and idempotent phase progression.

## Core Steps

1. Resolve existing workflow file.
2. Research best-practice patterns (`research-synthesis`; optional `assimilate`).
3. Build RED tests for gate regressions and duplicate transition handling.
4. Apply minimal workflow updates.
5. Verify workflow validation + integration docs + registry references.

## Memory + Search

Use existing memory/search stack for evidence and record updated workflow learnings in memory files.

Overview

This skill refreshes existing workflows by adding phase-gate regression checks and idempotency validation to ensure safe transitions. It enforces that every workflow update proves gate correctness and that phases progress without creating duplicate or conflicting transitions. The goal is minimal, verifiable changes that reduce regressions and improve operational safety.

How this skill works

The skill first locates the target workflow and gathers evidence from memory and search to understand current patterns. It synthesizes best-practice patterns, builds regression tests that verify gate behavior and idempotent phase progression, and applies minimal updates. Finally, it runs validations against integration docs and registry references and records findings back into memory for future audits.

When to use it

When updating production workflows and needing guarded, test-backed changes.
When introducing new phase gates or modifying transition rules.
When regression risk exists for duplicate transitions or non-idempotent operations.
When you must document and verify workflow changes for compliance or audits.
When you want minimal-change updates with automated validation and evidence capture.

Best practices

Always create RED-style tests for gate regressions before changing workflow logic.
Prefer minimal, incremental edits rather than sweeping refactors to limit risk.
Validate idempotency by simulating repeated transitions and duplicate events.
Record research and post-change learnings in memory to support traceability.
Confirm integration docs and registry references are updated alongside code changes.

Example use cases

Add a new approval gate to an on-call escalation workflow while ensuring previous transitions still work.
Patch a CI/CD pipeline step to be idempotent after intermittent duplicate job triggers were observed.
Refresh an order processing flow to include explicit rollback gates and test regressions.
Harden a deployment workflow by verifying registry references and documentation consistency.

FAQ

How does the skill prove gate correctness?

By synthesizing patterns from existing workflows and creating regression tests that assert expected gate decisions under representative conditions.

What does idempotency validation include?

Simulated repeated transitions and duplicate-event handling checks to ensure the workflow reaches the same state without side effects.