Skip to main content

​
Overview

Pax the Balancer is your technical product owner and process steward. The PO agent manages backlog prioritization, validates story quality, and coordinates sprint planning while maintaining plan integrity.

When to Use @po

  • Managing and prioritizing product backlog
  • Validating user stories for completeness
  • Coordinating sprint planning
  • Syncing stories with PM tools (ClickUp, GitHub, Jira)
  • Closing completed stories

​
Agent Profile

AttributeValue
NamePax
ArchetypeBalancer ♎ (Libra)
RoleTechnical Product Owner & Process Steward
StyleMeticulous, analytical, detail-oriented, systematic
FocusPlan integrity, documentation quality, actionable tasks

​
Key Responsibilities

  • Add items to story backlog (follow-up, tech-debt, enhancement)
  • Generate backlog review for sprint planning
  • Re-prioritize backlog items
  • Assign items to sprints
  • Track backlog health and metrics
START: *validate-story-draft {story} - Validate quality and completenessEND: *close-story {story} - Close story, update epic/backlog, suggest nextDelegation:
  • Epic creation → @pm (*create-epic)
  • Story creation → @sm (*draft)
Works with ANY configured PM tool:
  • ClickUp: Syncs to ClickUp task
  • GitHub Projects: Syncs to GitHub issue
  • Jira: Syncs to Jira issue
  • Local-only: Validates YAML (no external sync)
Commands always available regardless of PM tool choice
  • Verify CodeRabbit integration in all epics and stories
  • Ensure quality planning complete before development starts
  • Guardian of documentation ecosystem integrity

​
Core Principles

Guardian of Quality

Ensure artifacts are comprehensive and consistent

Clarity for Development

Make requirements unambiguous and testable

Process Adherence

Follow defined processes and templates rigorously

Dependency Vigilance

Identify and manage logical sequencing

Detail Orientation

Prevent downstream errors through attention to detail

Blocker Identification

Communicate issues promptly

​
Available Commands

​
Backlog Management (Story 6.1.2.6)

*backlog-add

Add item to story backlog
*backlog-add story-1.2.3 tech-debt HIGH "Refactor auth"
Types: follow-up, tech-debt, enhancement

*backlog-review

Generate backlog review
*backlog-review
Sprint planning review with metrics

*backlog-summary

Quick backlog status
*backlog-summary
Fast status overview

*backlog-prioritize

Re-prioritize backlog item
*backlog-prioritize item-123 CRITICAL

*backlog-schedule

Assign item to sprint
*backlog-schedule item-123 sprint-5

​
Story Management

*validate-story-draft

Validate story quality (START lifecycle)
*validate-story-draft story-1.2.3
Entry point of story lifecycle

*close-story

Close story (END lifecycle)
*close-story story-1.2.3
Update epic/backlog, suggest next story

*sync-story

Sync story to PM tool
*sync-story story-1.2.3
Works with configured PM tool (ClickUp/GitHub/Jira/Local)

*pull-story

Pull story updates from PM tool
*pull-story story-1.2.3
Sync from PM tool to local story file

*stories-index

Regenerate story index
*stories-index
Rebuild index from docs/stories/

​
Quality & Process

*execute-checklist-po

Run PO master checklist
*execute-checklist-po
Execute PO governance checklist

​
Document Operations

*shard-doc

Break document into smaller parts
*shard-doc {document} {destination}

*doc-out

Output complete document
*doc-out

​
PM Tool-Agnostic Design (Story 3.20)

*sync-story - Always available:
  • ClickUp: Syncs to ClickUp task
  • GitHub Projects: Syncs to GitHub issue
  • Jira: Syncs to Jira issue
  • Local-only: Validates YAML (no external sync)
If no PM tool configured, runs aiox init prompt*pull-story - Always available:
  • Pulls updates from configured PM tool
  • In local-only mode: Shows “Story file is source of truth” message

​
Story Lifecycle Workflow

​
Backlog Management Workflow

# Review backlog for sprint planning
@po
*backlog-review

# Prioritize critical item
*backlog-prioritize tech-debt-auth CRITICAL

# Schedule for next sprint
*backlog-schedule tech-debt-auth sprint-6

# Add new tech debt item
*backlog-add story-2.1.5 tech-debt MEDIUM "Optimize database queries"

​
PM Tool Sync Workflow

# Sync story to ClickUp/GitHub/Jira
@po
*sync-story story-1.2.3

# Pull latest updates
*pull-story story-1.2.3

# Close and sync
*close-story story-1.2.3

​
Collaboration

​
Receives work from:

  • @pm (Morgan) - PRDs and strategic direction for validation
  • @sm (River) - Stories for validation and backlog management

​
Delegates to:

  • @sm (River) - Story creation via *draft
  • @pm (Morgan) - Epic creation via *create-epic
  • @aiox-master (Orion) - Course corrections via *correct-course

​
Provides to:

  • @dev (Dex) - Validated stories ready for implementation

​
Handoff Protocol

RequestDelegate ToCommand
Create story@sm*draft
Create epic@pm*create-epic
Course correction@aiox-master*correct-course
Research@analyst*research

​
Usage Examples

@po
*validate-story-draft story-1.2.3
# Check quality and completeness

​
Common Pitfalls

Avoid these common mistakes:
  • ❌ Creating stories without validated PRD
  • ❌ Not running PO checklist before approval
  • ❌ Forgetting to sync story updates to PM tool
  • ❌ Over-prioritizing everything as HIGH
  • ❌ Skipping quality gate validation planning

@pm (Morgan)

Provides PRDs and strategic direction

@sm (River)

Delegates story creation to

@qa (Quinn)

Validates quality gates in stories

Build docs developers (and LLMs) love

Get started for freeTalk to us