| name | plan-tickets |
| type | atomic |
| license | MIT |
| description | Draft and classify structured tickets with area prefixes and five-section format (Summary, Background, Acceptance Criteria, Dependencies, Technical Notes), plus a readiness checklist. Draft-only by default; create issues only after explicit user approval. Use when breaking a plan into tickets, creating Jira/GitHub issues, classifying work items.
|
| metadata | {"version":"1.0.0","user-invocable":"true"} |
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
Integration
| Skill | When |
|---|
| generate-tasks | After tasks exist |
| create-prd | Align tickets with PRD scope |
