ticket-refinement

Refining raw Jira tickets involves structuring them with user stories, acceptance criteria, and technical notes. The ticket-refinement skill automates this by applying project-specific contracts to ensure technical dependencies and accessibility requirements are documented before development begins.

Ticket refinement is the process of transforming raw triaged issues into actionable tasks. You need to add acceptance criteria when a ticket lacks the necessary technical context or definition-of-done requirements required for a developer to begin implementation.

To standardize technical documentation and workflow states, you validate ticket content against project-specific contracts. This ensures critical links, environment prerequisites, and diagnostic observations are preserved and aligned with required workflow states before estimation.

Ticket refinement operates specifically on triaged tickets, not untriaged ones. Tickets must be initially prepared so the skill can effectively apply project-specific contracts, accessibility requirements, and definition-of-done validations to make them ready for development.

The best way to document accessibility requirements before estimation is to validate ticket content against project-specific definition-of-done requirements. This ensures technical notes, dependencies, and accessibility criteria are explicitly captured during the refinement process.

Your development ticket lacks technical context because raw tickets often contain ambiguity. Refining them structures the ticket body with user stories, acceptance criteria, and technical notes, ensuring all diagnostic observations and environment prerequisites are documented.