Billy Hart
Defines goals, provides requirements, and reviews the team's output. The human in the lead.
This page shows the orchestrated team of AI agents that collaboratively design, develop, and test this portfolio. Each agent specializes in a specific role—designer, developer, tester—coordinated by an Orchestrator.
Defines goals, provides requirements, and reviews the team's output. The human in the lead.
Routes tasks to team members, manages memory across projects, and aggregates results back to Billy.
Always ActiveCreates design specifications, layouts, visual systems, and accessibility guidelines.
Spawned on DemandBuilds features from design specs, writes clean code, and follows established project patterns.
Spawned on DemandVerifies implementation against requirements, tests accessibility, and provides quality reports.
Spawned on DemandRole: Project Owner & Final Reviewer
Billy is the human in the lead who initiates projects, defines requirements, and provides feedback on deliverables. The entire agent system exists to serve Billy's goals and execute his vision.
Role: Team Coordinator & Memory Manager
The Orchestrator is the central coordination hub that manages all team activities. It routes tasks to appropriate agents, maintains project memory, and ensures quality handoffs between team members.
Role: UI/UX & Visual Design Specialist
The Designer creates comprehensive design specifications including layouts, visual systems, interactions, and accessibility guidelines. They establish design systems and ensure visual consistency across projects.
Role: Full-Stack Implementation Specialist
The Developer transforms design specifications into working code. They write clean, maintainable code that follows established patterns and respects performance constraints for the Raspberry Pi deployment environment.
Role: Quality Assurance & Validation Specialist
The Tester verifies that implementations meet requirements and maintain quality standards. They test functionality, accessibility, responsive design, and performance to ensure deliverables are ready for deployment.
Typical task pipeline showing how agents collaborate:
If any agent needs clarification, they can loop back through the Orchestrator for answers.
The agent system is designed to add new teams as needed—for example, a communications team, content team, or specialized tooling teams.
New specialist teams can be added to handle different domains like content strategy, marketing, or technical documentation.