spec:beads

Automate dependency-aware task tracking for spec workflows with Git-backed persistence.

39|4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/martinffx/atelier --skill spec-beads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec:beads
Source: https://github.com/martinffx/atelier/tree/main/skills/spec%3Abeads
Command: npx skills add https://github.com/martinffx/atelier --skill spec-beads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads provides a command-line interface to manage tasks and epics with strict dependency tracking, ensuring work happens in the correct order and progress is visible in Git.

Core Features & Use Cases

  • Dependency-driven execution: bd ready surfaces only unblocked tasks, enabling teams to pick work with certainty.
  • Bottom-up enforcement: Entities → Repositories → Services → Routers to preserve architectural discipline.
  • Git-backed persistence: .beads/beads.jsonl records all tasks, statuses, and history across sessions.
  • Spec integration: /spec:plan creates epics and ordered tasks to drive spec-driven development.

Quick Start

Create your first Beads epic and tasks using /spec:plan feature to initialize a spec-driven workflow.

Frequently Asked Questions about spec:beads

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

FAQPage Schema
How do I track task dependencies for spec workflows in Git?

Track task dependencies for spec workflows in Git by using a command-line interface that records all tasks, statuses, and history in a .beads/beads.jsonl file. This ensures work happens in the correct order and progress remains visible across sessions.

How do I surface unblocked tasks ready for development?

To surface unblocked tasks ready for development, use the bd ready command. This dependency-driven execution feature filters tasks so teams can pick work with certainty and avoid dependency bottlenecks.

How do I create epics and ordered tasks for feature planning?

Create epics and ordered tasks for feature planning by running the /spec:plan command. This initializes a spec-driven workflow that drives discovery to delivery by mapping out tasks with strict dependency tracking.

Does dependency-aware task tracking enforce architectural layer order?

Yes, dependency-aware task tracking enforces bottom-up architectural layer order. It strictly sequences Entities, Repositories, Services, and Routers to preserve architectural discipline during feature execution.

What commands integrate with dependency-driven task execution?

Dependency-driven task execution integrates with /spec:plan, /spec:work, /spec:status, and /spec:complete commands. These commands support creating Beads epics, tracking progress, and finalizing spec-driven development workflows.