Faber Config Manager FAQs

Question 1

Can I exclude specific steps inherited from a parent workflow?

Accepted Answer

Yes, you can use the 'skip_steps' field in your project workflow to specifically exclude inherited step IDs that are not needed for your current context.

Question 2

How does workflow inheritance work in this skill?

Accepted Answer

Workflows can use an 'extends' field to inherit logic. The skill merges pre-steps, steps, and post-steps from the entire hierarchy, following a specific order from root ancestor to child.

Question 3

Why does this skill require deterministic scripts for merging?

Accepted Answer

Complex merge logic can be inconsistent when handled by LLMs alone. Using dedicated scripts ensures the inheritance chain is processed perfectly every time without skipping steps.

Question 4

What is the primary purpose of faber-config?

Accepted Answer

It manages the loading, validation, and merging of FABER configuration files and workflows, ensuring Claude has a clear, deterministic execution plan for development tasks.

Question 5

What configuration formats are supported?

Accepted Answer

The skill primarily manages JSON configurations (v2.0) but also includes legacy support for TOML configuration files via a legacy loader script.

Faber Config Manager

Key Features

Use Cases

Faber Config Manager

Key Features

Use Cases