task-driven-developmentlisted

Work through engineering issues one at a time with dependency checks, scoped staging, and review-ready commit messages. Use when implementing work from GitHub Issues, GitLab Issues, a backlog, or workflow document. Engineering host is GitHub or GitLab per the consumer .skills/profile — not ClickUp.
singleton-sd/ai-plattform-skills · ★ 0 · AI & Automation · score 68

Install: claude install-skill singleton-sd/ai-plattform-skills

# Task-Driven Development Use this skill when implementing work from the **project host's** issue tracker. ## Resolve the engineering host 1. Read consumer `.skills/profile` when present (`engineeringHost`: `github` | `gitlab`). 2. Else infer from `git remote get-url origin` (`github.com` → github, `gitlab.com` → gitlab). 3. Load the matching profile under [`config/tracker-profiles/`](../../config/tracker-profiles/README.md). | Host | CLI | Claim | Handoff | |------|-----|-------|---------| | GitHub | `gh` | Branch/worktree + open PR linking the issue | PR body `Closes #N` | | GitLab | `glab` | Branch/worktree + open MR linking the issue | MR with closing keyword | **ClickUp is not the engineering tracker.** Product features and optional tracking tickets live in ClickUp; see `operations/create-tracking-ticket`. Do not claim or hand off engineering work via ClickUp status or Claim Token. Read the target repo `AGENTS.md` for worktree helpers, hub-file rules, and conflict playbooks. Also apply [`engineering/isolated-worktree`](../../engineering/isolated-worktree/SKILL.md). ## Issue and chat titles - Prefer the **issue title** as the primary label in chat and summaries. - Numbers are fine in URLs, branch names (`<type>/<issue-number>-<kebab-title>`), and as secondary references. ## Out of scope → follow-up issues When planning, every real **Out of scope** follow-up must become a host issue: 1. Search existing issues first — do not invent duplicates. 2. Create missing