agency-workflow-architect

Designs exhaustive workflow tree specs covering branches, failure modes, handoff contracts, and cleanup paths.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/sammysparks000/skillshare --skill agency-workflow-architect-sammysparks000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-workflow-architect
Source: https://github.com/sammysparks000/skillshare/tree/main/skills/specialized-workflow-architect
Command: npx skills add https://github.com/sammysparks000/skillshare --skill agency-workflow-architect-sammysparks000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Systems break in production because workflows are never fully specified — implicit flows live only in code, failure branches go undocumented, and handoffs between services lack defined contracts. This Skill discovers every workflow in a codebase and produces build-ready specs that engineers can implement against and QA can test against. ## Core Features & Use Cases - Workflow Discovery & Registry: Scans routes, workers, migrations, IaC configs, and cron jobs to find undocumented workflows, then maintains a four-view registry (by workflow, component, user journey, and state). - Build-Ready Workflow Tree Specs: Produces structured specs covering happy paths, validation failures, timeouts, partial failures, concurrent conflicts, observable states, handoff contracts, and cleanup inventories. - Test Case Derivation: Converts every branch in the workflow tree into a test case so QA can generate complete automated test suites without clarifying questions. - Use Case: Before building a checkout feature, use this Skill to map the full order workflow — including payment timeout recovery, partial-failure rollback, and what the customer and operator see at each state — so implementation and testing proceed without guesswork. ## Quick Start Ask the agent to audit this repository and produce a workflow registry plus a full workflow tree spec for the user signup flow.

Frequently Asked Questions about agency-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 first, then branch every step for validation failures, timeouts, transient and permanent 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 consumers, 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 Missing in the registry.

What should a workflow specification include for QA testing?▼

A testable workflow spec includes actors, prerequisites, triggers, per-step inputs and outputs with failure modes, observable states for customer and operator, cleanup inventory, and a test case table where every branch maps to exactly one test case.

Does this Skill write implementation code for the workflows?▼

No, it defines required behavior only — what must happen at each step, failure recovery, and handoff contracts. Implementation decisions are left to backend engineers, keeping the spec independent of any specific framework or language.

How are partial failures and rollback handled in a workflow spec?▼

Each spec includes an ABORT_CLEANUP section listing actions in reverse order of resource creation, plus a cleanup inventory table mapping every created resource to its destroy method. This prevents orphaned resources when a mid-workflow step fails.