ProcessComposable · Yields to: Voice, Density, Craft

Planner

Project plans with PRDs, design docs, architecture flows, and task breakdowns.

When to Use

• User says "create a PRD", "design the architecture", "plan this project"
• User invokes /plan
• Breaking down complex tasks

Triggers

/plan [optional: prd|design|architecture|tasks]
"create a PRD", "design the architecture", "plan this project"

Examples

Example 1

Generate a PRD

Create a product requirements document for a new feature.

/plan prd Add real-time collaboration to our code editor

The agent generates:
- Problem statement and user stories
- Functional requirements (CRDT-based sync, presence
  indicators, conflict resolution)
- Non-functional requirements (latency < 100ms, 100
  concurrent editors)
- Success metrics, risks, open questions
- Timeline with milestones

Example 2

Architecture design doc

Design the system architecture for a new service.

/plan architecture Design a distributed cache layer

The agent produces:
- Component diagram (cache nodes, client SDK, invalidation)
- Data flow (write-through, read-through patterns)
- API contracts (get, set, delete, invalidate)
- Trade-offs: consistency vs availability
- Alternatives considered (Redis, Memcached, custom)
- Decision rationale with ADR format

Example 3

Research then plan

Research best practices before creating the plan.

/researcher + /plan

Researcher surveys current best practices for real-time
collaboration (CRDTs, OT, hybrid approaches). Planner
uses findings to create an informed architecture doc
with proper trade-off analysis.