beo-validating

Validate feature plan integrity across contracts, dependencies, and spike coverage before execution.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/minhtri2710/skills --skill beo-validating
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beo-validating
Source: https://github.com/minhtri2710/skills/tree/main/skills/beo/validating
Command: npx skills add https://github.com/minhtri2710/skills --skill beo-validating

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validating is the critical gate between planning and execution. No code is written until this skill completes successfully.

Core Features & Use Cases

  • Phase contract verification ensures entry/exit conditions and a proven demo story exist.
  • Story-map and bead coherence checks confirm the internal build order and dependencies.
  • Plan health checks include CONTEXT.md, plan.md, and story-map.md for alignment and spike coverage of HIGH-risk items.

Quick Start

Validate the current epic plan to ensure phase, stories, and beads are ready for execution.

Frequently Asked Questions about beo-validating

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

FAQPage Schema
How do I validate feature plan soundness before execution?

Plan validation checks structural integrity by verifying phase contracts, story maps, decisions, and bead dependencies. This ensures CONTEXT.md, plan.md, and story-map.md are coherent before any code is written.

What is phase contract verification in epic planning?

Phase contract verification confirms that entry and exit conditions are met and a proven demo story exists. It prevents execution of epics lacking observable exit-state readiness.

How do I check story-map and bead dependencies for coherence?

Bead and story-map coherence checks validate the internal build order and dependencies against plan artifacts. This confirms all bead descriptions align before execution begins.

When do I need spike coverage for high-risk plan items?

Spike coverage for high-risk items is required during plan health checks to prevent late-stage failures. Validation enforces this coverage before execution proceeds on any epic.

What are the limitations of validating plan artifacts without CONTEXT.md?

Validating without CONTEXT.md breaks coherence verification, as alignment between CONTEXT.md, plan.md, and story-map.md is required. Missing it risks late-stage execution failures.