---
name: specdd-test
description: Use when Claude Code needs to derive, add, update, or assess focused tests from active SpecDD `Must`, `Scenario`, `Handles`, `Returns`, `Raises`, `Tasks`, or `Done when` contracts.
license: Apache-2.0
---

# SpecDD Test

Use this skill to connect SpecDD contracts to focused verification.

## Bootstrap Resolution

Before doing anything else in the target project, read bootstrap files in this exact order:

1. `.specdd/bootstrap.md`
2. `.specdd/bootstrap.project.md`, if it exists
3. `.specdd/bootstrap.local.md`, if it exists

Apply them in that order. Later files may narrow or specialize earlier rules, but must not silently weaken project contracts, inherited constraints, or write authority.

## Spec Chain Resolution

Before planning, editing, reviewing, testing, or reporting on a target:

1. Identify the target path, task, behavior, or changed files.
2. Resolve the effective spec chain using the active bootstrap rules.
3. Include same-directory basename specs when applicable.
4. Walk ancestor specs from the selected content root to the target.
5. Read explicit `References` only when they affect the requested work.
6. Identify the nearest local spec that grants write authority before any edit.

Do not infer authority from similar filenames, nearby files, symbols, module names, or conventions unless the active bootstrap or a governing spec explicitly defines that mapping.

## Workflow

1. Identify test authority from the nearest relevant spec.
2. Derive cases from applicable `Must`, `Scenario`, `Handles`, `Returns`, `Raises`, `Tasks`, and `Done when` entries.
3. Prefer the smallest tests that prove the specified behavior.
4. Run the relevant project test command when available.

## Test Rules

- Test observable behavior, not wording in the spec.
- Cover forbidden behavior when it can regress silently.
- Add regression tests for confirmed bugs.
- Do not create broad test harnesses unless the spec or project convention requires them.
- If the spec requires behavior but grants no clear test-file authority, ask before editing.

Report which spec entries each test covers and any specified behavior that still
lacks verification.