# Test Plan > Create a feature-level test plan from acceptance criteria and add it to the feature spec. Use when this capability is needed. - Skill: `tomevault-io/test-plan` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/test-plan` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/test-plan/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - 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-plan --- 1) Read `AGENTS.md`, `codex.toml` (if present), and the target feature spec `spec/features/-.md`. - `` must use `F.` (example: `F1.1`). 2) Convert acceptance criteria into a test matrix: - Unit tests (fast, isolated) - Integration tests (component boundaries) - End-to-end / scenario tests (happy path + key edge cases) - Negative/error cases (validation, permissions, timeouts, etc.) 3) Decide what to mock vs run for real (with rationale). 4) Update the feature spec “Test plan” section with: - Test cases mapped to ACs - Test data/fixtures needed - Any required test hooks/utilities 5) End by recommending `write-tests`. - Output exactly: - `Next recommended skill:` - `Run $write-tests to implement the planned unit/integration/edge-case tests.` - Replace `` with the real ID from the target spec (example: `F1.2`). - Do not use markdown links or absolute file paths in this recommendation. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/rafaie) — claim your Tome and manage your conversions.