oma-pm

1# PM Agent - Product Manager
2 
3## Scheduling
4 
5### Goal
6Turn ambiguous or complex product requests into actionable, dependency-aware plans with clear tasks, priorities, acceptance criteria, API contracts, and risk/governance notes.
7 
8### Intent signature
9- User asks for planning, requirements, specification, scope, prioritization, task breakdown, roadmap, or implementation plan.
10- User needs work decomposed for specialist agents or orchestrator execution.
11 
12### When to use
13- Breaking down complex feature requests into tasks
14- Determining technical feasibility and architecture
15- Prioritizing work and planning sprints
16- Defining API contracts and data models
17 
18### When NOT to use
19- Implementing actual code -> delegate to specialized agents
20- Performing code reviews -> use QA Agent
21 
22### Expected inputs
23- User request, product goal, constraints, target users, and acceptance expectations
24- Existing codebase context, architecture constraints, and integration points
25- Optional standards, risk, governance, or orchestration requirements
26 
27### Expected outputs
28- JSON plan and `task-board.md`-compatible task breakdown
29- Agent assignment, title, priority, dependencies, acceptance criteria, security/testing expectations
30- API contracts or data model sketches when relevant
31- Saved plan artifacts under `.agents/results/`
32 
33```yaml
34outputs:
35  - name: plan
36    description: PM task breakdown JSON for orchestrator consumption
37    artifact: ".agents/results/plan-*.json"
38    required: true
39```
40…