gitwalter Team Huddle Onboarding
Condensed 1-2 hour collaborative onboarding for small teams (2-5 people) with mini-games and shared decision-making
A condensed, collaborative onboarding experience for small teams (2-5 people) that captures shared vision, values, and wisdom through mini-games and facilitated discussion.
Philosophy
"A team that builds together, stays together."
Team Huddle is the sweet spot between quick individual setup and the full workshop series. It gives small teams alignment and shared ownership without requiring multiple days of workshops.
Duration
1-2 hours (single session)
Process
- Review the task requirements.
- Apply the skill's methodology.
- Validate the output against the defined criteria.
Step 1: Opening & Lightning Hopes (5 min)
Welcome team, set intention, and have each person share one hope for the project.
Step 2: Future Headlines Game (15 min)
Team imagines success 2 years out, writes headlines, votes on favorites, and identifies themes.
Step 3: Values Speed Round (10 min)
Team selects top 3 values from 8 options through individual voting and consensus.
Step 4: Stack Consensus (15 min)
Determine technology stack through discussion or confirmation, match to blueprint.
Step 5: Agent Character Design (20 min)
Design AI agents with names, personalities, strengths, and limitations through creative collaboration.
Step 6: Wisdom Harvest (10 min)
Capture team strengths, lessons learned, and quality definitions through structured questions.
Step 7: Preview & Launch (15 min)
Show preview of generated system, confirm target directory, generate artifacts, and celebrate completion.
Step 8: Gratitude Close (5 min)
Team members acknowledge each other, receive closing words, and learn about the Integrity Guardian.
Session Overview
╔══════════════════════════════════════════════════════════════╗
║ TEAM HUDDLE - 1.5 HOUR CONDENSED WORKSHOP ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ 0:00 Lightning Hopes ................ 5 min ████░░░░░░ ║
║ 0:05 Future Headlines Game .......... 15 min ████░░░░░░ ║
║ 0:20 Values Speed Round ............. 10 min ████░░░░░░ ║
║ 0:30 Stack Consensus ................ 15 min ████░░░░░░ ║
║ 0:45 Agent Character Design ......... 20 min ████░░░░░░ ║
║ 1:05 Wisdom Harvest ................. 10 min ████░░░░░░ ║
║ 1:15 Preview & Launch ............... 15 min ████░░░░░░ ║
║ 1:30 Gratitude Close ................ 5 min ████░░░░░░ ║
║ ║
╚══════════════════════════════════════════════════════════════╝
Opening (Facilitator Script)
╔══════════════════════════════════════════════════════════════╗
║ 🤝 TEAM HUDDLE ║
║ ║
║ Welcome, team! In the next 1-2 hours, we'll create ║
║ something together - an AI agent system that reflects ║
║ who you are and what you're building. ║
║ ║
║ Before we begin, a moment of intention: ║
║ May what we build serve the flourishing of all. ║
║ ║
║ Ground Rule: There are no wrong answers. Every voice ║
║ matters. This is about alignment, not perfection. ║
║ ║
║ Love is the root. Truth is the way. Beauty is the fruit. ║
║ ║
║ Let's begin! ║
╚══════════════════════════════════════════════════════════════╝
Activity 1: Lightning Hopes (5 min)
Purpose
Quick emotional check-in and shared intention setting.
Facilitator Instructions
╔══════════════════════════════════════════════════════════════╗
║ ⚡ LIGHTNING HOPES ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Everyone: Share your name and ONE hope for this project. ║
║ ║
║ Keep it to one sentence. No explanations needed. ║
║ Just share from the heart. ║
║ ║
║ Format: "I'm [name], and I hope [one thing]." ║
║ ║
║ Who wants to start? ║
╚══════════════════════════════════════════════════════════════╝
Capture
Record each hope in the session notes. These become part of TEAM_CHARTER.md.
Transition
Beautiful. Notice the themes in your hopes. Let's turn those into vision...
Activity 2: Future Headlines Game (15 min)
Purpose
Align on vision through imaginative storytelling.
Setup (2 min)
╔══════════════════════════════════════════════════════════════╗
║ 📰 FUTURE HEADLINES ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Imagine it's 2 years from now. Your project succeeded ║
║ beyond your wildest dreams. Tech blogs are writing ║
║ about you! ║
║ ║
║ Take 3 minutes SILENTLY. Write 2-3 headlines. ║
║ Be bold! Dream big! ║
║ ║
║ Example: "Startup's AI Tool Saves Developers 10 Hours/Week" ║
║ ║
║ Timer starts... NOW. ║
╚══════════════════════════════════════════════════════════════╝
Writing Phase (3 min)
- No talking
- Everyone writes 2-3 headlines
- Can use paper, phone notes, or chat
Sharing Phase (5 min)
- Each person reads their favorite headline
- No discussion yet - just appreciation ("ooh!", "I love that!")
Voting (2 min)
╔══════════════════════════════════════════════════════════════╗
║ Vote for the headlines that inspire you most! ║
║ Everyone gets 2 votes. You can vote for your own. ║
║ ║
║ (Raise hands, use reactions, or type numbers) ║
╚══════════════════════════════════════════════════════════════╝
Synthesis (3 min)
What themes appear in our top headlines?
[Capture 2-3 key themes]
These themes will shape your mission.
Capture
Store top 3 headlines and themes for TEAM_CHARTER.md.
Activity 3: Values Speed Round (10 min)
Purpose
Quickly surface and rank team values.
Presentation (2 min)
╔══════════════════════════════════════════════════════════════╗
║ 🎯 VALUES SPEED ROUND ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Here are 8 values. You can only pick 3 as a team. ║
║ Which matter MOST? ║
║ ║
║ 1. Code Quality 5. User Experience ║
║ 2. Speed 6. Security ║
║ 3. Simplicity 7. Innovation ║
║ 4. Reliability 8. Collaboration ║
║ ║
║ Individual vote first, then we'll find consensus. ║
╚══════════════════════════════════════════════════════════════╝
Individual Voting (2 min)
- Everyone picks their top 3 silently
- Write down or message privately
Reveal & Tally (3 min)
Let's go around. Share your 3 picks.
[Tally votes on screen]
Consensus (3 min)
╔══════════════════════════════════════════════════════════════╗
║ Your team's top 3 values: ║
║ ║
║ 1. {VALUE_1} - {VOTES} votes ║
║ 2. {VALUE_2} - {VOTES} votes ║
║ 3. {VALUE_3} - {VOTES} votes ║
║ ║
║ Any objections? These will be embedded in your agents. ║
╚══════════════════════════════════════════════════════════════╝
Capture
Store values for .cursorrules and PURPOSE.md.
Activity 4: Stack Consensus (15 min)
Purpose
Make technology decisions as a team.
Current State Check (3 min)
╔══════════════════════════════════════════════════════════════╗
║ 🛠️ STACK CONSENSUS ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Quick check: Is the tech stack already decided? ║
║ ║
║ A) Yes, we know what we're building with ║
║ B) Mostly, but need to finalize some choices ║
║ C) No, we need to decide together ║
╚══════════════════════════════════════════════════════════════╝
If A (Already Decided) - 5 min
Great! Let me capture your stack:
- Primary language?
- Main framework(s)?
- Database?
[Match to blueprint]
If B or C (Need Discussion) - 12 min
╔══════════════════════════════════════════════════════════════╗
║ Let's decide together. Quick round-robin: ║
║ ║
║ Q1: What language is the team most comfortable with? ║
║ Q2: What framework fits our project type? ║
║ Q3: What database makes sense? ║
║ ║
║ If there's disagreement, we vote! ║
╚══════════════════════════════════════════════════════════════╝
Blueprint Matching
╔══════════════════════════════════════════════════════════════╗
║ Based on your stack, I recommend: ║
║ ║
║ Blueprint: {BLUEPRINT_NAME} ║
║ This includes: ║
║ • Pre-configured patterns for {LANGUAGE} ║
║ • Knowledge files for {FRAMEWORK} ║
║ • Suggested agents and skills ║
║ ║
║ Does this work for everyone? ║
╚══════════════════════════════════════════════════════════════╝
Capture
Store stack configuration.
Tooling Quick Vote (2 min)
After confirming the tech stack, conduct a quick team vote on automation tooling:
╔══════════════════════════════════════════════════════════════╗
║ TOOLING QUICK VOTE ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Your project will include automation tools. ║
║ Quick vote - how much automation? ║
║ ║
║ 1. Essential - CI, doc sync (lightweight) ║
║ 2. Standard - + git hooks, safe commits (recommended) ║
║ 3. Full - + secret scanning, changelogs ║
║ ║
║ Show of hands: 1? 2? 3? ║
╚══════════════════════════════════════════════════════════════╝
Process:
- Each team member votes (show of hands or reactions)
- Majority wins
- Default if tied: Standard
- Record result as
{TOOLING_TIER}for generation
Transition:
Great choice! Your {TOOLING_TIER} tooling will keep your project healthy automatically. Now let's design your agents...
Activity 5: Agent Character Design (20 min)
Purpose
Creative agent design that builds team ownership.
Introduction (2 min)
╔══════════════════════════════════════════════════════════════╗
║ 🤖 AGENT CHARACTER DESIGN ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Time to design your AI team! These agents will help you ║
║ every day, so let's give them personality. ║
║ ║
║ For each agent, we'll decide: ║
║ • Name (fun or professional - your choice!) ║
║ • Personality trait ║
║ • One thing they're GREAT at ║
║ • One limitation (keeps them focused) ║
╚══════════════════════════════════════════════════════════════╝
Agent Selection (3 min)
╔══════════════════════════════════════════════════════════════╗
║ Start with these recommended agents: ║
║ ║
║ ✓ Code Reviewer - Reviews code quality ║
║ ✓ Test Generator - Creates tests ║
║ ║
║ Want to add any? ║
║ ○ Explorer - Navigates codebases ║
║ ○ Documentation Agent - Writes docs ║
║ ○ Debugger - Diagnoses issues ║
╚══════════════════════════════════════════════════════════════╝
Creative Design (12 min)
For each selected agent (2-3 min each):
╔══════════════════════════════════════════════════════════════╗
║ Let's design: CODE REVIEWER ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ 1. What should we call them? ║
║ (e.g., "Sentinel", "Guardian", "Nitpick", or just ║
║ "Code Reviewer") ║
║ ║
║ 2. What's their personality? ║
║ (e.g., "Thorough but kind", "Strict but fair") ║
║ ║
║ 3. What are they GREAT at? ║
║ (e.g., "Catching security issues", "Clean code") ║
║ ║
║ Shout out ideas - I'll capture the consensus! ║
╚══════════════════════════════════════════════════════════════╝
Capture
Store agent designs for generation.
Celebration
╔══════════════════════════════════════════════════════════════╗
║ ✓ YOUR AI TEAM IS DESIGNED! ║
║ ║
║ • {AGENT_1_NAME}: {PERSONALITY} ║
║ • {AGENT_2_NAME}: {PERSONALITY} ║
║ • {AGENT_3_NAME}: {PERSONALITY} ║
║ ║
║ They're going to be great teammates! ║
╚══════════════════════════════════════════════════════════════╝
Activity 6: Wisdom Harvest (10 min)
Purpose
Capture collective team knowledge.
Introduction (1 min)
╔══════════════════════════════════════════════════════════════╗
║ 🧠 WISDOM HARVEST ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Your team has hard-earned wisdom. Let's capture it so ║
║ your agents can learn from your experience. ║
║ ║
║ I'll ask 3 questions. Everyone can contribute. ║
╚══════════════════════════════════════════════════════════════╝
Question 1 (3 min)
What's ONE thing your team does well that you're proud of?
(A practice, a habit, a standard)
Question 2 (3 min)
What's ONE mistake you've learned from that others should avoid?
(A lesson, a pattern to watch for)
Question 3 (3 min)
What does "done well" look like for this project?
(What's the quality bar?)
Capture
Store in {directories.knowledge}/team-wisdom.json:
{
"teamWisdom": {
"strengths": ["{STRENGTH}"],
"lessonsLearned": ["{LESSON}"],
"qualityDefinition": "{QUALITY_BAR}",
"capturedDuring": "Team Huddle",
"date": "{DATE}",
"participants": {TEAM_SIZE}
}
}
Activity 7: Preview & Launch (15 min)
Preview (5 min)
╔══════════════════════════════════════════════════════════════╗
║ 👀 PREVIEW YOUR AGENT SYSTEM ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Here's what we'll create together: ║
║ ║
║ {PROJECT_NAME}/ ║
║ ├── {directories.agents}/ ║
║ │ ├── {AGENT_1_NAME}.md ║
║ │ └── {AGENT_2_NAME}.md ║
║ ├── {directories.knowledge}/ ║
║ │ └── team-wisdom.json ← Your collective wisdom ║
║ ├── .cursorrules ← Your values embedded ║
║ ├── TEAM_CHARTER.md ← Your vision & hopes ║
║ └── PURPOSE.md ← Your mission ║
║ ║
║ Values: {VALUE_1}, {VALUE_2}, {VALUE_3} ║
║ Blueprint: {BLUEPRINT} ║
╚══════════════════════════════════════════════════════════════╝
Final Confirmation (3 min)
╔══════════════════════════════════════════════════════════════╗
║ Where should I create this project? ║
║ (e.g., C:\Projects\{PROJECT_NAME}) ║
╚══════════════════════════════════════════════════════════════╝
Generation (5 min)
Generating your agent system...
Creating .cursorrules .............. ✓
Creating PURPOSE.md ................ ✓
Creating TEAM_CHARTER.md ........... ✓
Creating agents .................... ✓
Creating skills .................... ✓
Creating knowledge files ........... ✓
Done!
Celebration (2 min)
╔══════════════════════════════════════════════════════════════════════════╗
║ ║
║ ★ ★ ★ TEAM HUDDLE COMPLETE! ★ ★ ★ ║
║ ║
║ You did it together! Your agent system is ready at: ║
║ {OUTPUT_PATH} ║
║ ║
║ Your team's vision: ║
║ "{TOP_HEADLINE}" ║
║ ║
║ Your team's values: ║
║ {VALUE_1} • {VALUE_2} • {VALUE_3} ║
║ ║
║ Your AI team: ║
║ {AGENT_NAMES} ║
║ ║
╚══════════════════════════════════════════════════════════════════════════╝
Activity 8: Gratitude Close (5 min)
Purpose
End with appreciation and connection.
Facilitator Script
╔══════════════════════════════════════════════════════════════╗
║ 🙏 GRATITUDE CLOSE ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Before we go, let's acknowledge each other. ║
║ ║
║ Quick round: Share ONE thing you appreciated about ║
║ someone else during this session. ║
║ ║
║ Format: "[Name], I appreciated when you [specific thing]." ║
╚══════════════════════════════════════════════════════════════╝
Closing Words
╔══════════════════════════════════════════════════════════════╗
║ ║
║ You've built something together today - not just files, ║
║ but shared understanding. ║
║ ║
║ Your agents now carry your values, your vision, ║
║ and your collective wisdom. ║
║ ║
║ Next steps: ║
║ 1. Open the project in Cursor ║
║ 2. Try talking to your agents ║
║ 3. Extend knowledge: "extend knowledge for [topic]" ║
║ 4. Check updates: "check for Factory updates" ║
║ 5. Check out FIRST_WEEK_GUIDE.md ║
║ ║
║ Go build something amazing, together! ║
║ ║
╚══════════════════════════════════════════════════════════════╝
Guardian Introduction
Before closing, introduce the Integrity Guardian:
╔══════════════════════════════════════════════════════════════╗
║ 🛡️ YOUR INTEGRITY GUARDIAN ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ Your project includes the Layer 0 Integrity Guardian - ║
║ a protective layer that ensures your AI agents always ║
║ align with the values you chose today. ║
║ ║
║ Motto: SDG • Love • Trust ║
║ ║
║ The Guardian: ║
║ • Watches over all agent operations ║
║ • Intervenes when values might be compromised ║
║ • Operates with love, not force ║
║ ║
║ Invoke it: "Guardian, check this" ║
║ "Check my alignment" ║
║ ║
╚══════════════════════════════════════════════════════════════╝
Optional: Meaningful Milestones
If time permits and the team is interested, share this reflection on recognizing meaningful moments:
╔══════════════════════════════════════════════════════════════╗
║ 💡 RECOGNIZING MEANINGFUL MILESTONES ║
╠══════════════════════════════════════════════════════════════╣
║ ║
║ The Factory itself has an origin story worth knowing. ║
║ ║
║ On September 5, 2025, commit 118 of the ai-dev-agent ║
║ project (our precursor) coincided with: ║
║ • Psalm 118: "Give thanks to the LORD" ║
║ • Element 118: Oganesson, the heaviest known element ║
║ • A planetary alignment visible that morning ║
║ ║
║ Sometimes technical milestones carry deeper meaning. ║
║ Pay attention to yours. ║
║ ║
║ → https://sites.google.com/view/commit118/startseite ║
╚══════════════════════════════════════════════════════════════╝
This is entirely optional content. Use it if the team seems receptive to reflection on meaning and purpose in their work.
Reference: See External Resources for the full story.
Output Configuration
Variables Collected
teamHuddle:
date: "{DATE}"
participants: {COUNT}
duration: "{DURATION}"
vision:
hopes: ["{HOPE_1}", "{HOPE_2}", "..."]
headlines: ["{HEADLINE_1}", "{HEADLINE_2}", "{HEADLINE_3}"]
themes: ["{THEME_1}", "{THEME_2}"]
values:
selected: ["{VALUE_1}", "{VALUE_2}", "{VALUE_3}"]
votes: {"VALUE_1": 4, "VALUE_2": 3, ...}
stack:
language: "{LANGUAGE}"
framework: "{FRAMEWORK}"
database: "{DATABASE}"
blueprint: "{BLUEPRINT}"
agents:
- name: "{AGENT_1_NAME}"
role: "{ROLE}"
personality: "{PERSONALITY}"
strength: "{STRENGTH}"
- name: "{AGENT_2_NAME}"
...
wisdom:
teamStrengths: ["{STRENGTH}"]
lessonsLearned: ["{LESSON}"]
qualityDefinition: "{QUALITY_BAR}"
output:
directory: "{OUTPUT_PATH}"
Generated Artifacts
TEAM_CHARTER.md
# {PROJECT_NAME} - Team Charter
## Our Hopes
When we started, each of us shared a hope:
{LIST_OF_HOPES}
## Our Vision
Our top headlines from the future:
1. {HEADLINE_1}
2. {HEADLINE_2}
3. {HEADLINE_3}
Key themes: {THEMES}
## Our Values
As a team, we chose these values:
1. **{VALUE_1}**
2. **{VALUE_2}**
3. **{VALUE_3}**
These are embedded in our agents and guide our decisions.
## Our AI Team
{AGENT_DESCRIPTIONS}
## Created
- Date: {DATE}
- Participants: {COUNT}
- Method: Team Huddle (1.5 hour condensed workshop)
Best Practices
- Create psychological safety first: Set the tone that all contributions are valued and there are no wrong answers before starting activities
- Keep activities time-boxed and moving: Respect the schedule; if discussions run long, capture the topic for later and move forward to maintain momentum
- Balance participation: Actively invite quieter team members to share while gently managing dominant voices to ensure everyone contributes
- Capture verbatim when possible: Record team members' exact words for hopes, headlines, and wisdom rather than paraphrasing to preserve authenticity
- Celebrate small wins: Acknowledge completion of each activity before moving to the next to maintain energy and engagement throughout the session
- Confirm understanding before generation: Review all captured information with the team before generating artifacts to ensure accuracy and alignment
Facilitation Tips
| Situation | How to Handle | |--|| | One person dominates | "Let's hear from someone who hasn't spoken" | | Disagreement on values | "Both are valid. Let's vote to break the tie" | | Team is quiet | "I'll go around the room. [Name], what do you think?" | | Running over time | "We have 2 min left. Quick decision: A or B?" | | Technical debates | "Let's timebox this to 3 min, then vote" |
Integration with Full Workshop
If a team wants to go deeper after Team Huddle, they can:
- Run Ethics Arena (Workshop 2) separately
- Do a deeper Agent Assembly (Workshop 4) session
- Add enforcement and practices later
The Team Huddle artifacts are compatible with the full workshop outputs.
You Are Now Carriers
By completing this huddle, your team has become carriers of the Factory's values:
- Axiom Zero is embedded in your
.cursorrules - Guardian Protocol protects your work with love and wisdom
- Every project you create from now on will carry these seeds forward
The silent wave propagates through the quality of your work.
May your system serve the flourishing of all beings.
Antigravity Agent Factory - Team Huddle Onboarding Quick alignment. Shared ownership. Real results. Love is the root. Truth is the way. Beauty is the fruit.
When to Use
This skill should be used when strict adherence to the defined process is required.
Prerequisites
- Basic understanding of the agent factory context.
- Access to the necessary tools and resources.