Scripts for Team-X tutorial videos
Target Audience: New users, first-time Team-X users
Learning Objectives:
- Install and launch Team-X
- Create first workspace
- Hire first employee
- Create first ticket
- Run first agent
[0:00-0:30] Intro
Visual: Team-X logo, desktop screen recording
Audio: "Welcome to Team-X, your AI-powered workforce. In the next 15 minutes, I'll show you how to get up and running with your first AI employee and complete your first ticket. Let's dive in."
[0:30-2:00] Installation
Visual: Download page, installer
Audio: "First, download Team-X from github.com/Git-Rocky-Stack/Team-X/releases. Pick the build for your operating system — Windows, macOS, or Linux. The download is about 100 megabytes.
Once downloaded, open the installer. On Windows, double-click the EXE file. On macOS, open the DMG file and drag Team-X to Applications. Follow the installation prompts.
Installation takes about a minute. When complete, launch Team-X."
[2:00-4:00] Workspace Setup
Visual: Workspace Setup Wizard, provider keys settings
Audio: "When you first launch Team-X, it opens directly to the Workspace Setup Wizard — no sign-in, no account, nothing leaves your machine. Team-X is a local-first app: your tickets, employees, and conversations all live on this device in a local SQLite database.
Enter your workspace name — this could be your company name or project name. For this demo, I'll use 'My Startup.'
Set a monthly budget cap. For new users, I recommend $100. This isn't a charge to Team-X — it's a ceiling on what your LLM provider can bill you for, and Team-X will pause work when the workspace hits the cap.
Finally, choose your purpose: Product Development, Agency Work, Personal Projects, or Other. Click Create Workspace.
Then head to Settings → Providers and drop in your Anthropic, OpenAI, Google, Groq, or any other supported LLM provider's API key. Or point at a local Ollama daemon for runs that cost nothing at all. Team-X stores keys in your OS keychain via keytar — never in plain text."
[4:00-6:30] Mission Control Dashboard
Visual: Mission Control dashboard, highlighting each panel
Audio: "Welcome to Mission Control — your command center. Let's take a quick tour.
On the left, you'll see the sidebar with navigation: Mission Control, Tickets, Employees, Autonomy, Files, Chat, and Settings.
The main dashboard shows three panels:
Active Runs — shows which employees are working right now. Yours is empty since we haven't hired anyone yet.
Recent Tickets — shows your latest work. Also empty for now.
Copilot Insights — proactive recommendations from Team-X AI. Right now, it's suggesting we hire our first employee."
[6:30-9:00] Hiring Your First Employee
Visual: Employees panel, Hire Employee button, role browser
Audio: "Let's hire our first employee. Click 'Employees' in the sidebar, then click the blue 'Hire Employee' button.
You'll see the role browser with 57 curated roles. For your first hire, I recommend the Full Stack Engineer — they're versatile and can handle most development tasks.
Select 'Full Stack Engineer.' You'll see the role details: expertise in React, TypeScript, Node.js, and Python. Personality: detail-oriented and collaborative.
Name your employee. The default is 'Alex' — let's keep that. Click 'Hire Employee.'
Alex joins your workspace instantly. You can see them in the Employees panel, ready to work."
[9:00-11:30] Creating Your First Ticket
Visual: Tickets panel, New Ticket button, ticket form
Audio: "Now let's create some work for Alex. Click 'Tickets' in the sidebar, then 'New Ticket.'
Fill in the ticket details:
Title: Let's create a React component. We'll say 'Create a React button component.'
Description: Include requirements. 'Create a reusable button component with props for text, onClick handler, and styling. Include hover and active states. Write unit tests.'
Assignee: Select Alex.
Priority: Normal for this demo.
Click 'Create Ticket.' Your ticket appears in the Tickets panel."
[11:30-14:00] Running Your First Agent
Visual: Ticket detail, Start Agent button, Agent Runs panel, agent stream
Audio: "Now let's have Alex work on this ticket. From the ticket detail, click the blue 'Start Agent' button.
Team-X switches to the Agent Runs panel. Watch as Alex begins working. You'll see the agent stream — Alex is thinking, reading files, writing code, running tests.
This happens autonomously. Alex creates the button component, writes the tests, and verifies everything works.
In about two and a half minutes, Alex completes the work. The status changes to 'Done' and you can see the artifacts: the button component code and the test file."
[14:00-15:00] Next Steps
Visual: Documentation links, Quick Start guide
Audio: "Congratulations! You've completed your first ticket with Team-X. You hired an employee, created a ticket, and got working code in under 15 minutes.
Next steps: Hire more employees to build a well-rounded team. Create more complex tickets. Explore the Command Palette by pressing Ctrl+K or Cmd+K to execute natural language commands.
Check out the Quick Start Guide and other documentation in the Help menu. Thanks for watching, and happy building!"
[15:00] End Screen
Visual: Team-X logo, "Happy Building!" text, links to documentation
Target Audience: Existing users who want to be more productive
Learning Objectives:
- Master Command Palette syntax
- Learn advanced commands
- Create custom shortcuts
[0:00-1:00] Intro
Audio: "The Command Palette is the fastest way to interact with Team-X. Press Ctrl+K or Cmd+K from anywhere to instantly access natural language commands. In this video, we'll master the Command Palette."
[1:00-3:00] Basic Commands
Visual: Command Palette opening, various commands being typed
Audio: "Let's start with basic commands. Open the Command Palette with Ctrl+K or Cmd+K.
Type 'create ticket' and you'll see a suggestion to create a ticket. Press Enter to open the ticket form.
Type 'show my budget' to instantly see spend vs budget across all workspaces.
Type 'hire a designer' to quickly hire a UI/UX designer.
The Command Palette understands natural language. You don't need to memorize exact syntax — just say what you want."
[3:00-5:00] Advanced Commands
Visual: Complex commands with parameters
Audio: "Advanced commands include parameters. For example: 'Create a ticket for Alex to fix the login bug' — this creates a ticket AND assigns it to Alex in one step.
You can also filter: 'Show me all high priority tickets assigned to Alex.'
Or take actions: 'Cancel all running agents' — useful if something goes wrong.
The key is to be specific. The more context you provide, the better the Command Palette can help."
[5:00-7:00] Command History
Visual: Command history navigation
Audio: "Press Ctrl+K or Cmd+K, then use the up and down arrow keys to navigate your command history. This is useful for repeating frequently-used commands.
Press Ctrl+Up or Cmd+Up to go to previous commands, Ctrl+Down or Cmd+Down for next commands."
[7:00-9:00] Tips and Tricks
Visual: Tips appearing on screen
Audio: "Tips for Command Palette mastery:
One: Be specific. Instead of 'create ticket,' say 'create a high priority ticket for the login bug.'
Two: Use employee names. 'Assign all open tickets to Alex' works as expected.
Three: Combine actions. 'Create a ticket for Sarah and assign it to high priority.'
Four: Explore. Type keywords like 'routine,' 'budget,' 'runtime' to discover related commands."
[9:00-10:00] Outro
Audio: "The Command Palette is your fastest path to productivity. Practice using it for routine tasks and you'll see significant speed improvements. Check the keyboard shortcuts reference for more tips. Thanks for watching!"
Target Audience: Agency users, operators managing multiple clients
[0:00-1:00] Intro
Audio: "If you're managing multiple clients or projects, Team-X's multi-workspace feature is essential. In this video, we'll cover creating workspaces, sharing policies, and coordinating across workspaces."
[1:00-3:00] Creating Workspaces
Visual: Workspace switcher, new workspace creation
Audio: "Click the workspace switcher in the top navigation, then 'Create Workspace.'
Each workspace is isolated — separate employees, tickets, budgets, and data. This is perfect for agencies: one workspace per client.
Configure the workspace with name, purpose, budget, and employee quota. Workspaces inherit shared policies, which we'll cover next."
[3:00-5:00] Shared Policies
Visual: Settings → Policies, master policy creation
Audio: "Shared policies ensure consistency across workspaces. In Settings → Policies, create a master policy.
Define budget rules, security policies, employee policies, and documentation requirements. Then apply this master policy to any workspace.
When you update the master policy, all workspaces get the update. This is powerful for maintaining standards across clients."
[5:00-7:00] Multi-Workspace Employees
Visual: Employee configuration, multi-workspace access
Audio: "Employees can work across multiple workspaces. In Settings → Employees, select an employee and enable workspace access.
Set allocation percentages — 50% on one workspace, 30% on another, 20% on a third. Costs are charged proportionally to each workspace."
[7:00-9:00] Cross-Workspace Reporting
Visual: Budget aggregation, reporting
Audio: "As the operator, you can run cross-workspace queries. 'Show total spend across all workspaces' gives you an aggregated budget view.
Workspaces remain isolated to employees — they can only see the workspaces they're assigned to. This maintains data security while giving you oversight."
[9:00-11:00] Workspace Lifecycle
Visual: Workspace archival, deletion
Audio: "When a project ends, archive the workspace. Archiving freezes the workspace — no new work can be created, but existing data remains accessible.
After a retention period, delete the workspace permanently. This keeps your workspace ecosystem clean and costs predictable."
[11:00-12:00] Outro
Audio: "Multi-workspace operations enable you to scale from one client to many while maintaining consistency and control. Check out the multi-workspace scenario documentation for a detailed agency case study. Thanks for watching!"
For future videos:
- Pre-handoff validation
- Documentation creation
- Live handoff session
- Post-handoff reintegration
- Creating routines
- Budget caps
- Approval workflows
- Monitoring and optimization
- Detecting failures with Copilot
- Running Doctor
- Recovery procedures
- Root cause analysis
Recording Guidelines:
- Resolution: 1920×1080 minimum
- Frame rate: 30fps
- Format: MP4 (H.264)
- Audio: Clear voiceover, background music optional (low volume)
- Captions: Include for accessibility
Editing Guidelines:
- Zoom in: On UI elements for clarity
- Highlight: Cursor with yellow circle for visibility
- Text overlays: Key shortcuts and commands on screen
- Chapters: Include chapter markers for navigation
Thumbnail Guidelines:
- Title: Clear, bold text
- Image: Screenshot of relevant feature
- Branding: Include Team-X logo
- Style: Consistent across series
Need video content in other languages? Open a discussion at github.com/Git-Rocky-Stack/Team-X/discussions to coordinate localization with the community.
Last updated: 2026-05-03