hw-test

Generate markdown hardware test plans from phase-based plan documents.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/matthewdeaves/peertalk --skill hw-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hw-test
Source: https://github.com/matthewdeaves/peertalk/tree/main/.claude/skills/hw-test
Command: npx skills add https://github.com/matthewdeaves/peertalk --skill hw-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Generates structured hardware test plans from phase-based design documents to streamline manual testing on Classic Macintosh hardware and modern platforms.

Core Features & Use Cases

  • Parse plan files (plan/PHASE-*.md) to identify sessions and acceptance criteria.
  • Generate platform-specific test plans (markdown) using the provided template.
  • Save plans to tests/hw/ with session and platform identifiers for easy tracking.

Quick Start

Create a hardware test plan for session 5.1 on MacTCP by parsing the corresponding plan file and populating the test template.

Frequently Asked Questions about hw-test

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

FAQPage Schema
How do I generate a hardware test plan from a phase document?

Manual hardware testing for MacTCP, Open Transport, and AppleTalk requires structured test plans to track verification sessions across multiple platforms and hardware configurations. This skill automates extracting acceptance criteria from phase documents to populate markdown test templates.

Does this tool support generating test plans for Open Transport and AppleTalk?

Yes, it generates manual hardware test plans for MacTCP, Open Transport, and AppleTalk. It parses phase-based plan files to extract acceptance criteria and populates platform-specific markdown templates for documenting hardware verification sessions.

How do I document manual hardware verification sessions across multiple platforms?

You document manual hardware verification by parsing plan/PHASE-*.md files to identify sessions and acceptance criteria. The skill populates a markdown template and saves the structured test plan to tests/hw/ with session and platform identifiers for easy tracking.

Can I use my own markdown template for hardware testing sessions?

The skill generates test plans using a provided markdown template to ensure structured hardware testing documentation. It parses phase-based plan files, extracts acceptance criteria, and populates the template before saving the results to tests/hw/ with a clear status.

What is the best way to track hardware test status across different phases?

Tracking hardware test status is handled by saving generated markdown test plans to tests/hw/ with clear session and platform identifiers. The skill parses phase-based plan documents to populate the test plan template with a clear status.