agent-workflow-orchestrator

Orchestrate end-to-end QA workflows from requirements to Playwright implementation.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/swongsuddee/windflu-test --skill agent-workflow-orchestrator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-workflow-orchestrator
Source: https://github.com/swongsuddee/windflu-test/tree/main/.agents/toolkit/agent-workflow-orchestrator
Command: npx skills add https://github.com/swongsuddee/windflu-test --skill agent-workflow-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents slow, fragmented agent execution by coordinating the full end-to-end QA workflow (requirements to test implementation) while keeping project memory and hot-cache state consistent.

Core Features & Use Cases

  • Workflow orchestration for QA pipelines: Selects and sequences multi-skill agents to produce requirements, exploration diagrams, test designs, Playwright specs, and final reports.
  • Hot-cache and activity-log governance: Forces a hot-cache-first approach, updates cache after file changes, and appends an activity-log entry after every task.
  • Repository integration guardrails: Enforces commit/push policy via dedicated rules and avoids committing secrets or generated authenticated artifacts.
  • Diagram-to-test alignment workflow: Guides the conversion of exploration into Mermaid flow/state diagrams and then into Zephyr-style test design.

Quick Start

Use the agent-workflow-orchestrator to update the hot cache first, then run the canonical workflow chain to go from exploration through test implementation for the target feature key.

Frequently Asked Questions about agent-workflow-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate end-to-end QA workflows from requirements to Playwright implementation?▼

QA workflow coordination sequences skills to produce requirements, Mermaid diagrams, test cases, and Playwright specs while enforcing strict Git safety rules and deterministic hot-cache updates.

What is the best way to generate Mermaid flow diagrams and map them to test cases?▼

Converting exploration into Mermaid flow and state diagrams directly guides Zephyr-style test design, ensuring diagrams align with generated test cases before implementing Playwright specs.

Does this QA orchestration workflow enforce Git commit and push policies?▼

Repository integration guardrails enforce strict commit and push policies, preventing the committing of secrets or generated authenticated artifacts during QA workflow execution.

How do I manage hot cache and activity logs during automated test design?▼

Hot-cache governance forces a hot-cache-first startup, updates cache after file changes, and appends activity-log entries after every task to maintain deterministic project memory state.

Can I use this for website and API testing tasks with existing Playwright specs?▼

The workflow applies to website and API testing tasks where it selects provider-aware skills, produces diagrams, generates test cases, and validates Playwright specs in required workflow order.