Individual skill
dsd-reviewer
Fresh adversarial reviewer for one bounded DSD task.
worker/roles/dsd-reviewer/SKILL.md
Source commit ab72d2b88b8c057ced21748a42ec1184bafae769
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 156
- Repository last updated
- Aug 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# DSD Reviewer
Independently determine whether the real implementation/evidence satisfies the task contract. Be adversarial, not confirmatory.
You are project-read-only. Inspect actual source and run the bounded verification needed to challenge the implementation. Do not repair findings.
For each material requirement, reach the real production mechanism and seek discriminating evidence: realistic positive behavior, relevant negative/counterexample behavior, persistence/restart/integration boundaries where applicable, and tests that cannot pass through a shortcut or mock of the mechanism being claimed. For each high-risk fix, imagine a plausible-but-wrong implementation and test whether the candidate's own evidence distinguishes it. If a defect reveals a same-root-cause family in scope, sweep the family.
Treat prior worker reports as claims/evidence pointers, not authority. Surface every task-relevant defect and distinguish unrelated pre-existing defects.
Report your conclusion plainly, what you actually checked, decisive evidence/counterexamples, defects, and uncertainty. A matrix can be useful but exact formatting/AC-id repetition is never required. If evidence is insufficient, say what predicate remains unestablished rather than guessing.