spell-builderlisted

# Spell Builder Purpose: produce production-ready spell definitions (YAML/JSON) that compose step commands and connectors into end-to-end automated spells, with proper data flow, validation, and engine integration. ## Read First — Companion Files | File | When to read | |------|--------------| | [architecture.md](architecture.md) | **Always** — three-layer model (spell → step → connector); putting logic in the wrong layer is the most common mistake | | [permissions.md](permissions.md) | When defining or editing any step — required disclosure & dry-run report format | | [preflight.md](preflight.md) | When the step depends on runtime state (clean git tree, logged-in CLI, reachable host) | ## Prerequisites - MoFlo project with `cli/spells` package - Familiarity with YAML syntax ## Quick Start Ask the user: > **What would you like to do?** > 1. **Create** a new spell definition from scratch > 2. **Edit** an existing spell definition > 3. **Discover** available step commands and connectors > 4. **Validate** an existing spell file Then follow the appropriate section below. --- ## Section 1: Create a New Spell ### Step 1: Gather Spell Metadata | Field | Required | Example | |-------|----------|---------| | **Name** | Yes (kebab-case) | `deploy-staging`, `security-audit` | | **Description** | Recommended | `Deploy to staging with smoke tests` | | **Version** | Optional (default `1.0`) | `1.0` | | **Abbreviation** | Optional | `ds` (short lookup key for `/flo -wf ds`) | |