team-building
npx machina-cli add skill mfwarren/entrepreneur-claude-skills/team-building --openclawTeam Building
Culture documents, team charters, 1-on-1 templates, and feedback frameworks for small teams.
Purpose
Early-stage teams don't need corporate HR playbooks. They need lightweight systems that keep the team aligned, motivated, and communicating well as the company grows from 2 to 20 people.
Workflow
Step 1: Gather Context
- Team size and structure
- Current challenges (communication, alignment, morale)
- Company stage and growth rate
- What's working well today
- What format they want: culture doc, team charter, meeting templates, feedback systems
Step 2: Culture Document (if requested)
- Mission: Why does this company exist?
- Values: 3-5 behaviors you reward and hire for
- How we work: Communication norms, decision-making, meeting cadence
- What we don't do: Anti-values (what you actively avoid)
Step 3: Team Charter (if requested)
- Team purpose and goals
- Roles and responsibilities (RACI if needed)
- Communication norms (tools, response times, meeting cadence)
- Decision-making process
- Conflict resolution approach
Step 4: 1-on-1 Templates (if requested)
Weekly or biweekly template:
- What went well this week?
- What's blocking you?
- What do you need from me?
- Career growth check-in (monthly)
- Feedback exchange (both directions)
Step 5: Feedback Framework (if requested)
SBI model:
- Situation: When/where did it happen
- Behavior: What specifically happened
- Impact: How it affected the team/project/you
For positive and constructive feedback.
Output Format
## Team Building: [Company/Team]
### [Requested deliverable]
[Complete document]
Constraints
- Keep culture docs under 2 pages — nobody reads long ones
- Values must be specific and behavioral, not generic ("integrity" means nothing without examples)
- 1-on-1s should be the employee's meeting, not the manager's
- Feedback frameworks should work in both directions
Source
git clone https://github.com/mfwarren/entrepreneur-claude-skills/blob/main/skills/leadership/team-building/SKILL.mdView on GitHub Overview
Team Building provides culture documents, team charters, 1-on-1 templates, and a feedback framework for small teams. It helps early-stage teams stay aligned, motivated, and communicative as they grow from 2 to 20 people.
How This Skill Works
Begin with context gathering, then selectively create artifacts (culture doc, team charter, 1-on-1 templates) and a feedback framework. It relies on observable behaviors, SBI-style feedback, and lightweight, actionable templates instead of heavy HR playbooks.
When to Use It
- When forming a new team or onboarding members
- During rapid growth to maintain alignment and culture
- When morale or communication gaps appear
- When defining team norms, roles, and decision processes
- Before project kickoffs or cross-functional collaborations
Quick Start
- Step 1: Gather context (team size, challenges, growth rate)
- Step 2: Create the culture doc and/or team charter if requested
- Step 3: Roll out 1-on-1 templates and a feedback framework, and iteratively improve
Best Practices
- Keep culture docs under 2 pages and focused on observable behaviors
- Define 3–5 concrete values with behavior examples
- Document clear communication norms, tools, and meeting cadence
- Use SBI feedback to give specific, actionable input (both ways)
- Make 1-on-1s employee-led and prepared for the employee's agenda
Example Use Cases
- Startup creates a 2-page culture doc outlining mission, values, and norms
- New squad outputs a team charter with RACI and decision rights
- Teams use 1-on-1 templates to track blockers and career growth
- Peers use SBI-based feedback in both directions
- Onboarding includes values, anti-values, and a structured intro meeting
Frequently Asked Questions
Related Skills
decision-frameworks
mfwarren/entrepreneur-claude-skills
# Decision Frameworks Structured decision-making for founders using reversibility analysis, weighted scoring, pre-mortems, and second-order thinking. ## Purpose Founders make hundreds of decisions a week. Most should be fast. Some need structure. This skill identifies which type of decision you'
founder-productivity
mfwarren/entrepreneur-claude-skills
# Founder Productivity Time audits, energy management, deep work scheduling, and priority frameworks for founders who wear too many hats. ## Purpose Founders don't need generic productivity advice. They need to ruthlessly prioritize the 20% of work that drives 80% of results, while managing ener