# Template: start a new issue Copy, fill the `<...>` fields, and paste as the task prompt. ```text Task: implement . Rules (llm-project-workflow): - No repo changes without a tracking issue. If none exists, create one first; if it can't be created, stop. - Work only in an isolated branch worktree under branches/. The main checkout is orchestration/status only. - Do not self-review or self-merge. Steps: 1. Identity Checklist: Before claiming work, verify and state: - Required identity/profile for this task: author (allowed to push branches / create PRs) - Current authenticated identity (from whoami): - Target task role: author/work identity *If the current identity does not match the required role (or lacks push/PR permissions), STOP before claiming the issue. Relaunch/switch to the correct profile first.* 2. Verify the orchestration checkout is the right repo and clean. 3. git fetch --prune; confirm local master == /master (0 0). 4. Create the issue "" (problem, scope, acceptance) and claim it (status:in-progress + a "starting work" comment naming the branch). 5. scripts/worktree-start <type>/issue-<n>-<slug> # type = fix|feat|docs cd branches/<type>-issue-<n>-<slug> 6. Implement the narrow scope only; add/update focused tests if behavior changes. 7. Checks: run the test suite, compile/lint changed files, git diff --check, and scan the diff for secrets. 8. Commit (issue-linked message), push the branch, open a PR to master. *The PR body MUST use closing keywords like `Closes #N` or `Fixes #N` to close the issue; do NOT use `Implements #N` or `Refs #N` for closing, as Gitea will not auto-close it.* Include an "LLM Handoff Metadata" block in the PR body (attribution only; never an eligibility input — docs/llm-agent-sha.md): LLM Handoff Metadata: - LLM-Agent-SHA: llm-<12 lowercase hex, e.g. llm-8f3a9c2d6b41> - LLM-Role: implementer - Authenticated-Gitea-User: <whoami result> - MCP-Profile: <profile name> - Branch: <branch> - Worktree: <worktree path> - Self-review allowed: no 9. Stop before review/merge — you are the author. Handoff: issue #, branch, worktree path, files changed, checks + results, PR URL — formatted as the compact Controller Handoff (SKILL.md §K; long form only on the high-risk triggers); Review line: "Review needed — PR is open". ```