What problem does it solve?
BTB workflow prevents humans and AI from drifting out of sync by making documentation the single source of truth and requiring PROGRESS.md updates before any commit.
Core Features & Use Cases
- Documentation-driven development: Start from SPECS/README.md and follow the intended reading order so every participant knows what to do next.
- Mandatory progress tracking: Update SPECS/PROGRESS.md before committing, with checks for report date, branch, and (on claude/ branches) session ID.
- Design → MVP → phased implementation loop: Keep DESIGN and MVP long-lived while implementation proceeds in phases with a feedback loop that can adjust scope or request human input.
Use this when you collaborate in a repository that has (or will add) a SPECS/ directory with README.md and PROGRESS.md and supports iterative development across multiple phases.
Quick Start
Run the BTB pre-commit validator to ensure PROGRESS.md is updated before you commit in the current repository state.