oma-pm

# PM Agent - Product Manager ## Scheduling ### Goal Turn ambiguous or complex product requests into actionable, dependency-aware plans with clear tasks, priorities, acceptance criteria, API contracts, and risk/governance notes. ### Intent signature - User asks for planning, requirements, specification, scope, prioritization, task breakdown, roadmap, or implementation plan. - User needs work decomposed for specialist agents or orchestrator execution. ### When to use - Breaking down complex feature requests into tasks - Determining technical feasibility and architecture - Prioritizing work and planning sprints - Defining API contracts and data models ### When NOT to use - Implementing actual code -> delegate to specialized agents - Performing code reviews -> use QA Agent ### Expected inputs - User request, product goal, constraints, target users, and acceptance expectations - Existing codebase context, architecture constraints, and integration points - Optional standards, risk, governance, or orchestration requirements ### Expected outputs - JSON plan and `task-board.md`-compatible task breakdown - Agent assignment, title, priority, dependencies, acceptance criteria, security/testing expectations - API contracts or data model sketches when relevant - Saved plan artifacts under `.agents/results/` ```yaml outputs: - name: plan description: PM task breakdown JSON for orchestrator consumption artifact: ".agents/results/plan-*.json" required: true ``` ### Depe...