oma-pm

Provide the product goal, constraints, and acceptance expectations. The Skill decomposes the request into single-agent tasks, each with an assigned agent, title, priority tier, dependencies, and testable acceptance criteria, saved as a JSON plan for orchestrator execution.

It produces a JSON plan following the task template schema, including tasks, API contracts, data models, and non-functional requirements. Artifacts are saved to .agents/results/plan-{sessionId}.json and a task-board-compatible markdown summary.

No, it only plans and decomposes work. Implementation is delegated to specialist agents such as backend, frontend, mobile, and QA, which consume the generated plan and API contracts.

Circular dependencies are broken by defining a shared API contract or interface first as a priority-0 task with no dependencies. The conflicting tasks then depend on the contract rather than on each other.

Apply these standards for enterprise or regulated projects with material risk, many stakeholders, or unclear decision rights. Avoid them for small features or bugs where formal framing adds ceremony without improving delivery clarity.

The Skill lists explicit assumptions, clarifies uncertainty triggers such as business logic or security concerns, and escalates questions before decomposition. It never creates tasks while requirements remain ambiguous.