flow-well-architected

Standardizes Salesforce Flow design using a nine-principle framework for architecture and documentation.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/cchrisv/professorFlowVisualPicker --skill flow-well-architected
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-well-architected
Source: https://github.com/cchrisv/professorFlowVisualPicker/tree/main/.agents/skills/flow-well-architected
Command: npx skills add https://github.com/cchrisv/professorFlowVisualPicker --skill flow-well-architected

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flow design can drift into monoliths and spaghetti, leading to maintenance pain and unreliable deployments. This guide provides a nine-principle framework to ensure well-architected Salesforce Flows that are scalable, modular, and observable.

Core Features & Use Cases

  • Establishes a structured framework across Foundation, Design, and Production-readiness layers.
  • Promotes modularity with subflows, cohesive organization, and clear naming conventions.
  • Embeds error handling, testability, and performance considerations into flow design.

Quick Start

Apply the nine principles to a Salesforce Flow to improve architecture and documentation.

Frequently Asked Questions about flow-well-architected

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

FAQPage Schema
How do I design a well-architected Salesforce Flow that avoids becoming a monolith?

A well-architected Salesforce Flow uses a nine-principle framework spanning Foundation, Design, and Production-readiness. Applying these principles ensures flows remain modular, scalable, and observable by enforcing consistent naming, clear documentation, and cohesive organization.

What is the best way to refactor spaghetti Salesforce Flows?

Refactoring spaghetti Salesforce Flows involves applying nine structural principles focused on modularity. You extract subflows, enforce consistent element naming, document decisions, and add robust error handling to transform tangled logic into a maintainable architecture.

When should I extract subflows in Salesforce Flow architecture?

You should extract subflows in Salesforce Flow architecture when building new flows or refactoring existing ones to achieve modularity. This practice organizes logic cohesively, improves performance, and enforces testability according to the nine well-architected design principles.

How do I add error handling and testability to a Salesforce Flow?

Adding error handling and testability to a Salesforce Flow requires applying the Production-readiness principles of the nine-principle framework. This approach embeds robust error handling mechanisms and planned test strategies directly into the flow design.

Does this nine-principle framework work for reviewing existing Salesforce Flow designs?

Yes, the nine-principle framework works for reviewing existing Salesforce Flow designs. It serves as a structured design-review checklist to evaluate architecture, verify naming conventions, check documentation, and identify areas needing subflow extraction or performance optimization.