agency-workflow-architect

Name: agency-workflow-architect
Availability: InStock
Author: anavvanzin

Identify and document workflow paths from code, migrations, and configurations.

Updated Apr 15, 2026

Search Tags:#workflow #design #architecture #handoff #registry #spec

Ready to run

npx skills add https://github.com/anavvanzin/Research --skill agency-workflow-architect-anavvanzin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agency-workflow-architect
Source: https://github.com/anavvanzin/Research/tree/main/cowork/integrations/antigravity/agency-workflow-architect
Command: npx skills add https://github.com/anavvanzin/Research --skill agency-workflow-architect-anavvanzin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify, document, and aggregate implicit workflows across code, infrastructure, and configurations, turning tacit knowledge into explicit, testable specs that reduce risk and accelerate delivery.

Core Features & Use Cases

Discovery-driven workflow mapping: Read code routes, background jobs, migrations, and orchestrations to surface every workflow entry point.
Four-view registry: Maintain a living registry with views by workflow, component, user journey, and state to ensure full traceability.
Build-ready specs: Produce structured, implementation-agnostic workflow trees that engineers, QA, and operators can rely on.
Reality Checker integration: Validate spec against actual code and surface gaps for remediation.

Quick Start

Begin with a discovery pass to locate all entry points (routes, workers, migrations) and assemble the first workflow spec for a chosen path.

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 implicit workflows hidden across code and infrastructure configurations?▼

Document implicit workflows by inspecting code routes, background jobs, migrations, and configurations to surface every entry point, turning tacit infrastructure knowledge into explicit, testable workflow specs.

What is a four-view workflow registry and how does it map user journeys?▼

A four-view workflow registry maps workflows by name, component, user journey, and state, ensuring full traceability across your codebase and producing structured, implementation-agnostic workflow trees for engineering teams.

How do I generate build-ready workflow specs from existing codebases?▼

Generate build-ready workflow specs by running a discovery pass to locate all entry points like routes and workers, then assembling structured workflow trees that engineers, QA, and operators can rely on for delivery.

Can I verify documented workflow specs against actual code to find gaps?▼

Yes, you can verify documented workflow specs against actual implemented code using Reality Checker integration, which validates accuracy and surfaces gaps for remediation to prevent hidden risks.

What's the best way to prevent hidden risks in complex software workflows?▼

Prevent hidden risks by identifying and documenting every workflow path through code inspection and applying a four-view registry approach, which surfaces implicit workflows and aggregates them into testable specs.

Does this workflow architecture mapping require any external dependencies?▼

No, this workflow architecture mapping requires no external dependencies, allowing you to directly inspect code, migrations, and configurations to identify workflow paths and produce build-ready specs.