live-testing-plan

Extract acceptance criteria and map tests to changed code for Jira issues.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Omniloy/agent-skills --skill live-testing-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: live-testing-plan
Source: https://github.com/Omniloy/agent-skills/tree/main/skills/live-testing-plan
Command: npx skills add https://github.com/Omniloy/agent-skills --skill live-testing-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a Jira issue into a concrete live verification plan so teams can prove a change works against a real system instead of relying on guesswork. It reduces ambiguity by locking in acceptance criteria, clarifying who will run the tests, and keeping verification tied to the exact ticket in scope.

Core Features & Use Cases

  • Acceptance criteria extraction: Pulls explicit criteria from the issue, linked issues, or user discussion and turns them into a testable source of truth.
  • Mode-aware planning: Adapts the plan for Claude-run live server checks, Omniloy evals, or manual human testing.
  • Concrete test design: Produces setup steps, step-by-step tests, expected results, and pass or fail criteria for each case.
  • Results reporting: Renders a pass/fail table, summarizes coverage, and highlights failures for triage without attempting to fix code.
  • Use Case: A developer finishes a Jira ticket and needs a verification plan that can be executed immediately against staging, then reported back to the issue for review.

Quick Start

Use the live-testing-plan skill for MAR-123 to extract the acceptance criteria, draft the appropriate verification plan, and present the results table.

Frequently Asked Questions about live-testing-plan

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

FAQPage Schema
How do I create a verification plan from Jira acceptance criteria?

A live testing plan extracts explicit acceptance criteria from a Jira issue, linked items, or discussion and converts them into a testable source of truth. It then maps tests to the actual changed code for validation.

Can I use live server checks to verify backend services and UI flows for a Jira ticket?

Yes, live server checks can verify backend services, UI flows, and conversational agents tied to a Jira ticket. The testing plan adapts to the execution mode, supporting Claude-run live server checks, Omniloy evals, or manual human testing.

How do I generate pass or fail reporting with full acceptance criteria coverage?

Generate pass or fail reporting by executing mode-specific test cases against your system. The plan renders a pass/fail table, summarizes coverage, and highlights failures for triage without attempting to fix the code.

What setup prerequisites do I need for issue traceability when testing a Jira issue?

Setup prerequisites for issue traceability include the target Jira issue key, access to the changed code, and a configured execution environment like a staging server. The plan requires this traceability to map tests to the exact ticket in scope.

Does the testing plan fix code when validation fails against acceptance criteria?

No, the testing plan does not fix code when validation fails. It highlights failures for triage and renders a pass/fail table with full acceptance criteria coverage, keeping verification strictly separated from code modification.