Development & Testing Skills

Use when Claude Code needs to create, add, restructure, or improve SpecDD .sdd contract files, define ownership or write authority, clean up missing or unclear specs, or introduce SpecDD adoption without changing implementation unless explicitly requested.

Use when Claude Code needs to diagnose or fix a bug in a SpecDD project by reproducing or inspecting failure, comparing observed behavior to active .sdd contracts, and applying the smallest authorized fix.

Use when Claude Code needs to implement a requested code, docs, tests, task, or spec change in a SpecDD project by following Resolve, Read, Authorize, Change, Verify, and Report under active bootstrap and .sdd authority.

Use when Claude Code needs to write or update user, developer, release, onboarding, or operational documentation from SpecDD specs while preserving source contract boundaries and avoiding unsupported promises.

Use when Claude Code needs to explain a SpecDD .sdd file, feature contract, or effective spec chain in succinct human language, covering purpose, scope, behavior, boundaries, tasks, scenarios, and uncertainty without editing or expanding the contract.

Use when Claude Code needs to get oriented in a SpecDD project by reading .specdd/bootstrap.md, project/local bootstraps, root specs, explicitly applicable or requested spec files, and git status before later work, while making no edits.

Use when Claude Code is explicitly asked for a plan, or must resolve unclear SpecDD scope, write authority, public-contract risk, affected files, or verification before safe implementation; do not trigger for ordinary authorized changes.

Use when Claude Code needs to refactor code, tests, docs, specs, or project structure in a SpecDD project while preserving specified behavior, public contracts, scenarios, ownership, and local write authority.

Use when Claude Code needs to review a diff, branch, pull request, changed files, or proposed changes against active SpecDD contracts, focusing on spec violations, behavioral regressions, missing checks, and concrete findings.

Use when Claude Code needs to classify risk before SpecDD work starts, especially around write authority, public contracts, security, data, migrations, dependencies, verification gaps, rollback, or destructive operations.

Use when Claude Code needs to find, add, interpret, organize, or update Tasks entries in SpecDD .sdd files, including task status changes after implementation and verification are complete.

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.

Use when Claude Code needs to map SpecDD specs to code, tests, docs, changed files, public behavior, references, verification coverage, or gaps while preserving the distinction between read context and write authority.