Problem
Attunement records guardrail prerequisites but does not explicitly validate each required tool and version before dependent work, or define what to do when a tool is unavailable. Individual helpers maintain partial dependency checks, so missing tools can surface late with misleading diagnostics.
Evidence
skills/attunement/SKILL.md, step 5, asks for tools and version floors to be recorded, without requiring presence/version validation.- Step 6 explicitly validates GitHub authentication, but there is no corresponding general dependency check.
skills/quest/scripts/publish-forge-review checks a command list but omits its scanner dependency rg and does not identify the missing command in its error.scripts/setup.sh lists tools for developing Adept itself; it is not an installed-skill dependency inventory.
Expected scope
Extend attunement instructions to establish a task-scoped inventory of required tools from the invoked helpers and repository guardrails, verify availability and declared version floors, and record the result. Define missing-tool handling: use a documented equivalent only when it preserves the required behavior, otherwise give an actionable installation/PATH remedy and stop only dependent work. Do not silently skip safety checks or install tools without applicable authorization. Avoid a global installer or unrelated dependency framework.
Validation
Evaluate routes for an available tool, an absent tool with a supported equivalent, an absent mandatory tool without an equivalent, and a version below a declared floor. Confirm errors name the dependency and remedy, and unrelated work can continue.
Provenance
Filed at the user's request during investigation of #338 and #339. Their publisher/scanner fixes remain in one separate PR. Related prior work: #194 added prerequisite recording; this issue covers validation and fallback behavior beyond that completed scope.
Problem
Attunement records guardrail prerequisites but does not explicitly validate each required tool and version before dependent work, or define what to do when a tool is unavailable. Individual helpers maintain partial dependency checks, so missing tools can surface late with misleading diagnostics.
Evidence
skills/attunement/SKILL.md, step 5, asks for tools and version floors to be recorded, without requiring presence/version validation.skills/quest/scripts/publish-forge-reviewchecks a command list but omits its scanner dependencyrgand does not identify the missing command in its error.scripts/setup.shlists tools for developing Adept itself; it is not an installed-skill dependency inventory.Expected scope
Extend attunement instructions to establish a task-scoped inventory of required tools from the invoked helpers and repository guardrails, verify availability and declared version floors, and record the result. Define missing-tool handling: use a documented equivalent only when it preserves the required behavior, otherwise give an actionable installation/PATH remedy and stop only dependent work. Do not silently skip safety checks or install tools without applicable authorization. Avoid a global installer or unrelated dependency framework.
Validation
Evaluate routes for an available tool, an absent tool with a supported equivalent, an absent mandatory tool without an equivalent, and a version below a declared floor. Confirm errors name the dependency and remedy, and unrelated work can continue.
Provenance
Filed at the user's request during investigation of #338 and #339. Their publisher/scanner fixes remain in one separate PR. Related prior work: #194 added prerequisite recording; this issue covers validation and fallback behavior beyond that completed scope.