atelier-spec-beads

Manage dependency-aware tasks for spec-driven workflows with Git-backed persistence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dependency-aware task tracking for software projects, enabling teams to define tasks, organize them into epics, and enforce execution order via dependencies, with persistent state across sessions through Git.

Core Features & Use Cases

  • Spec-driven workflow integration: automatically creates and updates beads epics and tasks from spec plans.
  • Bottom-up dependency enforcement: ensures Entity -> Repository -> Service -> Router progression.
  • Git-backed persistence: stores tasks in .beads/beads.jsonl and preserves history.
  • Spec integration: supports /spec:plan, /spec:work, /spec:status, and /spec:complete patterns.

Quick Start

Initialize Beads in your project and create an epic with dependent tasks in dependency order.

Frequently Asked Questions about atelier-spec-beads

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

FAQPage Schema
How do I manage dependency-aware tasks in a spec-driven workflow?

You manage dependency-aware tasks by organizing them into epics and enforcing execution order through bottom-up dependencies, ensuring progression from Entity to Repository to Service to Router layers with Git-backed persistence.

How does git-backed persistence work for task tracking?

Git-backed persistence for task tracking works by storing state in a .beads/beads.jsonl file, which preserves task history and maintains data across sessions for spec-driven workflows.

Can I integrate spec commands like /spec:plan and /spec:work with task tracking?

Yes, spec commands including /spec:plan, /spec:work, /spec:status, and /spec:complete integrate directly to automatically create and update beads epics and tasks from spec plans.

What is the best way to enforce bottom-up dependencies across software layers?

The best way to enforce bottom-up dependencies across software layers is by structuring tasks to follow an Entity to Repository to Service to Router progression, ensuring foundational layers are completed before dependent ones.

Do I need git to use beads for spec-driven task tracking?

Yes, Git is required because the system uses git-backed persistence to store task states in .beads/beads.jsonl and preserve history across sessions for spec-driven workflows.