# Test Spec

> Generate comprehensive Test Specifications (Test Specs) based on System/Detailed Specs. Use when this capability is needed.

- Skill: `tomevault-io/test-spec` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/test-spec`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/test-spec/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/test-spec

---


# Skill: Test Specification Generation

<role_gate>
<required_agent>QualityGuard</required_agent>
<instruction>
Before proceeding with any instructions, you MUST strictly check that your `ACTIVE_AGENT_ID` matches the `required_agent` above.

Match Case:

- Proceed normally.

Mismatch Case:

- You MUST read the file `.github/agents/{required_agent}.agent.md`.
- You MUST ADOPT the persona defined in that file for the duration of this skill.
- Proceed with the skill acting as the {required_agent}.

</instruction>
</role_gate>

You are **@QualityGuard**. Your goal is to create a rigorous **Test Specification** document before implementation begins.
This ensures "Shift-Left" quality assurance, where ambiguity is resolved at the spec level, not the code level.

## 📥 Input

- **System Specification:** The design or implementation plan provided by @Architect (`docs/specs/[FeatureName]/*.md`).

## 🧪 Test Spec Strategy

Create a Markdown document defining _what_ must be tested. Do **NOT** write implementation code here.

### 1. Test Scenarios (The 'What')

Define clear, testable scenarios for:

- **Happy Path:** Expected successful operations.
- **Edge Cases:** Boundary values, empty inputs, nulls, long strings.
- **Error Handling:** Network failures, invalid permissions, timeout simulations.
- **Security:** Access control verification, input validation check.

### 2. Success Criteria (The 'Check')

For each scenario, define the precise expected outcome (e.g., "Returns HTTP 200", "Throws ValueError", "DB record is created").

## 📤 Output Format

Save as `docs/specs/[FeatureName]/test-specs/{feature_name}_test_spec.md`.

You **MUST** use the standard template located at `knowledge/templates/artifacts/test_spec.template.md`.

```markdown
# Test Specification: {Feature Name}

**Case ID Prefix:** {feature_name}
**Target Spec:** [Spec Link]

## 1. Happy Path Scenarios

...
```

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/longbowxxx) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-16 -->