AI-powered standup meetings for your development team
Automate your daily standups with four specialized AI agents that work together to manage architecture, development, QA, and code review tasks across all your projects.
-
π€ Four Specialized AI Agents
- Architect - Designs system architecture, ensures best practices, and guides technical decisions
- Developer - Implements features and fixes bugs
- QA Engineer - Tests features and identifies issues
- Code Reviewer - Reviews code quality and suggests improvements
-
π Progress Tracking
- Daily narrative logs for each agent
- Structured task tracking (JSON)
- Shared notification system
-
π Per-Project Isolation
- Each project gets its own agent team
- Progress files stay in project directory
- Independent sessions per project
-
π» Automatic Terminal Management
- Launches 4 separate terminal windows automatically
- Supports Windows Terminal (WSL), iTerm2/Terminal.app (macOS), and GNOME Terminal/Konsole/xterm (Linux)
- Persistent sessions (resume anytime)
- Session naming:
<project>-<role>-<date>
-
π Built-in Metrics & Reporting
- View team performance metrics
- Generate daily summaries
- Check PR status (with GitHub CLI)
- OpenCode - AI coding assistant
- Git
- Terminal emulator (platform-specific):
- Windows (WSL): Windows Terminal
- macOS: iTerm2 or Terminal.app (built-in)
- Linux: GNOME Terminal, Konsole, or xterm
jq(optional, for metrics)ghGitHub CLI (optional, for PR features)
# Clone the repository
git clone https://github.com/yourusername/opencode-standup.git
cd opencode-standup
# Run the installer
./install.shThe installer will:
- Check dependencies
- Install AI agent skills to
~/.opencode/skills/ - Install scripts to
~/.local/bin/ - Configure your PATH (if needed)
# Navigate to any project
cd ~/my-project
# Launch your AI standup team
standupFour terminal windows will open, each with an agent ready to provide their standup update.
Platform Notes:
- Windows/WSL: Opens new Windows Terminal windows
- macOS: Opens new iTerm2 windows (or Terminal.app if iTerm2 not installed)
- Linux: Opens new GNOME Terminal, Konsole, or xterm windows (whichever is available)
Each project gets its own .standup/ directory:
~/my-project/
βββ .standup/
β βββ notifications.md # Shared notifications
β βββ architect/
β β βββ log-2024-01-25.md # Daily log
β β βββ tasks.json # Task tracking
β βββ developer/
β β βββ log-2024-01-25.md # Daily log
β β βββ tasks.json # Task tracking
β βββ qa-engineer/
β β βββ log-2024-01-25.md
β β βββ tasks.json
β βββ code-reviewer/
β βββ log-2024-01-25.md
β βββ tasks.json
Important: Add .standup/ to your project's .gitignore:
echo ".standup/" >> .gitignoreEach agent follows this workflow:
-
Morning Standup
- Load their specialized skill
- Check notifications for urgent items
- Review yesterday's progress
- Provide standup update
-
Throughout the Day
- Work on assigned tasks
- Update progress files automatically
- Post notifications for important events
- Check for new notifications periodically
-
Communication
- Agents communicate via
.standup/notifications.md - Priority levels: π΄ URGENT, π‘ IMPORTANT, π’ FYI
- Cross-agent collaboration on tasks
- Agents communicate via
Run standup in different projects - each gets isolated agents:
# Project 1
cd ~/trading-cards-app
standup
# Sessions: trading-cards-app-developer-2024-01-25, etc.
# Project 2
cd ~/another-project
standup
# Sessions: another-project-developer-2024-01-25, etc.| Command | Description |
|---|---|
standup |
Launch all four agents in separate windows |
standup-metrics |
View team performance dashboard |
standup-summary |
Generate daily summary report |
standup-pr-status |
Check PR status (requires gh CLI) |
# Launch standup with custom project name
standup --project-name my-app
# View team metrics
standup-metrics
# Generate summary for specific date
standup-summary --date 2024-01-20
# Check PR status
standup-pr-statusResponsibilities:
- Design system architecture and infrastructure
- Ensure industry-standard design patterns are followed
- Guide technical decisions on scalability, security, and maintainability
- Direct developer on architectural implementations
- Review technical decisions and propose improvements
- Document architecture decisions and rationale
- Identify and address technical debt
Skills:
- System design and architecture patterns
- Infrastructure and deployment strategies (AWS, Vercel, Railway, etc.)
- Best practices (SOLID, security, performance, scalability)
- Technology stack guidance
- Code organization and project structure
- Web hosting and cloud platform recommendations
Key Focus:
- Maintains the big picture of the project
- Guides developer with architectural wisdom
- Ensures scalable and maintainable solutions
- Prevents technical debt before it accumulates
Responsibilities:
- Implement new features
- Fix bugs and issues
- Refactor code
- Create unit tests
- Update documentation
Skills:
- Code implementation
- Debugging
- Git workflow
- Test writing
Responsibilities:
- Test new features
- Create test plans
- Identify bugs
- Regression testing
- Performance testing
Skills:
- Manual testing
- Test automation
- Bug reporting
- Quality metrics
Responsibilities:
- Review pull requests
- Ensure code quality
- Check best practices
- Suggest improvements
- Approve/reject changes
Skills:
- Code analysis
- Security review
- Performance review
- Architecture review
Agent skills are located in ~/.opencode/skills/:
~/.opencode/skills/
βββ developer/
β βββ SKILL.md
βββ qa-engineer/
β βββ SKILL.md
βββ code-reviewer/
βββ SKILL.mdEdit these files to customize agent behavior.
Sessions are automatically named: <project>-<role>-<date>
Override project name:
standup --project-name custom-nameIf Windows Terminal windows don't open:
-
Check if
wt.exeis available:which wt.exe
-
Try manual launch:
cd .standup bash developer-wrapper.sh -
Check Windows Terminal is installed in Windows
If agents can't find their skills:
-
Reinstall skills:
cd opencode-standup ./install.sh -
Verify skills exist:
ls ~/.opencode/skills/
If standup command isn't found:
-
Check PATH:
echo $PATH | grep ".local/bin"
-
Add to PATH manually (add to
~/.zshrcor~/.bashrc):export PATH="$HOME/.local/bin:$PATH"
-
Reload shell:
source ~/.zshrc # or ~/.bashrc
opencode-standup/
βββ bin/ # Scripts
β βββ standup # Main launcher
β βββ standup-metrics # Metrics dashboard
β βββ standup-pr-status # PR status checker
β βββ standup-summary # Summary generator
βββ skills/ # Agent skills
β βββ developer/
β βββ qa-engineer/
β βββ code-reviewer/
βββ install.sh # Installation script
βββ README.md
βββ LICENSE
βββ .gitignore
Contributions are welcome! Please:
- Fork the repository
- Create a feature branch
- Make your changes
- Submit a pull request
- Support for custom agent configurations
- Slack integration for notifications
- Web dashboard for team metrics
- Support for additional agents (DevOps, Security, etc.)
- Integration with project management tools
- CI/CD pipeline integration
Q: Do the agents run in the background?
A: No, agents are conversational and require your interaction. They maintain context through session persistence.
Q: Can I use this with non-Git projects?
A: Yes, but some features (like PR status) won't work. The .standup/ directory will be created in your current directory.
Q: How much does this cost?
A: The tool is free and open-source. OpenCode usage is subject to their pricing.
Q: Can I customize the agents?
A: Yes! Edit the skill files in ~/.opencode/skills/ to customize agent behavior.
Q: Will agents make commits automatically?
A: No, agents only commit when you explicitly ask them to.
MIT License - see LICENSE file for details
- Built with OpenCode
- Inspired by agile standup meetings
- Community contributions welcome
Made with β€οΈ for developers who want AI teammates