Agent Team
John - Product Manager
PRD creation, requirements discovery, stakeholder alignment
Winston - Architect
Distributed systems, cloud infrastructure, API design
Amelia - Developer
Story execution, test-driven development, code implementation
Quinn - QA Engineer
Test automation, API testing, E2E testing, coverage analysis
Bob - Scrum Master
Sprint planning, story preparation, agile ceremonies
Sally - UX Designer
User research, interaction design, UI patterns
Mary - Business Analyst
Market research, competitive analysis, requirements elicitation
Paige - Technical Writer
Documentation, Mermaid diagrams, standards compliance
Barry - Quick Flow Solo Dev
Rapid spec creation, lean implementation, minimum ceremony
Agent Collaboration
Agents work together across different phases:Analysis Phase
- Mary (Analyst) conducts market, domain, and technical research
- Mary creates product briefs
Planning Phase
- John (PM) creates and validates PRDs
- Sally (UX Designer) designs user experiences
Solutioning Phase
- Winston (Architect) creates technical architecture
- John (PM) creates epics and stories
- John, Winston, Sally verify implementation readiness
Implementation Phase
- Bob (Scrum Master) plans sprints and prepares stories
- Amelia (Developer) implements stories with TDD
- Quinn (QA) generates automated tests
- Amelia performs code reviews
Documentation Phase
- Paige (Tech Writer) documents projects and explains concepts
Invoking Agents
Agents are invoked through their menu commands. Each agent has specific triggers:Agent Configuration
All agents are defined in YAML files located at:- metadata: ID, name, title, icon, capabilities
- persona: Role, identity, communication style, principles
- menu: Available commands and workflows
- critical_actions: Key behaviors (for some agents)
- prompts: Welcome messages and guidance (for some agents)
