Skip to main content
Playbooks are domain-specific instructions that load into the agent’s system prompt when the task matches a domain. While SOUL.md defines WHO the agent is, playbooks define HOW it approaches specific types of work. Personas are the user-facing way to activate a playbook — use --persona to start a session with a specialized mindset.

Personas

Use the --persona flag to run Fliiq as a specialized agent:
The persona stays active for the entire session (REPL/TUI) or the single-shot command.

Built-in Personas

Fliiq ships with four personas:

Auto-Detection

When no --persona flag is given, Fliiq automatically detects which playbook to load based on keywords in your prompt. If 2+ keywords match a playbook, it activates. Examples:

Creating Custom Personas

This scaffolds .fliiq/playbooks/devops.md from a template. Edit the file to add your instructions.

Keywords

The # Keywords: line defines when the playbook activates automatically:
When 2+ of these keywords appear in your prompt, the playbook loads. You can also activate it explicitly with --persona devops.

Content

The rest of the file is free-form markdown instructions the agent follows:

Playbooks in Jobs

Scheduled jobs can load a playbook directly via the playbook: field in job YAML. This lets a job run with specialized domain instructions without requiring a --persona flag at the command line:
Any bundled or custom playbook name works. The playbook loads into the job’s system prompt the same way --persona does in interactive mode.

Playbook Resolution

Custom playbooks with the same name override bundled ones. Custom playbooks with new names are additive.