Turn product requirements into scoped tasks with dependencies and acceptance criteria. Use for implementation planning and prioritization.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/oma-pm/SKILL.mdTurn ambiguous or complex product requests into actionable, dependency-aware plans with clear tasks, priorities, acceptance criteria, API contracts, and risk/governance notes.
task-board.md-compatible task breakdown.agents/results/outputs:
- name: plan
description: PM task breakdown JSON for orchestrator consumption
artifact: ".agents/results/plan-*.json"
required: trueresources/execution-protocol.md, examples, task template, and ISO planning guide| Action | SSL primitive | Evidence |
|---|---|---|
| Read requirements/context | READ | User request and project context |
| Select planning structure | SELECT | Task template and workflow needs |
| Infer tasks and dependencies | INFER | Domain decomposition |
| Validate acceptance criteria | VALIDATE | Checklist and task schema |
| Write plan artifacts | WRITE | JSON plan and task-board markdown |
| Notify plan summary | NOTIFY | Final planning report |
1. Define API/data contracts.
2. Decompose tasks with agent, title, priority, dependencies, and acceptance criteria.
3. Save `.agents/results/plan-{sessionId}.json` using the injected session ID. Write the run-scoped report from the shared memory/result contract.| Scope | Resource target |
|---|---|
MEMORY | Requirements, assumptions, dependencies |
LOCAL_FS | .agents/results/plan-{sessionId}.json, injected claim path and task/run-scoped report |
CODEBASE | Optional project context and API/data model references |
{id, description} acceptance criteria, covering required_checks with exact argv/cwd, a replayable task prompt, priority tier (1 = independent, lower runs first), dependencies, and scopeLocal code tools: ../_shared/core/code-intelligence.md (code search/navigation)
Runtime identity and run-scoped reports: ../_shared/runtime/memory-protocol.md, ../_shared/runtime/result-contract.md
Execution steps (follow for the selected task): 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
Ultrawork PLAN phase protocol: resources/plan-phase-protocol.md (used when this skill runs inside the ultrawork workflow)
Task board spec (orchestrator-consumed format): ../oma-orchestration/resources/memory-schema.md
Human-readable tracker: when running inside the /plan workflow, also generate docs/plans/work/{NNN}-{name}.md per .agents/workflows/plan.md
API contract template (SSOT): ../_shared/core/api-contracts/template.md; write generated contracts to .agents/results/api-contracts/ (run artifact) or docs/plans/contracts/ (durable spec)
Context loading: ../_shared/core/context-loading.md
Planning depth: ../_shared/core/difficulty-guide.md (unresolved scope or dependencies)
Clarification: ../_shared/core/clarification-protocol.md
Context budget: ../_shared/core/context-budget.md
Lessons learned: ../_shared/core/lessons-learned.md (matching prior failure or requested retrospective)
first-fluke/oh-my-agent
8a03eb1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.