Project Binder Generator

Build your team's collaboration foundation in 7 steps

Let's start with your beliefs 🌟

These beliefs ground your approach to working with AI. They're your team's philosophy—what you believe about AI collaboration and what makes it powerful. Create 3 belief statements by choosing from each column.

Example: "I believe that AI can be a true creative collaborator and is powerful when we iterate together on outputs."

Tell me about your project 🎯

This is your team's north star—what you're building and why. Clear purpose keeps everyone (AI and human) aligned on what matters.

Example: "We're building a guide series to help non-technical teams work confidently together. Success looks like readers can set up their first Project Binder in under 15 minutes."

Let's define your voice 🎤

Your voice is how you communicate—the tone, personality, and style that makes your content distinctly yours. Be specific! "Professional" tells AI nothing. "Warm and direct, like a trusted colleague" gives clear direction.

Example: "Authentic & vulnerable, Conversational & relatable, Actionable & practical"
Avoid: "Corporate jargon, Hype without proof"

What our voice IS

What we AVOID

Show me with examples

Who's on your team? 👥

Tell me about everyone on your team—humans and AI. Who are they? What are their primary responsibilities?

Example:
Maura (Human) - Title/Role: Product Lead. Primary Responsibilities: Final product decisions, strategic direction, user perspective.
CP (AI - ChatGPT) - Title/Role: Creative Partner. Primary Responsibilities: Rapid ideation, multiple variations, creative exploration.
Soph (AI - Claude) - Title/Role: Chief of Staff. Primary Responsibilities: Synthesis, documentation, technical architecture.

💡 Consider adding Alpha Redi

Alpha Redi is an AI assistant designed specifically for team rituals and decision-making tools. Redi provides contextual help within your apps—acting as a Consensus Driver in Co-Sign, Pattern Analyzer in AlignFirst, and Risk Navigator in Sprint Kickoff.

Title/Role: Team Facilitator
Primary Responsibilities: Consensus driving, pattern recognition, decision support, contextual recommendations

Your context library 📚

What essential documents, decisions, or references should your team always have access to? This is your team's institutional knowledge.

Essential docs: Brand guidelines, product roadmap, user research
Key decisions: We're focusing on non-technical users first, We prioritize clarity over features

Essential Documents

Key Decisions

How does your team sync? 📄

Communication protocols keep your team aligned. How often do you check in? How do you pass context when threads end?

Sync pattern: Daily async updates, weekly deep-dives
Handoff process: End every thread with a note documenting decisions and next steps

Your decision framework 🎲

How does your team make decisions? What's your process when you're aligned? What do you do when you're stuck?

Decision process: Run assumption checks, consult brand guidelines, human has final say
When stuck: Reframe the problem, take a trust check if energy feels off

Your Project Binder is ready! 🎉

Here's everything we built together. You can download the complete Project Binder for documentation, or just the Team Context Card to import across your ritual apps.

✓ All 7 elements complete! Your Project Binder is ready to use.

Full Project Binder: Markdown file with all your project context
Team Context Card: JSON file to import into Co-Sign, Sprint Kickoff, and other ritual apps