spec-test-plan-agent

Generates test cases, answer keys, and test-spec markdown from approved feature specifications.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/neuthos/ldx-monorepo --skill spec-test-plan-agent-neuthos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-test-plan-agent
Source: https://github.com/neuthos/ldx-monorepo/tree/main/.agents/skills/spec-test-plan-agent
Command: npx skills add https://github.com/neuthos/ldx-monorepo --skill spec-test-plan-agent-neuthos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an approved feature specification into a complete, traceable test plan is slow and error-prone: requirements get missed, boundary cases are skipped, and QA sheets drift out of sync with the spec. This Skill automates the planning-stage conversion of a spec into structured test artifacts while keeping all target repositories read-only. ## Core Features & Use Cases - Spec-to-Testcase Generation: Reads the spec's Traceability Matrix and produces Testcases rows with strict statuses, categories, and one-step-per-row cases in the ringi TDD Google Sheet. - Answerkey & Metadata Sync: Creates per-TC Answerkey tabs for E2E cases and updates BOUNDARIES checklist rows in Metadata without touching human-edited cells. - Technical Test Spec Output: Writes {ringi-id}-test-spec.md with a six-column test case table, data preparation summary, and test pyramid breakdown for FE/BE/E2E teams working in parallel. - Use Case: After a product spec is approved, run this Skill to produce a full test plan covering all BR/FRs, BOUNDARIES dimensions, and a balanced Unit/Integration/E2E pyramid before any implementation begins. ## Quick Start Use the spec-test-plan-agent to turn the approved ringi spec into Testcases, Answerkey tabs, and a test-spec markdown for the FE, BE, and E2E teams.

Frequently Asked Questions about spec-test-plan-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a test plan from a feature specification?▼

Provide the approved spec markdown and its traceability matrix; the agent maps every BR/FR to test cases, designs BOUNDARIES probes, and outputs a six-column test case table plus sheet rows. Pending or rejected requirements are recorded as gaps rather than tested.

What test case categories and pyramid does the agent produce?▼

Cases are categorized as Happy Path, Negative path, Edge case, Error handling, or Boundaries, each assigned exactly one level of Unit, Integration, or E2E. The target split is roughly 70% Unit, 15-20% Integration, and 5-10% E2E, with deviations reported and justified.

Does the test plan agent modify code or run tests?▼

No. It operates strictly read-only against the FE, BE, and E2E repositories and never creates code, installs dependencies, runs tests, or changes branches. Repository evidence is used only to ground routes, endpoints, and models in the technical markdown.

How does the agent handle edited or rejected requirements in the sheet?▼

On re-runs it reads existing statuses first: Editted rows are ingested with adapted test cases keeping their IDs, Rejected rows are dropped from regeneration with reasons kept, and human-entered cells are never overwritten or renumbered.

What is the BOUNDARIES checklist in test planning?▼

BOUNDARIES is a ten-dimension discovery guide covering Boundary values, Ordering, Unicode, Null/empty, Data volume, Access, Race conditions, Integration failures, Environment, and State transitions. Each dimension is marked Covered, Partially covered, or Not applicable with a reason, and gaps become PENDING entries.