submit-tasklisted

# submit-task Turns a single, already-clear issue into a brief-level task section in the current milestone's `TASKS_TODO.md`. This skill is the user-facing entry point (`/submit-task`) and the handoff target for `/discuss-new-task`. It owns the triage and positioning that need the **whole task list in view** — checking for duplicates and deciding where the task belongs — and then it authors and inserts the task **inline, in this conversation**. If the issue is still vague or might be several tasks, use `/discuss-new-task` first. ## Invocation ``` /submit-task <issue description> ``` `<issue description>` is a free-form description of a problem or gap discovered during development, specific enough that the affected system, desired behavior, and how to verify it are clear. ## Workflow ### 0. Find the current milestone Follow `${CLAUDE_PLUGIN_ROOT}/shared/get-current-milestone.md` to resolve `<MILESTONE_DIR>`. Never use a hardcoded task-list path. ### 1. Read context for triage Read in parallel: - `<MILESTONE_DIR>/requirements.md` — to confirm the issue fits the milestone's scope. - `<MILESTONE_DIR>/TASKS_TODO.md` — existing pending tasks, for duplicate-detection and positioning. - `<MILESTONE_DIR>/TASKS_DONE.md` — completed work, to catch issues already addressed. ### 2. Triage - **Duplicate?** If an existing pending task or a completed task already covers this issue, stop and tell the user which task covers it. Do not add a duplicate. - **In scope?** If the issue c