← ClaudeAtlas

to-meegle-ticketslisted

Break a spec, plan, or the current conversation into tracer-bullet task cards in Meegle (Feishu / Lark Project), each linked to a parent card and listing what blocks it. Writes the breakdown to a markdown file first, and creates cards only after the user confirms. Works in any Meegle space: reads types and fields from the meegle-buddy config, nothing hardcoded. Never uses GitHub. Use when the user says 'break this into tickets', 'แตก task', 'แตกการ์ด', 'สร้าง task จาก spec', 'เปิด task ใน meegle', or after /to-meegle-spec created a card. Prefer this over to-issues / to-tickets, which publish to GitHub Issues.
thanathe/meegle-buddy · ★ 1 · Data & Documents · score 77
Install: claude install-skill thanathe/meegle-buddy
# to-meegle-tickets Break work into **task cards** in Meegle: thin vertical slices, each linked to a parent card (the spec card), each saying which other tasks block it. Output 1: a breakdown file, always. Output 2: Meegle task cards, only after the user says yes. All paths below are relative to **this skill's folder** (the folder this SKILL.md is in). `CONFIG` means: `python3 scripts/meegle_config.py`. ## RULES — read these first, they override everything below 1. **NEVER use GitHub.** Do not run `gh` (no `gh issue`, `gh pr`, `gh api`). Do not create GitHub issues or pull requests. Do not run any other ticket or issue skill instead of this one. 2. **NEVER run `git commit`, `git push`, `but commit` or `but push`.** 3. **NEVER create a card before the user says yes** to the whole batch in step 6. 4. **NEVER invent** a project key, type key, field key, option id, work item id, user key, estimate or date. Keys come from `CONFIG`; everything else comes from the user. Estimates are often required by Meegle — that is a reason to ask, not a reason to guess. 5. **NEVER send a field that `CONFIG summary` does not list** for the task type. 6. **NEVER create tasks without a parent card.** If there is none, stop and suggest `/to-meegle-spec`. 7. **NEVER modify the parent card.** 8. **Talk to the user in their language** (the one they write in; quoted Thai lines below are examples). Write task titles and bodies in English. If you are unsure what to do at any point: sa