fabro-create-workflow

name	fabro-create-workflow
description	Use when the user wants to create or evolve a Fabro workflow package for a repo. Triggers on requests to write `.fabro` or `.toml` files, map repo work into units and lanes, synthesize a full `fabro/` package from broad requirements, or evolve an existing `fabro/` tree against doctrine and run evidence.

Fabro Create Workflow

Turn requirements into a Fabro workflow package: a .fabro graph, a .toml run config, and, when Raspberry supervision is involved, the repo-level contract that lets the supervisory plane understand what the workflow owns.

When the request is broad or repo-shaped, do not jump straight to isolated files. Use a blueprint first, then create or evolve the full checked-in fabro/ package from that blueprint.

If the request is Raspberry-shaped, answer the repo question first:

• what unit and lane exist?
• what milestone does the lane own?
• which artifacts prove that milestone?
• which checks or state files will the supervisor read?
• which run config path should the manifest point at?

Do not jump straight to graph syntax if those answers are missing.

Start

1. Run fabro model list before naming models or providers.
2. Classify the request:
   • Plain Fabro workflow authoring: read references/dot-language.md, references/run-configuration.md, and references/example-workflows.md.
   • Raspberry-supervised repo or lane authoring: also read references/raspberry-authoring.md and references/raspberry-examples.md.
   • Broad repo bootstrap or repo update request: also read references/program-synthesis.md, references/program-interview.md, references/program-blueprint-schema.md, and .