clarity--ticket-writer

Name: clarity--ticket-writer
Availability: InStock
Author: Pattern

Transform vague stakeholder requests into structured engineering work tickets.

57|3|Updated Mar 30, 2026

Search Tags:#requirements #engineering #stakeholder #ticket #product-management #acceptance-criteria

Ready to run

npx skills add https://github.com/patterninc/code-mint --skill clarity-ticket-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clarity--ticket-writer
Source: https://github.com/patterninc/code-mint/tree/main/.agents/skills/clarity--ticket-writer
Command: npx skills add https://github.com/patterninc/code-mint --skill clarity-ticket-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Vagueness in stakeholder requests often leads to ambiguous work items, misaligned expectations, and delays. This Skill converts unclear input into precise, actionable tickets that engineers can execute with confidence.

Core Features & Use Cases

Triage and clarify ambiguous tasks by asking targeted questions and capturing decisions in a formal ticket.
Generate structured tickets including title, description, acceptance criteria, complexity tier, target files, and any necessary references.
Use cases: refining feature requests from product managers; turning ad-hoc requirements into production-ready tickets; reviewing incoming requests for scope and risk.

Quick Start

Provide a clear stakeholder request; the system will produce a ready-to-submit ticket with all required fields.

Frequently Asked Questions about clarity--ticket-writer

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

FAQPage Schema

How do I turn vague stakeholder requests into actionable engineering tickets?▼

To turn vague stakeholder requests into actionable engineering tickets, you provide the raw request input to trigger a triage process that asks targeted clarifying questions and outputs a structured ticket with acceptance criteria, complexity tier, and target files.

What is the best way to write acceptance criteria for ambiguous product management tasks?▼

Writing acceptance criteria for ambiguous product management tasks requires capturing stakeholder decisions through targeted questions, then structuring those decisions into formal ticket fields with explicit complexity tiers and design notes for engineering execution.

Can I refine feature requests to include target files and complexity tiers automatically?▼

You can refine feature requests to include target files and complexity tiers by processing the initial request through a structured ticket generation workflow that evaluates scope and outputs these specific engineering fields.

Does this ticket writing approach work for reviewing incoming ad-hoc requirements?▼

This ticket writing approach works for reviewing incoming ad-hoc requirements by triaging the ambiguous input, identifying scope and risk through targeted questions, and producing a production-ready ticket with necessary references.

What should a production-ready work ticket include when refining requirements?▼

A production-ready work ticket should include a structured title, description, acceptance criteria, complexity tier, target files, design notes, and optional references or assets to guide engineering work confidently.

Why do stakeholder requests lead to misaligned expectations during ticket writing?▼

Stakeholder requests lead to misaligned expectations during ticket writing because vagueness in the initial input creates ambiguous work items, which structured ticket generation with formal acceptance criteria resolves.