core

Enforce spec-driven development with mandatory TDD and on-disk state management.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/BEE-CODED/bee-dev --skill core-bee-coded
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core
Source: https://github.com/BEE-CODED/bee-dev/tree/main/plugins/bee/skills/core
Command: npx skills add https://github.com/BEE-CODED/bee-dev --skill core-bee-coded

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a rigorous, spec-driven development workflow, ensuring code quality, test coverage, and user control throughout the development lifecycle.

Core Features & Use Cases

  • Mandatory TDD: Enforces writing tests before implementation (Red-Green-Refactor).
  • Disk-is-Truth: Critical project state is always persisted to disk (STATE.md, TASKS.md, config.json).
  • User Control: Prevents auto-commits and ensures user confirmation for all destructive actions.
  • Spec-Driven Development: Guides development strictly based on defined specifications and phase plans.
  • Phase Lifecycle Management: Orchestrates a structured workflow through planning, execution, review, testing, and committing.

Quick Start

Follow the TDD workflow by writing tests before implementation.

Frequently Asked Questions about core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce test-driven development in an automated software workflow?

To enforce test-driven development, this Skill mandates a strict Red-Green-Refactor workflow, requiring you to write tests before implementation. It governs agent behavior to prioritize code integrity throughout the development lifecycle.

What is spec-driven development and how does it manage project state?

Spec-driven development guides coding strictly based on defined specifications and phase plans. This Skill manages project state by persisting critical data to disk in files like STATE.md, TASKS.md, and config.json.

How do I prevent automated commits during a spec-driven development process?

To prevent automated commits during a spec-driven development process, this Skill enforces user control by blocking auto-commits and requiring explicit user confirmation for all destructive actions.

Can I use this TDD workflow without defining phase plans beforehand?

No, you cannot use this TDD workflow without phase plans. It orchestrates a structured lifecycle through mandatory planning, execution, review, testing, and committing phases, ensuring strict adherence to specifications.