skills.rest
malhashemi
malhashemiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ticket-review

Review ticket documents for gaps, inconsistencies, and severity-classified issues.

20|Updated Oct 13, 2025
Search Tags:#quality assurance#code review#documentation#issue tracking#specification analysis#ticket review
One-click install
npx skills add https://github.com/malhashemi/dotfiles --skill ticket-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-review
Source: https://github.com/malhashemi/dotfiles/tree/main/dot_config/opencode/skill/caster/ticket-review
Command: npx skills add https://github.com/malhashemi/dotfiles --skill ticket-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the issue of incomplete, inconsistent, or ambiguous ticket documentation, ensuring that tickets are clear, complete, and ready for implementation.

Core Features & Use Cases

  • Structured Review Workflow: Guides users through a systematic process of analyzing tickets.
  • Severity Classification: Identifies and categorizes issues (Critical, High, Medium, Low) based on their impact on implementation.
  • Actionable Feedback: Provides specific before/after text proposals for fixes.
  • Use Case: When a developer receives a ticket that is unclear about acceptance criteria, this skill can be used to identify the ambiguity, suggest clearer wording, and ensure all necessary details are present before development begins.

Quick Start

Use the ticket-review skill to analyze the ticket document located at /path/to/ticket.md.

Frequently Asked Questions about ticket-review

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

FAQPage Schema
How do I review a ticket for completeness and implementer readiness?▼

Ticket review involves analyzing documentation for gaps and inconsistencies, categorizing issues by severity (Critical, High, Medium, Low), and providing specific before/after text proposals to ensure implementer readiness.

What is the best way to classify issues found during ticket review?▼

Issue severity classification categorizes ticket findings into Critical, High, Medium, and Low levels based on their impact on implementation, helping prioritize fixes through a structured review workflow.

Can I get specific text proposals for fixing unclear acceptance criteria?▼

Yes, actionable ticket feedback provides specific before/after text proposals for fixes. It identifies ambiguity in acceptance criteria and suggests clearer wording to ensure necessary details are present for development.

How do I identify gaps and inconsistencies in issue tracking documentation?▼

You identify gaps and inconsistencies in issue tracking documentation through specification analysis, systematically reviewing existing tickets to detect incomplete information and categorize issues by severity for structured remediation.

When do I need to use a structured ticket review workflow?▼

You need a structured ticket review workflow when a developer receives an unclear ticket. It ensures documentation completeness, resolves ambiguity in acceptance criteria, and verifies implementer readiness before coding starts.

Related Skills

Explore More Software Engineering Skills→
alfredoperezalfredoperez
80

to-tickets

Create tickets with dependencies from plans, specs, or conversations.

Community
Intermediate
larsnyglarsnyg

performance-optimizer

Identify and resolve performance bottlenecks across frontend, backend, and database layers.

Community
Advanced
blakesimsblakesims

review-code

Review executed code phases against the plan using git commands.

Community
Advanced
Desko77Desko77
40

1c-role-validate

Validate 1C Role Rights.xml structure, rights, RLS, and metadata.

Community
Advanced