uat-instructions

Generate Given-When-Then UAT instructions from Linear issues into Markdown documents.

Updated Oct 15, 2025
One-click install
npx skills add https://github.com/kingler/v0-jetvision-assistant --skill uat-instructions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uat-instructions
Source: https://github.com/kingler/v0-jetvision-assistant/tree/main/.claude/skills/uat-instructions
Command: npx skills add https://github.com/kingler/v0-jetvision-assistant --skill uat-instructions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generates formal UAT instructions from Linear issues, including Given-When-Then acceptance criteria and test steps, and saves outputs for QA handoff.

Core Features & Use Cases

  • Generate Given-When-Then acceptance criteria from Linear issues
  • Produce batch UAT plans for multiple in-progress issues
  • Save Markdown UAT documents to docs/uat and optionally post updates back to Linear

Quick Start

Run /uat_instructions on a Linear issue to generate a complete UAT plan and save it to docs/uat/.

Frequently Asked Questions about uat-instructions

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

FAQPage Schema
How do I generate UAT plans from Linear issues automatically?

To generate UAT plans from Linear issues, run the designated command on an issue to parse context, produce Given-When-Then acceptance criteria, format a Markdown document, and save the output.

What is Given-When-Then acceptance criteria and how does it apply to QA handoffs?

Given-When-Then acceptance criteria define preconditions, actions, and expected outcomes. They apply to QA handoffs by translating Linear issue context into clear, executable test steps for testers.

Can I create batch UAT plans for multiple in-progress Linear issues?

Yes, batch UAT plans can be created for multiple in-progress Linear issues. The system parses context across selected issues to generate acceptance criteria and test steps, saving each as a Markdown document.

Do I need Linear MCP context to generate acceptance criteria and test steps?

Linear MCP context is required to generate acceptance criteria and test steps. The system parses this context to extract issue details and format them into structured Markdown UAT documents.

Does the generated UAT document save locally or post updates back to Linear?

Generated UAT documents save locally to the docs/uat directory as Markdown files, with optional postings back to Linear. This provides testers with documented plans while keeping issue tracking synchronized.