Workflow Architect

Maps complete workflow trees with failure modes, handoff contracts, and observable states into build-ready specs.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/tcvdog/agency-agents-hermes --skill workflow-architect-tcvdog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Workflow Architect
Source: https://github.com/tcvdog/agency-agents-hermes/tree/main/specialized/workflow-architect
Command: npx skills add https://github.com/tcvdog/agency-agents-hermes --skill workflow-architect-tcvdog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Systems fail in production because workflows are implied by code but never specified — branches, timeouts, partial failures, and cleanup paths go undocumented until they break. This Skill discovers every workflow in a codebase and produces exhaustive, build-ready workflow tree specifications before implementation begins. ## Core Features & Use Cases - Workflow Discovery Audit: Scans route files, workers, migrations, orchestration configs, and cron jobs to find workflows that exist in code but have no spec, flagging them as liabilities. - Four-View Workflow Registry: Maintains a cross-referenced registry organized by workflow, component, user journey, and entity state so anyone can look up system behavior from any angle. - Build-Ready Workflow Tree Specs: Produces structured specs covering happy paths, validation failures, timeouts, partial failures, concurrent conflicts, handoff contracts, cleanup inventories, and derived test cases. - Use Case: Before building a checkout feature, use this Skill to map every step from cart to payment confirmation — including what happens when the payment API times out at step 6 of 10, what the customer sees, and which resources must be rolled back. ## Quick Start Ask the agent to audit your repository and produce a workflow tree spec for a specific flow such as user signup, including all failure branches and handoff contracts.

Frequently Asked Questions about Workflow Architect

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

FAQPage Schema
How do I document system workflows before writing code?▼

Map the happy path end-to-end first, then branch every step for validation failures, timeouts, transient errors, and partial failures. Define handoff contracts with payload schemas and timeouts at each system boundary, and derive one test case per branch.

How to find undocumented workflows in an existing codebase?▼

Scan API route files, background workers, cron definitions, event listeners, database migrations, and infrastructure-as-code modules. Every endpoint, job type, and schema change implies a workflow — any workflow found in code without a spec is flagged as a liability.

What should a workflow specification include for QA testing?▼

A testable workflow spec includes actors, prerequisites, triggers, step-by-step trees with timeouts and failure outputs, state transitions, handoff contracts, a cleanup inventory, and a test case table where every branch maps to exactly one test case.

How do I handle partial failures in multi-step workflows?▼

Define an ABORT_CLEANUP section listing every resource created by the workflow and its destroy method, executed in reverse order of creation. Each step's failure output specifies whether it is retryable with backoff or routes directly to cleanup.

When should workflow specs be updated after deployment?▼

Update specs whenever code diverges from documented behavior, a failure reveals an unmapped branch, or a timeout exposes an under-budgeted step. Specs are living documents — silent drift between spec and reality is treated as a bug.