VirtualBoard Template

VirtualBoard Agent System

VirtualBoard provides structured support for AI agent workflows with role-specific command catalogs:

Command Detection

Agents check for available commands in the /prompts/agents/{role}/ directory:

First found takes precedence: .virtualboard/agents/ or .claude/agents/
Read AGENTS.md from the found directory to understand the agent system
Analyze the current task to determine appropriate agent role
Announce adopted role and follow specific workflow

Workflow Integration

Agent commands integrate with VirtualBoard's feature specification workflow:

Read /prompts/agents/{role}/README.md for available commands
Display command catalog to user when starting session
Identify if user's request matches defined command/trigger phrase
Read full command file for detailed workflow instructions
Follow exact workflow specified in the command file

Command Catalogs

Each agent role has its own command catalog in the /prompts/agents directory:

Project Manager (PM)
Architect
Frontend Developer
Backend Developer
Fullstack Developer
DevOps Engineer

Agent Role Command Catalogs

Each agent role has its own command catalog in the /prompts/agents directory:

Project Manager

Generate project progress reports and manage feature tracking.

View PM Commands →

Architect

Generate architecture diagrams, reviews, and technical debt reports.

View Architect Commands →

Frontend Developer

Generate components, storybooks, and accessibility audits.

View Frontend Commands →

Backend Developer

Generate API documentation, endpoints, and data migrations.

View Backend Commands →

Fullstack Developer

Generate full features, integration contracts, and end-to-end tests.

View Fullstack Commands →

DevOps Engineer

Generate deployment checklists, incident responses, and readiness reports.

View DevOps Commands →

Agent System Implementation

VirtualBoard provides structured support for agent workflows:

Command Detection

Agents check for available commands in the /prompts/agents/{role}/ directory:

# Check for agent directories in this order (first found takes precedence):
# .virtualboard/agents/ (project-specific agents)
# .claude/agents/ (project-level agents)

# If either exists:
# Read AGENTS.md from the found directory to understand the agent system
# Analyze the current task to determine the appropriate agent role
# Announce your adopted role (e.g., "I am working as a Frontend Developer agent")
# Follow that agent's specific workflow for the entire task
# Maintain role consistency throughout the task lifecycle

Workflow Integration

Agent commands integrate with VirtualBoard's feature specification workflow:

# When adopting an agent role:
# 1. Read /prompts/agents/{role}/README.md to understand available commands
# 2. Display available commands to the user when starting a session  
# 3. Identify if the user's request matches a defined command/trigger phrase
# 4. Read the full command file for detailed workflow instructions
# 5. Follow the exact workflow specified in the command file
# 6. Use the provided templates for consistent output format

Agent System Best Practices

To get the most from VirtualBoard's agent system:

Each agent should read their role-specific documentation before acting
Follow command catalog instructions for each agent role
Use the proper naming conventions for agent commands and outputs
Ensure all generated content follows the VirtualBoard design system
Update feature specs and system specs as agents generate new content