eric-cielo/moflo / .claude/skills/fl
flo
VerifiedMoFlo ticket spell - analyze and execute GitHub issues
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.5 KB |
| epic.md | markdown | 2.1 KB |
| execution-modes.md | markdown | 4.4 KB |
| phases.md | markdown | 22.8 KB |
| sdd.md | markdown | 7.8 KB |
| spell-engine.md | markdown | 1.8 KB |
| ticket.md | markdown | 6.0 KB |
spell-engine.md
View on GitHub# Spell Engine Mode (-wf, --workflow)
When `-wf` is used, the /flo skill switches to the generalized spell engine
instead of the hardcoded coding process. This uses the `Grimoire` from
`cli/spells` to resolve and run YAML/JSON spell definitions.
## Scan Directories (in priority order)
1. Shipped: `src/cli/spells/definitions/` (bundled with moflo)
2. User: `spells/` and `.claude/spells/` (project-level overrides)
## Registry Behavior
- Each spell file defines `name` and optional `abbreviation` in frontmatter
- Registry builds lookup map: abbreviation -> file path, full name -> file path
- Duplicate abbreviations produce a collision error on load
- User definitions override shipped ones by name match
## Subcommands
`/flo -wf list` — List all available spells:
```
Use Grimoire.list() to get all registered spells.
Print a table: name | abbreviation | description | tier (shipped/user)
```
`/flo -wf info <name|abbreviation>` — Show spell details:
```
Use Grimoire.info(query) to get detailed info.
Print: name, abbreviation, description, version, source file, arguments, step count, step types
```
`/flo -wf <name|abbreviation> [positional-args] [--named-args]` — Execute a spell:
```
1. Use Grimoire.resolve(wfName) to find the spell
2. Map positional args to required arguments in order
3. Parse named args: --key=value or --key value
4. Use runSpellFromContent() or createRunner().run() to execute
5. Print step-by-step progress and final result
```
## Argument Mapping
- Positional args mapped to required arguments in definition order
- Named args: `--severity=critical` or `--severity critical`
- Boolean flags: `--autofix` (true if present)
- Example: `/flo -wf sa ./src --severity critical --autofix`
Maps to: `{ target: "./src", severity: "critical", autofix: "true" }`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |