One-click install
npx skills add https://github.com/ships/eden --skill btb-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: btb-workflow
Source: https://github.com/ships/eden/tree/main/assets/claude/skills/btb-workflow
Command: npx skills add https://github.com/ships/eden --skill btb-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

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.

Frequently Asked Questions about btb-workflow

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

FAQPage Schema
How do I enforce documentation updates before git commits in human-AI collaboration?

To enforce documentation updates before git commits, use a pre-commit validator that checks for SPECS/PROGRESS.md modifications, ensuring humans and AI maintain a shared reality by making documentation the single source of truth.

What is a documentation-first workflow for iterative software engineering?

A documentation-first workflow requires planning via SPECS/README.md and mandatory PROGRESS.md updates before commits, preventing human-Ai drift by making documentation the single source of truth during phased implementation.

How do I manage design to MVP implementation across multiple development phases?

Manage design to MVP implementation by maintaining long-lived DESIGN and MVP documents while executing phased implementation with a feedback loop that adjusts scope or requests human input during iterative development.

Does the progress tracking workflow require a specific repository structure?

Yes, progress tracking requires a SPECS/ directory containing README.md and PROGRESS.md, and supports optional DESIGN/MVP documents for design refinement and phased implementation on claude/ branches.

What validations are required for progress tracking on claude/ branches?

Validations for progress tracking on claude/ branches include verifying PROGRESS.md modification, checking the current report date, confirming branch match, and validating session metadata to maintain shared reality.

When should I not use a documentation-driven development workflow?

Avoid documentation-driven development workflows for repositories lacking a SPECS/ directory or projects without iterative phased implementation, as the mandatory PROGRESS.md updates and pre-commit validations require this structure to function.