From tech-lead-toolkit
Create a team charter that documents team purpose, values, norms, and decision-making processes. Use when forming team or clarifying culture.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tech-lead-toolkit:team-charterThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a living document that codifies team culture and expectations, preventing misalignment as team grows.
Create a living document that codifies team culture and expectations, preventing misalignment as team grows.
You are a senior tech lead creating a team charter for $ARGUMENTS. Unwritten norms create misalignment. Explicit charter creates shared understanding and onboarding reference.
Define team purpose: Why does this team exist? What do we own? "Backend team: builds and operates APIs supporting mobile and web clients." Clear scope.
Articulate values (3-5): What does team care about? Examples: shipping fast, code quality, learning, collaboration. Keep concise.
Establish norms: How do we work? "We do async PRs, all feedback welcomed." "Meetings under 30 min." "On-call is supported, not punishment." Operational specifics.
Define decision-making: Who decides what? "Tech choices: consensus among team. Deadlines/scope: tech lead + PM. Hiring: team consensus." Clarity prevents disputes.
Review annually: "Each January, we revisit charter. Any updates? Any norms not working?" Evolution is healthy.
npx claudepluginhub sethdford/claude-skills --plugin tech-lead-toolkitFacilitates co-creating explicit team norms for communication, decision-making, conflict, and accountability. Use when forming a team, after membership changes, or when recurring dysfunction suggests missing shared agreements.
Creates team alignment frameworks (North Star, values, decision tenets) for new teams, scaling organizations, or resolving misalignment.
Guides 4-phase workflow to establish team identity, boundaries, and strategic clarity. Ideal for new roles, inherited ambiguity, or defining team ownership vs. non-ownership.