tech-task

What problem does it solve? Engineering work like refactoring, CI/CD changes, tooling upgrades, and tech debt cleanup doesn't fit the product feature pipeline (no PRD/BRD), so it often lacks structure, ownership, and tracking. This Skill provides a dedicated kickoff workflow that scopes the task, routes it to the right specialist agent, and tracks it on the Kanban board. ## Core Features & Use Cases - Scope-Based Routing: Classifies tasks as small, medium, or large, then applies the right governance — direct agent handoff for small tasks, an ADR for medium ones, and an RFC with task breakdown for large initiatives. - Domain-to-Agent Mapping: Routes work to 15 specialized agents (Sentinel for CI/CD, Pixel for design systems, Kai for Android tooling, Nova for web tooling, and more) based on the affected codebase area. - Worktree and Board Integration: Creates an isolated git worktree before implementation and files board tasks tagged as "Tech Task" so sprint reports distinguish infrastructure work from feature work. - Use Case: You want to fix a flaky build pipeline. The Skill creates a worktree, identifies Sentinel as the owner, creates a board task with acceptance criteria, and hands off with full context — no PRD required. ## Quick Start Ask the assistant to start a tech task, for example: "Create a tech task to refactor the shared networking module and clean up the related tech debt."