assignlisted

Delegate a specific, named task to the right repo / engineer subagent — design-first, with full pre-flight checks and the 6-gate post-delegation review. Use when the user names a specific task ID, e.g. '/assign {{TASK_ID_PREFIX}}-S<N>.<NN>', 'work on TG-NN', 'execute task NN'. Sister skill: /next-task (when the user doesn't name a specific task — the orchestrator picks the next eligible row).
Maximumsoft-Co-LTD/claude-flightdeck · ★ 2 · AI & Automation · score 78

Install: claude install-skill Maximumsoft-Co-LTD/claude-flightdeck

# /assign — Delegate a Specific Task (Design-First) > **Announce on start:** open your reply with "Using /assign to delegate `<TASK_ID>` design-first." For when the user already knows which task they want to dispatch. Otherwise → `/next-task`. ## Token budget (MANDATORY) - **All scan steps ≤1k tokens total.** `Grep` the sprint file for the task row (not full Read); `Read` the Design Doc directly (path is in the row). - **Read large artifacts lazily** — only when a specific step needs the content. No full `Read` on files ≥200 lines. - **Do NOT re-read CLAUDE.md** — the harness auto-loads it at session start (both parent AND child subagent). ## Input `/assign <repo-or-component> <task_id>` — e.g. `/assign backend {{TASK_ID_PREFIX}}-S03.04` ## Repo / Component → Subagent mapping Default mapping (the core engineers are architecture-agnostic — they read `.claude/rules/code-style.md` + sample the code and conform). Full table: `references/repo-to-agent-mapping.md`. | Repo / Component | Subagent | |---|---| | Any server-side component | `backend-engineer` | | Any client-side / UI component | `frontend-engineer` | | Infra / deploy (if `k8s-helm` installed) | `k8s-engineer` | | Cross-service architectural decision | `senior-tech-lead` | ## Steps 1. **Parse repo + task ID.** Map repo → directory. 2. **Find the task row (lazy — do not Read full sprint file)**: - `Glob` for the active sprint file in `docs/spec/sprints/sprint-*.md` - `Grep` for the task ID with `-A 5 -B 1