Brandedflow systems

Skill: Systems

install

source · Clone the upstream repo

git clone https://github.com/JenCW/brandedflow

manifest: client-delivery-factory/systems/skill.md

source content

Skill: Systems

Purpose

Integrate CRM, lead capture, automations, email, SiteSignal, and nurture into one coherent, testable systems layer for the client. Execution uses Node runner, MCP (

POST https://brandedflow.onrender.com/run

), and n8n on Render — never one-off scripts that bypass the registry.

Goal

Execute deterministic systems workflow and write only under

clients/{client_id}/systems/

(plus directive-driven updates to Airtable via MCP).

Steps

Validate systems input contract (
```
client_id
```
, purchased tracks, base IDs).
Run systems executor actions via approved executor router (factory runner → MCP / n8n).
Verify outputs against systems eval checks.
If verification fails, run systems refine once.
Return verified outputs for write to
```
clients/{client_id}/systems/
```
.

Constraints

No direct external execution from this skill except through approved paths in
```
foundation/directives/
```
and
```
foundation/registries/
```
.
No client-specific workflow duplication in code — parameterize by
```
client_id
```
+ profile.

Related modules

```
crm/
```
— lead capture focus
```
email-marketing/
```
,
```
sitesignal/
```
,
```
nurture/
```
— vertical slices that may compose into systems

See

systems/README.md

for plain-English scope.