// Use when the user explicitly invokes $work or asks for execution strategy for complex engineering work with unclear scope, dependent steps, or separable workstreams.
| name | work |
| description | Use when the user explicitly invokes $work or asks for execution strategy for complex engineering work with unclear scope, dependent steps, or separable workstreams. |
| metadata | {"short-description":"Route complex work"} |
Route complex work into the smallest execution shape that preserves evidence, focus, and momentum. Do not duplicate narrower skills; let debugging, TDD, review, PR, or platform-specific skills own their lanes.
quick: one obvious local step. Execute directly.research: user needs location, explanation, or confidence. Inspect source and answer.structured: dependent steps or multi-file edits. Use update_plan, then work sequentially.parallel: independent units with disjoint write scopes. Delegate only sidecar tasks when
permitted; keep the blocking path local.orchestrated: large, staged work. Decompose into waves; wait only when blocked.unclear: ambiguity risks the outcome. Ask the smallest question.Report what changed, what verified it, and any remaining risk or unverified edge.
Preparing and creating git commits when explicitly requested; covers staged diff review, secrets checks, and conventional commit messages.
Verifying implementation work before claiming completion; covers tests, affected artifacts, evidence, and unresolved risks.
Create a conventional commit from current workspace changes. Use when the user asks to run $commit, asks to commit changes, or asks for a commit message from the current diff.
Create GitHub issues with optional parent/sub-issue relationships and organization issue types. Use when the user asks to create, link, or retag GitHub issues, especially when they mention a parent issue, sub-issues, tasks, bugs, epics, or cross-repo issue hierarchy.
Extract the underlying intent behind a request, issue, PR, or diff. Focus on problem and desired outcome; do not propose implementation, testing strategy, or rollout plans.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.