Plan Tickets
Normalize inputs, classify each work item, draft tickets in a standard structure. Default mode: draft-only.
HARD-GATE
- Do not create tracker issues unless explicitly asked.
- Do not assume tracker credentials, project fields, sprint IDs, or status behavior.
- If only tickets are requested, return Markdown drafts.
Core Process
Normalize initiative: theme, project, draft vs. create mode, default bucket, constraints.
Classify each ticket: type, area, execution order, dependency level, target bucket using the classification rules below.
Apply sprint placement: foundation/api before client, exclude external confirmations, place follow-up tickets in ready-to-refine.
Apply title prefixes: BE | (backend), FE | (frontend), Mobile | (mobile).
Draft each ticket with five sections: Summary, Background, Acceptance Criteria, Dependencies, Technical Notes.
Output:
Draft-only (default): Markdown tickets with classification line and five-section structure plus a readiness checklist.
Create-in-tracker: After explicit approval, create issues using the tracker API. Validate required fields; do not set status on create. Confirm with one issue before bulk creation.
Classification Rules
[type: Story|Task] [area: backend|web|mobile|cross-platform|external] [execution_order: foundation|api|client|follow-up] [dependency_level: unblocked|blocked] [target_bucket: ready-to-refine|next-dev-sprint|later]
Optional: coordination_need, external_dependency, urgency.
Extended Resources
- EXAMPLES.md — full plan-to-ticket example
- assets/ticket-samples/sample_issue.md — sample issue format
Integration
| Skill |
When |
| generate-tasks |
After tasks exist |
| create-prd |
Align tickets with PRD scope |
1---2name: plan-tickets3description: Use when breaking a plan into tracker tickets or classifying work items. Draft-only unless the user explicitly asks to create issues. Trigger words: create tickets, Jira, Linear, GitHub Issues, classify work items, ticket drafts.4license: MIT5---6# Plan Tickets78Normalize inputs, classify each work item, draft tickets in a standard structure. Default mode: draft-only.910## HARD-GATE11- Do not create tracker issues unless explicitly asked.12- Do not assume tracker credentials, project fields, sprint IDs, or status behavior.13- If only tickets are requested, return Markdown drafts.1415## Core Process161. Normalize initiative: theme, project, draft vs. create mode, default bucket, constraints.172. Classify each ticket: type, area, execution order, dependency level, target bucket using the classification rules below.183. Apply sprint placement: foundation/api before client, exclude external confirmations, place follow-up tickets in ready-to-refine.194. Apply title prefixes: `BE | ` (backend), `FE | ` (frontend), `Mobile | ` (mobile).205. Draft each ticket with five sections: Summary, Background, Acceptance Criteria, Dependencies, Technical Notes.216. Output:2223 **Draft-only (default):** Markdown tickets with classification line and five-section structure plus a readiness checklist.2425 **Create-in-tracker:** After explicit approval, create issues using the tracker API. Validate required fields; do not set status on create. Confirm with one issue before bulk creation.2627## Classification Rules28`[type: Story|Task] [area: backend|web|mobile|cross-platform|external] [execution_order: foundation|api|client|follow-up] [dependency_level: unblocked|blocked] [target_bucket: ready-to-refine|next-dev-sprint|later]`2930Optional: `coordination_need`, `external_dependency`, `urgency`.3132## Extended Resources33- [EXAMPLES.md](./EXAMPLES.md) — full plan-to-ticket example34- [assets/ticket-samples/sample_issue.md](assets/ticket-samples/sample_issue.md) — sample issue format3536## Integration37| Skill | When |38|-------|------|39| **generate-tasks** | After tasks exist |40| **create-prd** | Align tickets with PRD scope |
igmarin