// Use this skill to lock feature requirements. Use when a missing answer can change acceptance, non-goals, compatibility, constraints, or user-visible scope. Do not use when the work is only a design choice.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | beo-explore |
| description | Use this skill to lock requirements before planning. Use when no locked requirements exist, requirements are missing or contradicted, acceptance/scope-affecting answers are unresolved, or a Human Gate can affect acceptance, scope, non-goals, compatibility, approval, security/privacy, access, or legal/business constraints. Do not use when implementation details can be safely decided inside locked scope. |
Lock requirements before planning.
Active when no locked requirements exist, requirements are missing or contradicted, acceptance/scope-affecting answers are unresolved, or a Human Gate can affect acceptance, scope, non-goals, compatibility, approval, security/privacy, access, or legal/business constraints.
Not active when implementation details can be safely decided inside locked scope.
Produce or repair locked requirements.
.beads/artifacts/<feature_slug>/CONTEXT.md; .beads/artifacts/<feature_slug>/pending-human-gates.md only if needed; STATE.json fields needed for requirements lock and next owner; HANDOFF.json only when pausing/transferring.
Do not plan. Do not implement. Do not approve readiness. Do not lock requirements while a required Human Gate remains unresolved. Do not ask questions that cannot affect acceptance or scope. Do not route for requirements defects that beo-explore owns.
beo-plan, 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