skills/beads-validation/SKILL.md
Validates beads issues after creation. Checks dependencies, PRD mapping, order, and issue quality. Use when: after creating issues, before TDD loop, before handoff. Triggers: "validate beads", "check issues", "verify tasks", "check quality", "validate handoff".
npx skillsauth add timequity/vibe-coder beads-validationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Validates that beads issues are correctly created and ready for TDD.
After creating issues (in rust-project-init):
Before TDD loop (in /ship Phase 2.5):
bd ready returns expected first task# Count features in PRD
grep -c "^###\|^-" docs/PRD.md | head -1
# Count issues created
bd list --status=open | wc -l
# Each MVP feature should have an issue
# List all dependencies
bd list --status=open --json | jq '.[] | .dependencies'
# Check each dependency ID exists
bd show {dep_id} # Should not error
# bd doctor checks for cycles
bd doctor
# Should have at least one ready issue
bd ready --limit=1
# If empty, something is blocked incorrectly
# All priorities should be 0-4
bd list --json | jq '.[] | .priority' | sort -u
# Check all open issues have required sections
python3 scripts/validate_beads.py --check-quality
Validates that issues are self-contained:
# After creating issues
python3 scripts/validate_beads.py --check-created --prd docs/PRD.md
# Before TDD
python3 scripts/validate_beads.py --check-deps --check-ready
# Check issue quality (for handoff)
python3 scripts/validate_beads.py --check-quality
# Full validation (all checks)
python3 scripts/validate_beads.py --all --prd docs/PRD.md
Output:
## Beads Validation
[PASS] PRD features: 4, Issues created: 4
[PASS] All dependency IDs exist
[PASS] No circular dependencies
[PASS] Ready queue has 1 issue (notes-abc)
[PASS] All 4 open issues pass quality check
[PASS] All priorities valid (0-4)
Result: 6/6 checks passed
Quality check failure output:
## Beads Validation
[WARN] 2/4 issues have quality problems
Quality issues:
task-abc:
- Description too short (45 chars, need 100+)
- Missing Acceptance Criteria section
task-xyz:
- Missing Files to Modify section
[FAIL] No issues ready to work on
Cause: All issues blocked by dependencies Fix: Check dependency chain, ensure at least one issue has no blockers
[WARN] PRD has 5 features, only 3 issues created
Fix: Create missing issues with bd create
[FAIL] Dependency notes-xyz does not exist
Fix: Check issue ID before bd dep add
[FAIL] Circular dependency: A → B → C → A
Fix: Remove one dependency to break cycle
[WARN] task-abc: Description too short (45 chars, need 100+)
[WARN] task-abc: Missing Files to Modify section
Fix: Use bd edit <id> --description and follow the template from beads-workflow/references/issue-template.md
Called automatically in:
rust-project-init.md → After creating issuesship.md → Phase 2.5: Before TDD loopbeads-workflow → Before handoff (Phase 5)development
Hidden quality gate that runs before showing "Done!" to user - ensures all tests pass, build succeeds, and requirements met before claiming completion
data-ai
Use when about to claim work is complete or fixed - requires running verification commands and confirming output before making any success claims
tools
Generate UI components from natural language descriptions. Use when: user asks for a page, component, or UI element. Triggers: "create page", "add component", "show form", "make button", "страница", "компонент", "форма".
content-media
10 ready-to-use themes with colors and fonts for consistent styling. Use when: applying visual themes to pages, components, or design systems. Triggers: "theme", "color palette", "color scheme", "fonts", "branding", "visual identity", "design system colors".