.claude/skills/requirements-discoveryRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
结合源码证据和针对性问答,明确业务边界、阻塞决策与可验收的需求约定
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/requirements-discoveryRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/requirements-discoveryRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/requirements-discoveryRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @wlykan/requirements-discoveryclawhub inspect @wlykan/requirements-discovery --version 1.0.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:2bcbdd9c959d4e600bbf9794c635f279f0b979672a056aafe6280816e24a7e96agents/openai.yamlreferences/openspec-handoff.mdskill-card.mdSKILL.mdrequirements-discovery 1.0.0 - Initial release of the requirements-discovery skill. - Clarifies ambiguous or conflicting development requirements into actionable and verifiable agreements via targeted Q&A and source validation. - Focuses on identifying business rules, scope boundaries, and blocking ambiguities; not for routine code explanation or minor, well-defined changes. - Systematically distinguishes between facts, user decisions, technical suggestions, and pending issues, with source attribution. - Provides clear criteria for requirement handoff and decision impact, supporting both exploration and actionable resolutions. - Output structured to suit both simple and complex needs, with emphasis on direct evidence and practical handoff.