@zibby/workflow-templates

Built-in workflow templates for Zibby.

This package was carved out of @zibby/core (≤ 0.4.6) so the engine ships without the scaffolding payload — @zibby/core is now ~5× lighter and the template catalog evolves independently.

What's inside

Three production-ready workflow templates:

| Template | Scaffolds for | Default slug | |---|---|---| | browser-test-automation | End-to-end browser tests driven by an AI agent + Playwright | browser-tests | | code-analysis | Ticket → code change → test-case generation | ticket-analyzer | | generate-test-cases | Diff → prioritized test specs | tests-from-diff |

Each template ships its own graph.mjs, node modules, prompts (where relevant), state.js (Zod schema), README and icon.

How it's used

The zibby CLI (@zibby/cli) is the primary consumer:

• zibby template list — enumerate available templates
• zibby template add <name> — copy into the current project's .zibby/
• zibby workflow new <slug> -t <name> — scaffold a deployable workflow

For programmatic use:

import { TemplateFactory } from '@zibby/workflow-templates';

const all = TemplateFactory.listTemplates();
const { template, graphPath, nodesPath } =
  TemplateFactory.getTemplateFiles('browser-test-automation');

Migrating from @zibby/core@<=0.4.6

If you import templates today via @zibby/core/templates/*, switch to @zibby/workflow-templates/* — the on-disk layout is preserved.

// before
import { TemplateFactory } from '@zibby/core/templates';
import '@zibby/core/templates/register-nodes.js';
import { buildAnalysisGraph } from '@zibby/core/templates/code-analysis/graph.js';

// after
import { TemplateFactory } from '@zibby/workflow-templates';
import '@zibby/workflow-templates/register-nodes.js';
import { buildAnalysisGraph } from '@zibby/workflow-templates/code-analysis/graph.js';

@zibby/core@>=0.5.0 no longer exports ./templates/*. @zibby/core is still a peerDependency of every template — they call into the engine via @zibby/agent-workflow.