testspec-points

Extract test points from analysis artifacts into categorized specs/testpoints.md.

5|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/winhok/testkit --skill testspec-points
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testspec-points
Source: https://github.com/winhok/testkit/tree/main/skills/testspec-points
Command: npx skills add https://github.com/winhok/testkit --skill testspec-points

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill extracts actionable test points from analysis artifacts and outputs them into specs/testpoints.md, enabling teams to translate insights into concrete validation targets without writing steps.

Core Features & Use Cases

  • Extract test points from analysis conclusions (requirements-analysis.md or proposal.md) and organize them into a structured, auditable set of test points categorized by type (Functional, Boundary, Exception, Integration, Non-Functional).
  • Produce specs/testpoints.md to feed testspec-generate for full test case creation, ensuring clear separation between "What" to validate and "How" to test.
  • Support mappings to requirements and potential testlib reuse for regression planning.

Quick Start

Take requirements-analysis.md or proposal.md as input and run testspec-points to generate specs/testpoints.md.

Frequently Asked Questions about testspec-points

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

FAQPage Schema
How do I extract test points from requirements analysis documents?

The skill generates test points by reading requirements-analysis.md or proposal.md, extracting actionable validation targets, and categorizing them into Functional, Boundary, Exception, Integration, and Non-Functional groups in specs/testpoints.md.

What is the best way to organize test points by category for regression planning?

Organizing test points for regression planning involves categorizing them into Functional, Boundary, Exception, Integration, and Non-Functional types, assigning unique TP_IDs, and mapping them to modules and features for testlib reuse.

Can I generate test points from a proposal if requirements analysis is unavailable?

Yes, you can generate test points from a proposal when analysis is unavailable. The extraction workflow automatically falls back to reading proposal.md to derive actionable validation targets and output structured test points.

How do test points feed into full test case creation workflows?

Test points feed into test case creation by producing specs/testpoints.md. This file defines what to validate and serves as structured input for testspec-generate to produce full test cases detailing how to test.

Does the test points extraction support traceability to requirements?

Yes, test points extraction supports traceability by generating unique TP_IDs and creating clear associations between the extracted validation targets and their original requirements documented in the analysis artifacts.

What are the limitations of using automated test point extraction from specs?

A limitation of automated test point extraction is that it strictly relies on the existence of requirements-analysis.md or proposal.md, and it generates validation targets rather than detailed test execution steps.