writing-flows

Explain Flow DSL syntax and agent authoring patterns for ADHD Framework .flow files.

Updated Feb 1, 2026

Search Tags:#workflow #agent #patterns #syntax #flow #imports #dsl

Ready to run

npx skills add https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3 --skill writing-flows

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-flows
Source: https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3/tree/main/modules/dev/instruction_core/data/skills/writing-flows
Command: npx skills add https://github.com/AI-Driven-Highspeed-Development/adhd_framework_v3 --skill writing-flows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Flow DSL syntax and agent authoring patterns for the ADHD Framework. Covers node definition (@node_id), pipe operators (|param=value|), content blocks (<<<>>>), variable references ($backward, ^forward), imports (+./path.flow), style parameters, .flow + .yaml sidecar pattern, shared _lib/ fragments, and the adhd r -f refresh command. Use this skill when creating or editing .flow files, building new agents, or understanding Flow compilation.

Core Features & Use Cases

Flow DSL syntax and patterns to design and orchestrate agent behavior in ADHD Framework.
Guidance on authoring .flow files and corresponding .yaml sidecars, including imports, style parameters, and modular fragments.
Real-world workflows for building new agents and understanding Flow compilation results.

Quick Start

Draft a new agent flow from a template and compile it with the ADHD refresh step.

Frequently Asked Questions about writing-flows

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

FAQPage Schema

How do I define nodes and use pipe operators in a .flow file?▼

Nodes in a .flow file are defined using the @node_id syntax, while pipe operators apply parameters using the |param=value| format. This Flow DSL syntax structures agent behavior and passes configuration directly to specific nodes.

What is the .flow and .yaml sidecar pattern for building agents?▼

The .flow and .yaml sidecar pattern separates agent logic from configuration. The .flow file contains DSL syntax and node definitions, while the .yaml sidecar manages style parameters and metadata, enabling modular and scalable agent authoring.

How do I import shared fragments and reference variables in Flow DSL?▼

Flow DSL imports shared fragments using the +./path.flow syntax from a _lib/ directory. Variable references pass data between nodes using $backward for previous outputs and ^forward for downstream values.

How do I compile and refresh a drafted agent flow in the ADHD Framework?▼

You compile and refresh drafted agent flows by running the adhd r -f refresh command. This processes the .flow source files, resolves imports, and translates the Flow DSL into executable ADHD agents.

Can I use content blocks to define multi-line text within a Flow DSL node?▼

Yes, content blocks enclosed in <<<>>> delimiters define multi-line text or logic within a Flow DSL node. This syntax allows you to embed complex instructions and structured data directly inside your agent definitions.

What are the limitations of using Flow DSL for agent orchestration?▼

Flow DSL is specifically tailored for the ADHD Framework, meaning it requires the adhd r -f refresh command to compile and cannot run independently outside its compilation pipeline. It functions best when paired with .yaml sidecars to manage style parameters.