Skip to main content

Analyst

The Analyst agent turns a rough idea into clear, actionable requirements. It is usually the first stop for a new feature or problem statement.

When to use Analyst​

  • The problem is ambiguous or spans multiple stakeholders.
  • You want a PRD-style document before architecture or coding.
  • You need the agent to challenge assumptions and surface missing constraints.

Typical outputs​

  1. High-confidence path — When the agent is confident it understands the ask, it writes a structured product/requirements artifact on the card (often referred to as PRD-style documentation).
  2. Clarification path — When confidence is lower, it may post a form with specific questions. Your answers let the agent resume and finish the write-up.

What to put in the card​

  • Goal and non-goals
  • Users and scenarios
  • Constraints (time, tech, compliance)
  • Links to tickets, designs, or prior discussions

Short titles help on the board; put detail in the description.

After Analyst​

  • Review the artifact for accuracy.
  • Move the card to Architect (or create a new Architect card and attach the Analyst artifact).