home / skills / thebushidocollective / han / validate

validate skill

safe

This skill validates Jira ticket acceptance criteria without changing status, delivering actionable feedback and clear remaining work.

npx playbooks add skill thebushidocollective/han --skill validate

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.2 KB

---
name: validate
description: Validate acceptance criteria for a Jira ticket without changing status
---

# validate

## Name

jira:validate - Validate acceptance criteria for a Jira ticket without changing status

## Synopsis

```
/validate [arguments]
```

## Description

Validate acceptance criteria for a Jira ticket without changing status

## Implementation

Validate that all acceptance criteria are met for a Jira ticket without transitioning status.

**Usage**: `/validate PROJ-123`

Use `atlassian_get_issue` to fetch ticket details and extract acceptance criteria.

**Display Format**:

```
🔍 Validating PROJ-123: {summary}

Current Status: {status}
Assignee: {assignee}

📋 Acceptance Criteria:

1. ✓ {criterion 1}
   Evidence: {ask user or check recent comments/code changes}

2. ✓ {criterion 2}
   Evidence: {ask user or check recent comments/code changes}

3. ✗ {criterion 3}
   Status: Not complete

4. ✓ {criterion 4}
   Evidence: {ask user or check recent comments/code changes}

Summary: 3/4 criteria met (75%)

Remaining work:
- {criterion 3}: {suggest what needs to be done}

Ready to complete? No - complete remaining criteria first.
```

Provide actionable feedback on what still needs to be done.

Overview

This skill validates acceptance criteria for a Jira ticket without changing the ticket status. It fetches issue details, extracts acceptance criteria, and reports which criteria are met, which are not, and what evidence exists. The output is actionable and focused on what remains to release or close the ticket.

How this skill works

The skill calls the Jira issue API to retrieve summary, status, assignee, and description fields, then parses the acceptance criteria block. For each criterion it checks for supporting evidence such as comments, recent commits, or linked pull requests and marks criteria as met or unmet. It returns a concise checklist with evidence notes, a completion percentage, and recommendations for outstanding work.

When to use it

Before marking a ticket Done or Ready for QA
During sprint review to confirm acceptance readiness
When preparing a pull request that references a Jira issue
To create a QA checklist from the ticket’s acceptance criteria
When triaging incomplete or blocked tickets

Best practices

Ensure acceptance criteria are written clearly and consistently in the issue description
Keep relevant commits, PRs, and test notes linked in the ticket or comments
Run validation after developer updates and before status transitions
Use the evidence suggestions to prompt team members for missing information
Confirm automated checks (CI, test runs) are referenced in the ticket comments

Example use cases

Validate PROJ-123 before requesting QA to ensure all criteria are satisfied
Run validation in a pre-merge checklist to surface missing acceptance items
Use during backlog grooming to identify tickets lacking testable acceptance criteria
Generate a short handoff summary for QA that lists unmet criteria and suggested fixes
Quickly assess blockers by highlighting criteria without evidence

FAQ

Will the skill change the ticket status?

No. It only reads issue data and reports validation results; it does not perform transitions.

How does it determine evidence for a criterion?

It looks for recent comments, linked commits or pull requests, and explicit mentions in the issue. If none are found, it prompts for manual verification or asks for links to evidence.