BeeDev Core Workflow FAQs

Question 1

Can I use BeeDev Core with existing projects?

Accepted Answer

Yes, though it will require you to start with tests for any new changes or improvements you make to the existing code to satisfy the mandatory TDD requirements.

Question 2

How does the skill handle different AI models?

Accepted Answer

It uses smart model delegation, automatically assigning structured work like scanning and validation to faster models while reserving production code and deep reasoning for more powerful models.

Question 3

What makes the BeeDev Core workflow different from standard AI coding?

Accepted Answer

BeeDev Core enforces a 'TDD mandatory' rule where all production code must be preceded by a failing test. It also moves project state out of the chat history and onto the disk to ensure long-term consistency.

Question 4

Does BeeDev Core perform automatic Git commits?

Accepted Answer

No. One of the firm rules is 'No auto-commit.' The AI suggests commits, but the user must always review and trigger them manually to maintain full control over the codebase.

Question 5

How does the 'disk-is-truth' principle benefit my project?

Accepted Answer

By storing current specs, phase progress, and decisions in files like STATE.md and TASKS.md, the AI always has an accurate source of truth that doesn't get lost when the conversation window shifts.

BeeDev Core Workflow

Key Features

Use Cases

BeeDev Core Workflow

Key Features

Use Cases