with one click
beo-validate
// Use this skill to decide execution readiness and select the approved execution set. Use when artifacts need readiness verification, not content edits. Do not use when artifact content edits or execution are required.
// Use this skill to decide execution readiness and select the approved execution set. Use when artifacts need readiness verification, not content edits. Do not use when artifact content edits or execution are required.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | beo-validate |
| description | Use this skill to classify readiness and select the next legal execution or repair path. Use when requirements and plan exist, but readiness, approval, execution set selection, remediation classification, or user-blocker classification is needed. Do not use when implementation, review verdicting, or requirements/plan authoring is needed. |
Classify readiness and select the next legal execution or repair path.
Active when requirements and plan exist, but readiness, approval, execution set selection, remediation classification, or user-blocker classification is needed.
Not active when implementation, review verdicting, or requirements/plan authoring is needed.
Emit exactly one readiness classification and select execution sets from the canonical PLAN.md bead graph: PASS_EXECUTE, FAIL_PLAN, FAIL_EXPLORE, BLOCK_USER, or FAIL_STATE.
.beads/artifacts/<feature_slug>/readiness-record.json.beads/artifacts/<feature_slug>/approval-record.jsonSTATE.json readiness mirrorsHANDOFF.json only when pausing/transferringDo not emit PASS_EXECUTE with missing trace coverage, unresolved required Human Gates, ambiguous hashes, fingerprint-only approval evidence, or mismatched selected execution-set fields. Do not implement. Do not review. Do not emit PASS_EXECUTE without approval_ref. Do not emit PASS_EXECUTE with stale approval. Do not emit PASS_EXECUTE unless the approval record is created or refreshed by beo-validate and its approval hashes match live artifacts. Do not select unsupported execution modes. Do not allow continuation after a blocked ordered-batch bead. Do not use FAIL_STATE for ordinary plan or explore defects. Do not ask user questions unless the blocker is a true Human Gate.
beo-execute, beo-plan, beo-explore, user, beo-route
beo-reference -> references/pipeline.mdbeo-reference -> references/state.mdbeo-reference -> references/artifacts.mdbeo-reference -> references/approval.mdbeo-reference -> references/skill-contract-common.md