myna-dev-task-addlisted

# Myna Add Task Draft a structured task entry and append it to `tmp/tasks.md`. Show the draft to the user before writing — they approve or adjust. ## Input Check `$ARGUMENTS`: - **If provided:** use it as the task description and proceed to Step 1. - **If empty and coming from conversation context** (e.g., invoked after `/myna-dev-diagnose`): use the agreed option from that conversation and proceed to Step 1. - **If empty with no context:** ask the user: "What task do you want to add to the queue?" --- ## Step 1 — Read the Queue Check if `tmp/tasks.md` exists: ```bash ls tmp/tasks.md 2>/dev/null ``` If it exists, read it to: - Get the current highest task number (for the next `#`) - Understand the format already in use If it doesn't exist, the next task number is 1. --- ## Step 2 — Draft the Task Entry From `$ARGUMENTS` and any conversation context, draft the task. Infer what you can — don't ask for information that's already clear. Use this structure: ```markdown ## Task [N] — [Title] **Problem:** [What's wrong or what's missing — and why it matters. 1-3 sentences.] **Correct behavior:** [What Myna should do instead — described as behavior, not implementation. 1-3 sentences.] **Context:** [Background the implementer needs. Relevant skill paths, related decisions, constraints. Skip if obvious.] **Suggested files:** [Most likely files to change — paths only. Omit if unclear.] **Done when:** - [Specific, verifiable assertion — not "it works" but "the skill's f