to-meegle-speclisted
Install: claude install-skill thanathe/meegle-buddy
# to-meegle-spec
Turn the conversation into a spec. Output 1: a markdown file, always. Output 2: a parent card in
Meegle, only if the user says yes. Nothing else.
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 spec or PRD skill instead of this one.
2. **NEVER run `git commit`, `git push`, `but commit` or `but push`.** Write the file and stop.
3. **NEVER create the Meegle card without the user saying yes** in step 5.
4. **NEVER invent** a project key, type key, field key, option id, work item id, user key, estimate,
priority or date. Keys come from `CONFIG`; everything else comes from the user.
5. **Talk to the user in their language** (the one they write in; quoted Thai lines below are
examples). Write the spec itself in English.
6. **Do not interview the user.** Build the spec from what the conversation already says. The only
questions are in steps 2 and 5, and the setup questions in step 6 if they are needed.
If you are unsure what to do at any point: write the file, stop, and ask the user in the user's language.
## Step 1 — Read the context
- Read the conversation so far.
- If the user gave a file path or a Meegle id, read it in full.
- Look at the repo the wor