# SKILL: PRD to Ticket Agent Skill

## Purpose
Convert a PRD into implementation-ready tickets with acceptance criteria, dependencies, risk notes, and test expectations.

## When to Use
Use this when the user needs to: Convert a PRD into implementation-ready tickets with acceptance criteria, dependencies, risk notes, and test expectations. It is designed for repeatable agent or automation work, not one-off fluffy prompting.

## Inputs Required
- PRD
- Target tracker
- Engineering constraints
- Definition of done
- Release deadline

## Workflow
1. Identify user stories and non-functional requirements
2. Split into vertical slices
3. Create acceptance criteria and edge cases
4. Flag dependencies and unknowns
5. Hold ticket creation for approval

## Output Format
Ticket backlog with title, description, acceptance criteria, dependency, and test note.

## Quality Rules
- Ground every claim in supplied inputs or clearly mark it as an assumption.
- Prefer specific fields, examples, and decision points over generic advice.
- Include a test command and pass criteria so the skill can be evaluated.
- Keep the output usable by a human first and automation-ready second.

## Guardrails
- Do not send emails, publish posts, contact leads, change calendars, spend money, delete data, or alter production systems without explicit human approval.
- Do not invent facts, private details, legal claims, prices, or external data.
- For web or profile research, use current sources and separate evidence from inference.
- For connected tools, use the minimum permission needed and log the action taken.

## Test Command
Run this skill on a simple example for PRD to Ticket Agent Skill and return the expected output structure plus any missing inputs.