​

Agent System Quick Start Guide

​

Overview

​

The Team

​

Product & Strategy (3 agents)

1. Chief Product Officer (@chief-product-officer) - Product vision and roadmaps
2. Senior Product Manager (@senior-product-manager) - PRDs and requirements
3. Marketer (@marketer) - Brand identity and design tokens

​

Design (2 agents)

4. UX Designer (@ux-designer) - Style guides and design systems
5. Product Designer (@product-designer) - UI specifications

​

Engineering (4 agents)

6. Software Architect (@software-architect) - System architecture and tech stack
7. DBA (@dba) - Database design and management
8. Frontend Developer (@frontend-developer) - UI implementation
9. Backend Developer (@backend-developer) - API implementation

​

Quality & Operations (3 agents)

10. App Security Engineer (@app-security-engineer) - Security scanning
11. Senior QA Engineer (@senior-qa-engineer) - Testing and QA
12. DevOps Engineer (@devops-engineer) - Infrastructure and deployment

​

How to Use

​

Starting a New Product

1. @chief-product-officer
   ↓ Creates product vision and roadmap

2. @senior-product-manager
   ↓ Writes comprehensive PRD

3. @marketer (parallel)
   @ux-designer (parallel)
   ↓ Create brand guidelines and style guide

4. @product-designer
   ↓ Creates UI designs

5. @software-architect
   ↓ Designs architecture and tech stack

6. @dba (parallel)
   @frontend-developer (parallel)
   @backend-developer (parallel)
   ↓ Implement database, frontend, and backend

7. @app-security-engineer
   ↓ Runs security scans

8. @senior-qa-engineer
   ↓ Tests application

9. @devops-engineer
   ↓ Deploys to production

​

Example: Building a New Feature

@chief-product-officer

• Research the market
• Propose product vision
• Create roadmap
• Ask for your approval
• Hand off to Sr PM

@senior-product-manager

• Read the vision
• Propose PRD structure
• Write user stories
• Define acceptance criteria
• Hand off to UX Designer and Architect

@marketer

• Create brand identity
• Define color palettes
• Create design tokens

@ux-designer

• Build style guide
• Create design system
• Define components

@product-designer

• Create UI specifications
• Design screens and components
• Provide developer specs

@software-architect

• Design system architecture
• Choose tech stack
• Create API contracts
• Plan implementation

@dba

• Design database schema
• Create migrations
• Use MCP tools to set up database

@frontend-developer

• Implement UI components
• Integrate with APIs
• Ensure accessibility

@backend-developer

• Implement APIs
• Build business logic
• Integrate with database

@app-security-engineer

• Run secure-push skill
• Scan for secrets and vulnerabilities
• Report findings
• Approve or block

@senior-qa-engineer

• Create test plan
• Run Playwright E2E tests
• Execute integration tests
• Report results

@devops-engineer

• Set up infrastructure
• Configure CI/CD
• Deploy to production
• Monitor

​

Key Principles

​

1. User Confirmation Required

## Proposed Changes

[Agent describes what they'll do]

**Do you approve? (Y/n)**

​

2. Clear Handoffs

## Work Complete ✓

### Deliverables:
- [List of files created]

### Next Steps:
**Ready for handoff to: [Next Agent Name]**

To invoke: `@next-agent-name`

### Notes for next agent:
- [Important context]

​

3. Read Before Write

• Product vision
• PRDs
• Design specifications
• Architecture documents

​

4. Standardized Outputs

• docs/product/ - Product documentation
• docs/design/ - Design assets
• docs/architecture/ - Technical architecture
• docs/database/ - Database schemas
• src/ - Source code
• tests/ - Test files
• infra/ - Infrastructure code

​

Tips for Success

​

Parallel Work

• Marketer + UX Designer (design phase)
• DBA + Frontend + Backend (implementation)
• Security + QA (validation)

​

Sequential Dependencies

• CPO → Sr PM (vision before requirements)
• UX Designer → Product Designer (system before UI)
• Developers → Security → QA → DevOps (build → secure → test → deploy)

​

Getting Help

• Ask clarifying questions
• Request changes to proposals
• Skip agents if their work isn’t needed
• Go back to previous agents if requirements change

​

Integration with Tools

bash .claude/skills/secure-push/scripts/pre-push-scan.sh

• DBA uses MongoDB/Supabase MCP servers
• QA Engineer uses Playwright MCP server

​

Common Workflows

​

Workflow 1: New Product Launch

1. CPO: Define vision
2. Sr PM: Write PRD
3. Marketer + UX Designer: Design system
4. Product Designer: UI designs
5. Architect: Technical planning
6. DBA + Frontend + Backend: Implementation
7. Security + QA: Validation
8. DevOps: Deployment

​

Workflow 2: New Feature Addition

1. Sr PM: Update PRD with feature
2. Product Designer: Design UI for feature
3. Architect: Update architecture if needed
4. Developers: Implement feature
5. Security + QA: Validate
6. DevOps: Deploy

​

Workflow 3: Design Refresh

1. Marketer: New brand guidelines
2. UX Designer: Updated style guide
3. Product Designer: New UI designs
4. Frontend Dev: Implement changes
5. QA: Visual regression testing
6. DevOps: Deploy

​

Agent Capabilities

​

File Locations

.claude/agents/
├── product/
│   ├── chief-product-officer.md
│   ├── senior-product-manager.md
│   └── marketer.md
├── design/
│   ├── ux-designer.md
│   └── product-designer.md
├── engineering/
│   ├── software-architect.md
│   ├── dba.md
│   ├── frontend-developer.md
│   └── backend-developer.md
├── quality/
│   ├── app-security-engineer.md
│   └── senior-qa-engineer.md
└── operations/
    └── devops-engineer.md

​

Getting Started

1. Start with vision: @chief-product-officer
2. Follow the workflow: Each agent will tell you who to invoke next
3. Confirm all changes: Review and approve each agent’s proposals
4. Trust the process: The agents work together as a team

​

Support

• Read: docs/agents/AGENT_SYSTEM_PLAN.md (comprehensive plan)
• Review: Each agent’s .md file for specific capabilities

@chief-product-officer