approve-spec

Convert approved specifications into Beads epics with tasks and dependencies.

27|3|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/JeremyKalmus/parade --skill approve-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: approve-spec
Source: https://github.com/JeremyKalmus/parade/tree/main/.claude/skills/approve-spec
Command: npx skills add https://github.com/JeremyKalmus/parade --skill approve-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Approving a specification is only the first step; this skill automates turning a reviewed discovery into an actionable beads epic with tasks, dependencies, and agent labels so work can proceed without manual coordination.

Core Features & Use Cases

  • Epic creation from an approved spec, including a descriptive title and status tracking
  • Task breakdown generation with dependencies and agent labeling for each task
  • Exporting the discovery results back into beads and updating discovery records for traceability

Quick Start

Use /start-discovery to review a spec, then run /approve-spec <spec-id> to export it as an epic. Open Parade to monitor the epic and its tasks and start /run-tasks when ready.

Frequently Asked Questions about approve-spec

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

FAQPage Schema
How do I export an approved spec to Beads as an epic?

To export an approved spec to Beads, run the /approve-spec command with your spec ID. It automatically generates a Beads epic with task breakdowns, dependencies, and agent labels for execution.

What is the best way to convert a discovery spec into actionable tasks?

Converting a discovery spec into actionable tasks is done by exporting it as a Beads epic. This process automatically generates task dependencies, applies agent labels, and updates discovery records for traceability.

Do I need to run a discovery review before exporting a spec to Beads?

Yes, you need to review a spec in discovery first. You use /start-discovery to review the specification, then run /approve-spec <spec-id> to export the approved discovery results as an epic.

How does task dependency and agent labeling work when creating a Beads epic?

Task dependency and agent labeling apply automatically during epic creation. The export process links agents and statuses to each generated task, ensuring the Beads epic is ready for execution without manual coordination.

Can I track the status of an epic after exporting a spec to Beads?

Yes, you can track epic status in Parade. After exporting your approved spec and creating the epic with its tasks, open Parade to monitor progress and run /run-tasks when ready for execution.