approve-spec

Name: approve-spec
Availability: InStock
Author: .do

Convert approved specs from discovery.db into beads epics with task breakdowns.

2|3|Updated Jan 8, 2026

Search Tags:#automation #beads #epic #task #project-management #approve-spec

Ready to run

npx skills add https://github.com/dot-do/dotdo --skill approve-spec-dot-do

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: approve-spec
Source: https://github.com/dot-do/dotdo/tree/main/.claude/skills/approve-spec
Command: npx skills add https://github.com/dot-do/dotdo --skill approve-spec-dot-do

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Approve-spec provides a repeatable, auditable process to convert an approved specification into an executable beads workflow by creating an epic, task breakdown, dependencies, and agent labeling.

Core Features & Use Cases

Automates epic and task creation from a spec in discovery.db
Establishes dependencies, labels, and a concluding close-up checklist
Supports optional Test-Driven Development (TDD) pairings and metadata linking

Quick Start

Provide an approved specification to beads and the skill will generate the epic, tasks, dependencies, labels, and close-up checklist.

Frequently Asked Questions about approve-spec

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

FAQPage Schema

How do I convert an approved specification into a beads epic with structured tasks?▼

To convert an approved specification into a beads epic, identify a spec in review status within discovery.db. The workflow creates the epic, child tasks, dependencies, agent labels, and a close-up checklist, then exports metadata back to discovery.

Can I automatically link test tasks to implementation tasks in TDD mode?▼

Yes, when TDD mode is enabled, the task breakdown process enforces data integrity by automatically linking test tasks to their corresponding implementation tasks within the beads epic.

What dependencies are required to automate project management task creation from a spec?▼

You need a valid discovery.db containing an approved specification in review status. The workflow reads this entry to establish dependencies, labels, and batch task creation before updating the database accordingly.

Does the approve-spec workflow support batching creation for multiple tasks?▼

Yes, the specification conversion workflow batches task creation where possible to efficiently generate child tasks, dependencies, and agent labels for the beads epic.

Why does my specification need to be in review status to generate a beads epic?▼

The specification must be in review status to ensure data integrity. This validates that the spec is approved and ready before converting it into a beads epic with linked metadata exported back to discovery.db.