kimchi:validate

Validate bead YAML files for executability with four distinct checks.

8|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Tromml/kimchi --skill kimchi-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kimchi:validate
Source: https://github.com/Tromml/kimchi/tree/main/plugins/kimchi/skills/validate
Command: npx skills add https://github.com/Tromml/kimchi --skill kimchi-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that generated task specifications (beads) are complete, clear, and executable, preventing downstream errors and wasted agent time.

Core Features & Use Cases

  • Automated Validation: Runs four distinct checks (Context Completeness, Deliverables Clarity, Test Specification, Isolation) on bead YAML files.
  • Self-Healing: Attempts to automatically enrich and fix failing beads through an iterative process.
  • Use Case: After generating a set of beads for a new feature, run this Skill to confirm they are ready for multi-agent execution, catching potential issues before they cause problems.

Quick Start

Use the kimchi:validate skill to validate all bead YAML files in the .beads directory.

Frequently Asked Questions about kimchi:validate

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

FAQPage Schema
How do I validate YAML task specifications for standalone executability?

This validation process runs four distinct checks—context completeness, deliverables clarity, test specification, and isolation—to confirm that bead YAML files contain all necessary information for standalone multi-agent execution.

What checks are needed to ensure generated beads are executable?

Executable bead validation requires four specific checks: context completeness, deliverables clarity, test specification, and isolation, which collectively prevent downstream errors and wasted agent time during task execution.

Can failing bead YAML files be fixed automatically during validation?

Yes, failing bead YAML files can be fixed automatically through a self-healing iterative process that enriches the beads up to a specified number of loops before flagging unrepairable ones for manual review.

How do I validate all bead YAML files in a project directory?

Running validation against the .beads directory processes all bead YAML files, applying four validators and generating a comprehensive report that flags any unrepairable beads for manual review.

What happens when a bead YAML file cannot be automatically repaired?

When automated enrichment loops fail to repair a bead YAML file, the validation process flags that bead as unrepairable in a comprehensive report, highlighting it for manual review and intervention.