specdd-test
Derive Tests from SpecDD Specs
SpecDD projects need tests that trace to active contracts. This skill guides Claude, Codex, and Claude Code through spec resolution and focused verification.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "specdd-test" from https://skillstore.io/skills/specdd-specdd-test.md and its manifest at https://skillstore.io/api/skills/specdd-specdd-test/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "specdd-test". Review tests for the payment retry behavior.
Expected outcome:
The report identifies the governing specs, lists covered requirements, and names retry scenarios that still need tests.
Using "specdd-test". Add tests for the new validation rule.
Expected outcome:
The result adds focused tests under authorized files and explains which SpecDD entries each test covers.
Using "specdd-test". Check whether this bug fix has regression coverage.
Expected outcome:
The response links the bug to active specs, confirms existing coverage, or proposes the smallest missing regression test.
Security Audit
SafeThe seven static external-command findings are false positives. They are Markdown inline code references to SpecDD paths and terms, not executable shell or Ruby backtick usage. No prompt-injection or malicious intent evidence was found in SKILL.md.
Risk Factors
⚙️ External commands (7)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/specdd-specdd-test/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/specdd-specdd-test?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/specdd-specdd-test?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/specdd-specdd-test/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/specdd-specdd-test.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
specdd. (2026). specdd-test security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/specdd-specdd-test/audits/4BibTeX citation
@techreport{specdd-specdd-specdd-test-2026,
author = {specdd},
title = {specdd-test security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/specdd-specdd-test/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "specdd-test security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "specdd"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/specdd-specdd-test/audits/4"
identifiers:
- type: other
value: "skillstore:specdd-specdd-test:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Add Contract Tests
Turn active SpecDD requirements into small tests that verify observable behavior.
Review Test Coverage
Compare existing tests with governing specs and identify required behavior without verification.
Create Regression Tests
Use confirmed bugs and current specs to add focused regression coverage.
Try These Prompts
Use specdd-test to review the tests for this target path. Report which SpecDD entries are covered and which still need tests.
Use specdd-test to derive the smallest tests for this behavior. Edit only files with clear SpecDD test authority.
Use specdd-test to check whether my recent changes satisfy the active specs. Run the relevant project test command if available.
Use specdd-test to map this confirmed bug to governing specs, add regression tests, and report any uncovered required behavior.
Best Practices
- Use the skill only after confirming the project has a root .specdd/bootstrap.md file.
- Name the target path, behavior, or changed files before asking for test work.
- Ask for a coverage report when you need traceability from tests to spec entries.
Avoid
- Do not use this skill to introduce SpecDD into a project without explicit adoption work.
- Do not ask it to edit tests when no governing spec grants test-file authority.
- Do not request broad harness changes when focused behavior tests are enough.