start_tasklisted

Before starting any non-trivial task, create a GitHub Issue, a dedicated branch, and a draft PR. This keeps work traceable and every PR maps to exactly one issue. ## Mandatory scripts | Action | Script | Never use | |--------|--------|-----------| | Start issue + branch + draft PR | `.agents/scripts/start_issue.sh <n> <type>` | bare `git checkout -b` + bare `gh pr create` | | Push branch | `.agents/scripts/push_branch.sh` | bare `git push` | | **Push + promote + merge (all-in-one)** | `.agents/scripts/finish_pr.sh <n>` | `gh pr ready`, bare `gh pr merge`, `gh pr checks --watch` | ## Steps 1. **Clarify scope** — if $ARGUMENTS is empty or vague, ask the user for: - Task title (one line, imperative: "Add X", "Fix Y", "Refactor Z") - Work type: `feat` / `fix` / `chore` / `docs` / `test` 2. **Check for existing issue and PR** — run `gh issue list` and `gh pr list`. If an issue already exists, use its number. If a draft PR already exists for that issue, use it — do **not** create a second PR. Skip to step 5. 3. **Create the issue** — load the `create_issue` skill and follow it. It gathers priority, area, size, references, dependencies, and acceptance criteria before running: ```bash ISSUE_NUMBER=$(.agents/scripts/create_issue.sh <type> "<title>" --priority <priority> --area "<area>" --size <size> --acceptance "<criterion>") echo "Created issue #$ISSUE_NUMBER" ``` 4. **Start work** — create the branch, push, and open a draft PR: ```bash .agents/scripts