agency-workflow-architect

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

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-workflow-architect-immamdouhaboammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-workflow-architect
Source: https://github.com/imMamdouhaboammar/Mimera/tree/main/.agents/skills/specialized-workflow-architect
Command: npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-workflow-architect-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Systems fail in production because workflows are never fully specified: undocumented branches, missing cleanup paths, undefined handoffs, and implicit assumptions cause bugs that only surface under failure. This Skill discovers every workflow in a codebase and produces exhaustive, build-ready specifications before code is written. ## Core Features & Use Cases - Workflow Discovery & Registry: Scans routes, workers, migrations, IaC configs, and cron jobs to find every workflow, then maintains a four-view registry (by workflow, component, user journey, and state) flagging undocumented flows as Missing. - Build-Ready Workflow Tree Specs: Produces structured specs covering happy paths, validation failures, timeouts, partial failures, concurrent conflicts, ABORT_CLEANUP procedures, handoff contracts with payload schemas, observable states, and derived test cases. - Spec vs Reality Auditing: Verifies specs against actual code, tracks assumptions explicitly, and coordinates with QA, security, and backend roles to close gaps. - Use Case: When designing an order checkout flow, use this Skill to map every step from cart submission to payment confirmation, define what happens if the payment gateway times out at step 4, and generate the cleanup inventory and test cases QA will automate. ## Quick Start Map the complete workflow tree for the user signup flow in this repository, including all failure branches, handoff contracts, and cleanup steps.

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 a workflow before writing code?

Start with a discovery pass over routes, workers, and migrations, then map the happy path end-to-end. Branch every step for validation errors, timeouts, and partial failures, define handoff contracts with payload schemas, and derive one test case per branch.

What should a workflow specification include for QA testing?

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

How do I find undocumented workflows in an existing codebase?

Scan API route files, background job processors, 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.

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

Define an ABORT_CLEANUP procedure listing every resource created, in reverse creation order, with its destroy method. Each step documents what was left in what state on failure, and the cleanup inventory guarantees no orphaned resources remain.

When should workflow specs be updated after deployment?

Update specs whenever code diverges from the documented behavior, a failure reveals an unmapped branch, or a timeout exposes an under-budgeted step. Specs are living documents with an audit log recording every reality-versus-spec finding.