Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From builtin-tasks
Workflow guidelines for team members executing tasks with Claude Code, including completion pipeline, commit rules, and worktree usage.
How this skill is triggered — by the user, by Claude, or both
Slash command
/builtin-tasks:team-memberThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
After implementing a task, run `/orchestration:finish` before marking the task complete or picking up a new one.
After implementing a task, run /orchestration:finish before marking the task complete or picking up a new one.
Always commit your work before going idle or moving to the next task. If precommit fails, fix and retry until it passes.
If the team lead instructed you to use a worktree, work in that directory. Otherwise work in the main repo directory.
npx claudepluginhub motlin/claude-code-plugins --plugin builtin-tasksGuides team leads coordinating task-executing agents: enforces one commit per task, serializes overlapping file tasks or uses worktrees, checkpoints idle states.
Enforces safe git workflow: one branch per task, no force pushes, atomic commits. Useful when coding autonomously and branches need human review before merging.
Guides creation of clean, atomic git commits following project conventions. Part of the Virtual Team pipeline for structured commit workflows.