beads-validation

Validate beads issues for PRD mapping, dependencies, readiness, and priorities.

6|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/timequity/plugins --skill beads-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads-validation
Source: https://github.com/timequity/plugins/tree/main/vibe-coder/skills/beads-validation
Command: npx skills add https://github.com/timequity/plugins --skill beads-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensures beads issues align with the PRD, dependencies are valid, and readiness is verified before TDD.

Core Features & Use Cases

  • PRD→Issues mapping validation
  • Dependency validation and circular dependency checks
  • Ready state and priority checks

Quick Start

Run the beads validation script to confirm PRD-to-issues mapping and readiness.

Frequently Asked Questions about beads-validation

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

FAQPage Schema
How do I validate beads issues against my PRD before starting TDD?

Beads validation checks that your issues map correctly to PRD requirements, dependencies exist and have no cycles, and at least one issue is ready. Run the validate_beads.py script after creating issues in rust-project-init to confirm PRD-to-issue coverage and readiness before the TDD loop.

What does beads validation check for circular dependencies?

Beads validation detects circular dependencies between issues using bd doctor and reports any cycles that would block the TDD workflow. It ensures your dependency graph is acyclic before proceeding to development.

When should I run beads validation in my workflow?

Run beads validation after creating issues with rust-project-init and before starting the TDD and ship phases. It verifies dependencies, PRD mapping, and readiness are correct so your workflow proceeds without blockers.

Can beads validation enforce priority constraints on issues?

Yes, beads validation enforces priority validity across your beads workflow, ensuring priorities are within the 1–3 range. This maintains priority consistency as you move through the TDD phase.

What happens if beads validation finds missing dependencies or PRD gaps?

Beads validation reports unmet dependencies and PRD-to-issue coverage gaps so you can fix them before TDD begins. It queries issues via bd list and inspects PRD.md to identify misalignments and missing mappings.

Do I need to manually check issue readiness, or does beads validation handle it?

Beads validation automatically confirms at least one issue is in ready state as part of its checks. You don't need manual verification—the script validates readiness as a functional requirement for proceeding.