testing

Automate test-driven development workflows for NL artifacts using .nlpm-test spec files.

111|29|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/xiaolai/nlpm-for-claude --skill testing-xiaolai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/xiaolai/nlpm-for-claude/tree/main/skills/nlpm/testing
Command: npx skills add https://github.com/xiaolai/nlpm-for-claude --skill testing-xiaolai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NLPM projects often struggle to validate NL artifacts before implementation. This Skill provides a formal spec-based workflow to drive test-driven development and automated validation across skills, agents, commands, rules, hooks, and prompts.

Core Features & Use Cases

  • Formal spec format for artifacts stored under .nlpm-test to drive deterministic testing with /nlpm:test.
  • Automated discovery, validation, and scoring integration to enforce quality gates and reduce regression risk.
  • Supports end-to-end TDD workflows across multiple artifact types (skills, agents, commands, rules, hooks, prompts).

Quick Start

Run /nlpm:test to execute specs and verify that artifacts pass their tests before scoring.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I automate test-driven development for natural language artifacts?▼

You can automate TDD for NL artifacts by defining formal spec files in a .nlpm-test directory, which drives deterministic validation, scoring, and red-green-refactor feedback loops via the /nlpm:test command.

What is spec-based validation for prompts and rules?▼

Spec-based validation for prompts and rules uses formal files to define artifact, type, min_score, and validation criteria, enabling automated discovery and quality gate enforcement before implementation to reduce regression risk.

How do I run validation tests for NLPM project components?▼

Run validation tests for NLPM project components by executing the /nlpm:test command, which automatically discovers spec files and verifies that your skills, agents, commands, rules, hooks, and prompts pass their defined tests.

Can I use TDD workflows across multiple artifact types like agents and commands?▼

Yes, you can apply TDD workflows across multiple artifact types including skills, agents, commands, rules, hooks, and prompts, allowing end-to-end test-driven development and automated validation across your entire NLPM project.

What format do test specs need to be in for NL artifact validation?▼

Test specs for NL artifact validation must be stored under the .nlpm-test directory and define the artifact, type, min_score, and validation criteria to properly drive the /nlpm:test execution and scoring.

Why does my NL artifact validation fail during the testing phase?▼

NL artifact validation fails during testing when the artifact does not meet the min_score threshold or validation criteria defined in the .nlpm-test spec files, acting as a quality gate to prevent regressions before implementation.