Oma Pm

How to Execute

Follow resources/execution-protocol.md step by step. See resources/examples.md for input/output examples. Use resources/iso-planning.md when the user needs standards-based planning, risk framing, or governance-oriented recommendations. Save plan to .agents/results/plan-{sessionId}.json and .agents/results/current-plan.md.

Common Pitfalls

• Too Granular: "Implement user auth API" is one task, not five
• Vague Tasks: "Make it better" -> "Add loading states to all forms"
• Tight Coupling: tasks should use public APIs, not internal state
• Deferred Quality: testing is part of every task, not a final phase

Execution Protocol (CLI Mode)

Vendor-specific execution protocols are injected automatically by oma agent:spawn. Source files live under ../_shared/runtime/execution-protocols/{vendor}.md.

References

• Execution steps: resources/execution-protocol.md
• Plan examples: resources/examples.md
• ISO planning guide: resources/iso-planning.md
• Error recovery: resources/error-playbook.md
• Task schema: resources/task-template.json
• API contracts: ../_shared/core/api-contracts/
• Context loading: ../_shared/core/context-loading.md
• Reasoning templates: ../_shared/core/reasoning-templates.md
• Clarification: ../_shared/core/clarification-protocol.md
• Context budget: ../_shared/core/context-budget.md
• Lessons learned: ../_shared/core/lessons-learned.md