test

Automate end-to-end TDD test execution for PMC tickets using tests.json and 3-spec.md.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/jayprimer/pmc-marketplace --skill test-jayprimer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/jayprimer/pmc-marketplace/tree/main/plugins/pmc/skills/test
Command: npx skills add https://github.com/jayprimer/pmc-marketplace --skill test-jayprimer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end TDD test workflow for PMC tickets, reducing manual testing overhead and ensuring consistent test execution.

Core Features & Use Cases

  • Orchestrates RED/GREEN/REFACTOR cycles for ticket-level test development.
  • Reads tests.json and 3-spec.md to drive test discovery, setup, and verification steps.
  • Records trajectory logs and updates ticket status to reflect progress and outcomes.
  • Supports browser/API/CLI interactions via provided workflow definitions and utilities.

Quick Start

Start a TDD cycle for a ticket by running the test workflow and following RED, GREEN, and REFACTOR steps.

Frequently Asked Questions about test

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

FAQPage Schema
How do I automate end-to-end TDD test execution for workflow tickets?

You can automate TDD test execution by reading tests.json and 3-spec.md to drive RED-GREEN-REFACTOR cycles, coordinating browser/API/CLI actions, and emitting trajectory logs with ticket status updates.

What is the RED-GREEN-REFACTOR flow for ticket-level test development?

The RED-GREEN-REFACTOR flow guides test discovery, setup, and verification. It drives test development through failing tests, implementation, and refactoring while recording trajectory logs to track progress and outcomes for each ticket.

Do I need specific files to start a TDD cycle for a PMC ticket?

Yes, you need a 3-spec.md specification and a tests.json file included with your PMC ticket. These files drive test discovery, setup, and verification steps throughout the automated TDD workflow execution.

How does trajectory recording work during automated test execution?

Trajectory recording captures the complete test execution path by logging browser, API, and CLI interactions coordinated during the workflow. It emits a full trajectory log alongside status updates to reflect ticket progress and outcomes.

Can I use browser, API, and CLI interactions in a single TDD workflow?

Yes, the TDD workflow supports browser, API, and CLI interactions within a single execution. It coordinates these actions as described in the workflow definitions to satisfy functional requirements and verify ticket-level tests.

What's the best way to reduce manual testing overhead for TDD workflows?

Automating the end-to-end TDD test workflow reduces manual testing overhead by orchestrating RED-GREEN-REFACTOR cycles, reading test specifications, coordinating multi-channel interactions, and emitting complete trajectory logs with status updates.