.claude/skills/rddRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Requirements-Driven Development — converge fuzzy requirements into specs before coding. Trigger: RDD, 需求收敛, 需求驱动开发, requirement driven, 先理清再动手.
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/rddRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/rddRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/rddRuntime, 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 @anyjohn/rddclawhub inspect @anyjohn/rdd --version 0.1.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:e96f95ae07fb85a01616b3ee4836befa8ddebcaf815a845eeecdc0d4c3f1bf78references/rdd-design.mdreferences/templates.mdskill-card.mdSKILL.mdInitial release of rdd: Requirements-Driven Development MVP. - Introduces a stepwise workflow to refine raw requirements into verifiable specs before coding. - Defines core work item types, statuses, and traceable relationships for complete requirement-to-code mapping. - Enforces clear separation of roles and steps: Requirement Analysis, Spec Writing, Test Contract, Implementation, and Verification. - Mandates explicit handling of open questions, assumptions, and human-in-the-loop decision records. - Supports handling new features, incremental changes, module replacements, and lightweight changes in existing systems.