testspec-new

Create a testspec change directory with proposal.md and collaboration checklist.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the initial setup of a TestSpec workflow by creating a standardized change directory, required subfolders, and a proposal template, grounding the testing effort from the outset.

Core Features & Use Cases

  • Create testspec/changes/<name>/ with specs/ and artifacts/ directories.
  • Generate proposal.md linking to requirements documents and aligning with project goals.
  • Include a collaboration checklist and context metadata to guide cross-team alignment and downstream analysis.
  • Provide next steps hints (testspect-analysis or testspec-points).

Quick Start

Run testspec-new to initialize the change directory and create proposal.md ready for collaboration.

Frequently Asked Questions about testspec-new

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

FAQPage Schema
How do I create a standardized test specification directory structure for a new change request?

Creating a standardized test specification directory involves generating a testspec/changes/<name>/ hierarchy complete with specs/ and artifacts/ subfolders. This establishes a consistent directory layout to ground your testing effort from the outset.

What is the best way to draft a testing proposal that aligns with project requirements?

The best way to draft a testing proposal is to generate a proposal.md file that directly links to requirements documents. Including context metadata and a collaboration checklist ensures cross-team alignment with project goals.

How do I format change names automatically when setting up test documentation directories?

To format change names automatically, you need a process that parses your input name and converts it to kebab-case. This standardization ensures the generated testspec/changes/<name>/ directory remains consistent for downstream analysis.

Can I use a single command to initialize both test specs and collaboration checklists for change management?

Yes, an automated testspec initialization command can simultaneously create the change directory structure, write the proposal.md with required fields, and seed a collaboration checklist to guide cross-team alignment.

What should I do after generating a test proposal and seeding material metadata for a new change?

After generating a test proposal and seeding material metadata, the next steps involve running downstream analysis actions like testspec-analysis or testspec-points to process the initialized artifacts and guide further testing efforts.