Generate Your PRD Free — No account required
Try PRD Generator →
Context Ark Logo
Context Ark

The Agent Roster

Context Ark doesn't just use "one big prompt." We deploy a Swarm of Specialist Agents, each with a specific persona, improved context window, and success criteria.

This separation of concerns ensures that your Database Schema isn't written by a Creative Writer, and your Marketing Copy isn't written by a Database Admin.

The 5 Personas

1. The Product Owner (PO)

  • Focus: User Value, Business Goals, Scope.
  • Output: PRDs (Product Requirement Docs), User Stories, Success Metrics.
  • Files: 01_Product/*.md, 02_Users/*.md

2. The Chief Architect

  • Focus: System Design, Scalability, Data Models.
  • Output: Architecture Diagrams (Mermaid), Database Schemas (SQL), API Specifications.
  • Files: 04_Architecture/*.md

3. The Senior Engineer

  • Focus: Implementation Details, Libraries, Code Patterns.
  • Output: Tech Specs, Frontend Guidelines, Context Rules for Cursor/Cline.
  • Files: 03_Context/*.md, 05_Security/*.md

4. The QA Lead

  • Focus: Edge Cases, Testing Strategy, Validation.
  • Output: Test Plans, E2E Scenarios.
  • Files: TESTING_STRATEGY.md

5. The DevOps Engineer

  • Focus: Deployment, CI/CD, Environment Variables.
  • Output: Deployment Guides, Env Var templates.
  • Files: DEPLOYMENT.md

How They Collaborate

The agents work in a directed acyclic graph (DAG).

  1. PO defines What to build.
  2. Architect defines How to structure it.
  3. Senior Engineer defines How to code it.

This flow ensures that the code implementation (Engineer) never contradicts the business goals (PO).