Create a team charter that documents team purpose, values, norms, and decision-making processes. Use when forming team or clarifying culture.
From tech-lead-toolkitnpx claudepluginhub sethdford/claude-skills --plugin tech-lead-toolkitThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
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.