Spec-driven development

Configurable workflows enforce spec requirements

Create custom workflows that block the AI from coding until documentation is complete. Define your own requirements—architecture diagrams, ERDs, API contracts, test plans.

Get started Design workflows →

Validation timeline — Validation feedback

Visual workflow editor

Create and edit workflows without code

Spec-state gating

Tasks move through draft → spec_in_progress → spec_ready. AI can't code until spec_ready.

Conditional requirements

Requirements activate based on keywords, file patterns, component types. Frontend tasks require mockups, backend tasks require observability notes.

Custom validation

Write JavaScript validators to check note content, checklist items, linked entities. Full programmatic control.

Multiple workflows

Built-in workflows for features, bugs, research. Create custom workflows for any process—even non-code tasks.

Reusable bundles & status transitions

Guide the AI with human-authored prompts and gated checkpoints

Validation bundles

Group required sections, checklists, rules, and subtasks into reusable bundles like spec_ready_checklist. Reference the same bundle while drafting the spec, or when moving a task into implementation.

Status flows

Define ordered transitions (e.g. spec_ready → in_progress) once, reuse them across every task type. The global status catalog and flow library keep names consistent, and the mapping UI lets you assign both a workflow and a flow per task type.

Transition prompts & gates

Add pre- and post-transition prompts to nudge the AI (“Double-check unit tests before reviewing”). Require acknowledgement tokens to block the status change until the agent confirms its work.

Validation phases

Attach auto-generated checklists to critical transitions. When a gate fires, Felix can drop checklist items (“Write ERD”, “Capture regression tests”) onto the task before the status change completes, so nothing slips through.

Manual snapshots

Workflows stay project-local. Export/import snapshots to keep them backed up or share with teammates:

felix workflows export --project /path/to/repo \ 
  --file .felix/workflows.snapshot.json

felix workflows import --project /path/to/repo \
  --file ./workflow-template.json

The UI exposes the same controls in the System Settings → Workflow Snapshots panel.