plan-tests

Generate a structured Test Plan from an approved spec by mapping acceptance criteria to test types.

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/opsMachine/OM-Agency --skill plan-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-tests
Source: https://github.com/opsMachine/OM-Agency/tree/main/skills/plan-tests
Command: npx skills add https://github.com/opsMachine/OM-Agency --skill plan-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating a structured test plan from an approved spec, separating planning from test implementation to ensure comprehensive coverage and traceability.

Core Features & Use Cases

  • Automated test plan generation: extracts acceptance criteria and maps them to unit, integration, and automated test types.
  • Plan organization: groups criteria by test location, references existing tests where possible, and identifies gaps.
  • Spec augmentation: inserts a recognizable "Test Plan" section into the spec with status and summary, guiding downstream work.

Quick Start

Run /plan-tests path/to/spec.md after spec approval to generate a test plan in the spec.

Frequently Asked Questions about plan-tests

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

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

To generate a test plan from a spec, run the command against your approved spec file. It extracts acceptance criteria, organizes them by test type, and appends a structured Test Plan section directly into the spec to guide QA.

How do I organize acceptance criteria by test type for automated and manual tests?

Organizing acceptance criteria by test type is handled automatically by mapping extracted criteria to unit, integration, and manual test categories. This structured mapping identifies coverage gaps and references existing tests within the generated plan.

What is the best way to map acceptance criteria to test files?

Mapping acceptance criteria to test files is achieved by generating a structured test plan within the spec. The plan groups criteria by test location, references existing tests where applicable, and highlights gaps for downstream test implementation.

When do I need to create a test plan after spec approval?

You need to create a test plan immediately after spec approval and before test implementation. This separates planning from coding, ensuring comprehensive automated and manual coverage with traceability back to the spec.

Can I use this test planning approach to guide downstream failing test generation?

Yes, this approach guides downstream failing test generation by appending a recognizable Test Plan section with status and summaries to the spec. This structured plan directs subsequent write-failing-test steps and spec updates.

Does test planning separate coverage planning from test implementation?

Yes, test planning separates coverage planning from implementation to ensure comprehensive coverage and traceability. By generating a structured plan within the spec, it organizes acceptance criteria before any actual test code is written.