start-issuelisted
Install: claude install-skill lamuniercosta/dotnet-agent-harness
# Start issue (repo-local)
**Customization for `dotnet-agent-harness` only.** Does not replace or fork the
shared harness `/task` skill. `install.ps1` syncs packaged `skills/` into
consumers; this directory is **not** in that tree, so it stays local.
In **this** repository, prefer `/start-issue` over `/task` so board Status
updates. See the root `CLAUDE.md` note.
## Parameters
```text
$ARGUMENTS
```
- **issue** — GitHub issue number, e.g. `40`
- **type** (optional) — `feature` | `bug` | `hotfix` (same rules as `/task`)
Typical: `/start-issue 40` or `/start-issue 40 feature`
## Prerequisites
- Authenticated `gh` with the **project** scope (default login often lacks it):
```bash
gh auth login
gh auth refresh -s project
```
- PowerShell 7 (`pwsh`) for `scripts/local/Set-IssueInProgress.ps1` and the harness branch scripts
## Steps
### 1. Run harness `/task` (or equivalent)
Follow [`skills/task/SKILL.md`](../../../skills/task/SKILL.md) exactly:
1. `gh issue view <n> --json number,title,body,labels`
2. Resolve branch type
3. `./packs/dotnet/scripts/new-task-branch.ps1 -Issue <n> [-Type …]` (from a consumer install the script is under `./scripts/`; in **this** repo the pack path is `./packs/dotnet/scripts/new-task-branch.ps1`)
4. Hand off to mandatory `/grill-with-docs` after the board step below — do not skip the grill
If the working tree is dirty or the branch already exists, stop and report; do not force.
### 2. Move project Status → In Progress
After a successfu