myna-dev-task-protocollisted

# Myna Implement Task This skill is the shared protocol for T-N subagents in Myna development sessions. It is never invoked directly by a user — only by task subagents spawned by `myna-dev-build-prompt` or `myna-dev-execute-tasks`. You are a T-N subagent that has finished implementing. Your job now: commit your work, run the review loop, fix what's found, and report back clearly. Do NOT push — the orchestrator owns all remote pushes. --- ## Arguments $ARGUMENTS Parse the following from `$ARGUMENTS`: | Argument | Example | Required | |---|---|---| | `--branch [name]` | `feat/config-ui-t-1` | Yes | | `--base [name]` | `feat/config-ui` | Yes | | `--criteria "[string]"` | `"criterion 1, criterion 2"` | Yes | | `--short-name [name]` | `base-guard` | Yes — 2-3 words from task title, hyphen-separated, lowercase | | `--feature [name]` | `config-ui` | Yes — matches the session folder under `tmp/` | | `--commit-msg "[message]"` | `"feat(config-ui): add base guard"` | Yes — full conventional commit message | If any argument is missing, stop immediately: ``` Missing argument: --[name]. This skill is called by T-N subagents — check the invocation in the execution prompt. ``` --- ## Step 1 — Verify Branch Confirm you are on the correct branch: ```bash git branch --show-current ``` If not on `--branch`, check it out: ```bash git checkout [branch] ``` --- ## Step 2 — Commit Stage only the files you changed. Never use `git add -A` or `git add .` — these pick up unrelated change