bp-intent-validate

Validate intent-mapping.yaml routing rules and 3VL semantics without modifying files.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/hiivmind/hiivmind-blueprint --skill bp-intent-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bp-intent-validate
Source: https://github.com/hiivmind/hiivmind-blueprint/tree/main/skills/_archived/bp-intent-validate
Command: npx skills add https://github.com/hiivmind/hiivmind-blueprint --skill bp-intent-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates an intent-mapping.yaml to ensure routing rules cover declared skills, handle fallbacks, and respect 3VL semantics, without modifying source files.

Core Features & Use Cases

  • Validates intent_flags, rules, and fallback presence.
  • Analyzes coverage, gaps, collisions, and 3VL semantics to surface informative issues.
  • Produces a structured, actionable validation report to guide repairs or improvements.

Quick Start

Run bp-intent-validate against your intent-mapping.yaml to generate a validation report for routing correctness.

Frequently Asked Questions about bp-intent-validate

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

FAQPage Schema
How do I validate an intent-mapping.yaml file for routing correctness?

To validate an intent-mapping.yaml for routing correctness, run a validation analysis that checks declared intent flags, rules, and fallback configurations, producing a structured report of issues and recommended fixes.

What does 3VL semantic analysis mean for intent mapping rules?

3VL semantic analysis for intent mapping rules evaluates three-valued logic conditions across your routing configuration, computing coverage, gaps, and collisions to surface informative conflicts without modifying source files.

How can I detect routing gaps and collisions in my intent-mapping configuration?

You can detect routing gaps and collisions in an intent-mapping configuration by analyzing 3VL semantics and rule coverage, which generates an actionable report detailing priority issues and recommended repairs.

Can I check intent flags and fallback presence without modifying my YAML source files?

Yes, you can check intent flags, rules, and fallback presence without modifying your YAML source files by running a read-only diagnostic analysis that outputs a structured validation report.

What issues should I look for when diagnosing intent-mapping.yaml routing failures?

When diagnosing intent-mapping.yaml routing failures, look for missing fallback configurations, uncovered intent flags, rule collisions, and 3VL semantic gaps, which a validation report prioritizes for repair.

Does intent-mapping validation require external dependencies or components?

Intent-mapping validation requires no external dependencies or components, directly analyzing your intent_flags, rules, and fallback configurations to output a standalone structured validation report.