home / skills / thebushidocollective / han / complete

complete skill

safe

/plugins/services/jira/skills/complete

This skill marks a Jira ticket as complete after validating acceptance criteria and documenting the completion summary.

npx playbooks add skill thebushidocollective/han --skill complete

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

Files (1)

SKILL.md

1.3 KB

---
name: complete
description: Mark a Jira ticket as complete after validating acceptance criteria
---

# complete

## Name

jira:complete - Mark a Jira ticket as complete after validating acceptance criteria

## Synopsis

```
/complete [arguments]
```

## Description

Mark a Jira ticket as complete after validating acceptance criteria

## Implementation

Complete a Jira ticket by validating acceptance criteria and transitioning to Done.

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

**Steps**:

1. Use `atlassian_get_issue` to fetch ticket details including description and comments
2. Extract acceptance criteria from description
3. Display each criterion and ask user to confirm completion
4. If all confirmed:
   - Use `atlassian_add_comment` to add completion summary
   - Use `atlassian_transition_issue` to transition to "Done"
5. If any not confirmed:
   - List incomplete criteria
   - Keep ticket in current status
   - Suggest next steps

**Display Format**:

```
✅ Completing PROJ-123: {summary}

📋 Acceptance Criteria Validation:

1. ✓ {criterion 1} - COMPLETE
2. ✓ {criterion 2} - COMPLETE
3. ✗ {criterion 3} - INCOMPLETE
4. ✓ {criterion 4} - COMPLETE

❌ Cannot complete: 1 criterion not met
- {criterion 3}

Suggestion: Complete remaining criteria before marking as Done.
```

Only transition to Done if ALL criteria are validated.

Overview

This skill marks a Jira ticket as complete after validating its acceptance criteria. It fetches the ticket, extracts acceptance criteria, prompts for validation, and only transitions the issue to Done when every criterion is confirmed. If any criterion remains unmet, it lists gaps and suggests next steps instead of closing the ticket.

How this skill works

The skill retrieves the issue details and comments using the Jira API, then parses the issue description to extract acceptance criteria. It presents each criterion for manual confirmation; when the user confirms all criteria are satisfied, the skill posts a completion comment and transitions the issue to the Done status. If any criteria are unconfirmed, it reports incomplete items and leaves the ticket in its current state while suggesting remediation steps.

When to use it

Before marking a Jira issue Done to ensure acceptance criteria are met
As a final checklist during pull request reviews or release prep
When you need an auditable comment summarizing completed criteria
To prevent premature workflow transitions and reduce reopens
When acceptance criteria are documented in the issue description

Best practices

Write clear, discrete acceptance criteria in the issue description so parsing is reliable
Confirm each criterion with relevant stakeholders before using the skill
Use the skill at the end of the implementation cycle to avoid back-and-forth transitions
Keep comments concise and factual when the skill posts a completion summary
Manually resolve ambiguous or unstated criteria before attempting completion

Example use cases

A developer runs /complete PROJ-123 after implementing features to confirm QA and product acceptance
QA lead validates test-based criteria and marks the ticket Done once tests pass
A release coordinator uses the skill to produce a completion comment for audit trails
A team lead prevents accidental closures by requiring explicit confirmation of all acceptance items
A product manager cross-checks delivered behavior against documented criteria before sign-off

FAQ

What happens if one acceptance criterion is not met?

The skill lists incomplete criteria, leaves the ticket in its current status, and suggests next steps instead of transitioning to Done.

Does the skill automatically infer acceptance criteria from comments?

It primarily extracts criteria from the issue description; comments may be fetched for context but explicit criteria should be in the description for reliable validation.