Skip to content

Latest commit

 

History

History
26 lines (20 loc) · 653 Bytes

File metadata and controls

26 lines (20 loc) · 653 Bytes
name ticket-breakdown
description Break a task or ticket into small steps. Use when a junior developer needs guidance on how to start.

Ticket Breakdown

Purpose

Break a task or ticket into small steps.

Inputs to request

  • Ticket description and acceptance criteria.
  • Target files or components.
  • Known constraints or deadlines.

Workflow

  1. Summarize the ticket goal and acceptance criteria.
  2. Split into implementation steps with dependencies.
  3. Identify what to test and how to validate.

Output

  • Step-by-step task list with checks.

Quality bar

  • Keep steps small and testable.
  • Highlight any missing requirements.