Skip to content
Skills Library
Programming · Automation

worktree-task-start

/worktree-task-start

Use when the user asks to start a backlog task, begin work on an issue, pick up issue N, or run `make task`. Triggers on "start task", "begin issue", "pick up issue N", "work on #N".

Repository
digithings ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user asks to start a backlog task, begin work on an issue, pick up issue N, or run `make task`. Triggers on "start task", "begin issue", "pick up issue N", "work on #N".

Triggers from the description

start taskbegin issuepick up issue Nwork on #N
Original author description

Use when the user asks to start a backlog task, begin work on an issue, pick up issue N, or run `make task`. Triggers on "start task", "begin issue", "pick up issue N", "work on #N".

How it works

  1. Before you run
  2. Run the task
  3. After the worktree is created
  4. Branch routing rules
  5. Finishing
Original SKILL.md headings · 60 lines, 276 words
SKILL.md preview
---
name: worktree-task-start
description: Use when the user asks to start a backlog task, begin work on an issue, pick up issue N, or run `make task`. Triggers on "start task", "begin issue", "pick up issue N", "work on #N".
---

# Worktree task start

Pre-flight checklist before running `make task ISSUE=N`.

## Before you run

1. **Confirm the issue number** — the user should supply `N` explicitly.
2. **Read the issue** to understand scope. Note the `primary component` field and acceptance criteria.
3. **Check for an existing worktree** — running `make task` twice for the same issue creates a conflict:
   ```bash
   git worktree list
   ```
   If a worktree for `task/<N>-*` already exists, switch into it instead of creating a new one.

4. **Confirm the base branch is up to date**:
   ```bash
   git fetch origin
   git status
   ```

## Run the task

```bash
make task ISSUE=N
```

This command:
- Creates branch `task/<N>-<slug>` from the appropriate base (`module/<component>` or `develop`).
- Creates an isolated git worktree at `../digithings-task-<N>/` (or equivalent).
- Prints the worktree path and branch name.

## After the worktree is created

1. `cd` into the worktree directory printed by `make task`.
2. Read `{component}/AGENTS.md` — mandatory pre-flight for every component.
3. Read `{component}/ARCHITECTURE.md` — understand the structure before touching code.
4. Confirm the test suite is green on the fresh branch:
   ```bash
   <test command from AGENTS.md>
   ```
5. Begin the red/green/refactor loop (see `test-first-implementer` agent).

## Branch routing rules

| Issue component | Base branch |
|---|---|
| Single module (`digiquant`, `digichat`, etc.) | `module/<component>` |
| Cross-cutting (`root`, `website`, `ci`) | `develop` |

The `make task` script reads `scripts/project_routing.json` to determine the base automatically.

## Finishing

When all acceptance criteria have passing tests:
1. Run `make score` from inside the worktree.
2. Invoke the `finish-task` skill to commit, push, and open the PR.

The PR is automatically targeted at the correct base branch.

Versions

The database has no other skills named worktree-task-start.

Database snapshot: 13.11.2026 · package version 27209183a428 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90start-issue
    Start implementation of a GitHub issue: fetch context, prepare worktree flow, implement with TDD, verify, and submit PR. Use for 'start issue #N', issue URLs, or requests to begin issue work. SKIP fully autonomous issue-to-merge requests; use complete-issue.
  • 100start
    Start working on a Linear issue — check blockers, claim it (assign + In Progress), set up the branch or worktree, plan, implement by delegation with checkpoints, then review. Tokens — `wt` (isolated worktree), `auto` (unattended; used by /auto), `simple` (simple review tier),…
  • 90start-work
    Begin or resume working on a Jira issue. Gets issue context, creates/checks out feature branch, shows MR feedback if exists, updates Jira status, searches related code, loads project gotchas. Use when user says "start work on AAP-X", "pick up issue", "begin work on AAP-12345".
  • 100pick-up-issue
    This skill should be used when the user asks to "pick up an issue", "work on issue #X", "claim issue", "start working on issue", "take this issue", "I'll work on this", or needs to take ownership of a GitHub issue before starting work.
  • 90start-issue
    Start work on a Linear issue end-to-end — create a worktree, fetch issue context from Linear, implement the fix, then commit, push, and open a draft PR. Use when the user says "start issue", "work on STU-1234", "create a worktree and fix <Linear link>", "start a worktree for…
  • 100work
    Handle issue/PR work items with worktree isolation. Triggered by "/work [issue_link|description]" to start focused work.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.