Multi-Role Spec and Task Breakdown
mylukin/agent-foreman
Runs a requirement through four research-backed specialist agents, a PM, a UX designer, a tech architect and QA, to produce implementable tasks.
Product manager that decomposes requirements into actionable tasks with priorities and dependencies.
Install Oma Pm
$ npx skills add first-fluke/oh-my-agent --skill oma-pm -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install first-fluke/oh-my-agent oma-pm --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-pm .claude/skills/oma-pm && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "oma-pm" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-pm into .claude/skills/oma-pm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-pm", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-pmType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add first-fluke/oh-my-agent --skill oma-pm -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install first-fluke/oh-my-agent oma-pm --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-pm .agents/skills/oma-pm && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "oma-pm" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-pm into .agents/skills/oma-pm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-pm", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add first-fluke/oh-my-agent --skill oma-pm -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install first-fluke/oh-my-agent oma-pm --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-pm .cursor/skills/oma-pm && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "oma-pm" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-pm into .cursor/skills/oma-pm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-pm", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/first-fluke/oh-my-agent.git --path benchmarks/runs/oma/.agents/skills/oma-pm--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add first-fluke/oh-my-agent --skill oma-pm -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install first-fluke/oh-my-agent oma-pm --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-pm .gemini/skills/oma-pm && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "oma-pm" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-pm into .gemini/skills/oma-pm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-pm", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install first-fluke/oh-my-agent oma-pmInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add first-fluke/oh-my-agent --skill oma-pm -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-pm .github/skills/oma-pm && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "oma-pm" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-pm into .github/skills/oma-pm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-pm", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add first-fluke/oh-my-agent --skill oma-pm -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install first-fluke/oh-my-agent oma-pm --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-pm .opencode/skills/oma-pm && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "oma-pm" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-pm into .opencode/skills/oma-pm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-pm", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
oma-pm- GitHub stars
- 1.3k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 695 words
- Files
- 7
- Skills in repo
- 57
- Repo updated
- First seen
- Licence
- MIT
At a glance
Product manager that decomposes requirements into actionable tasks with priorities and dependencies.
- Works in 3 steps: Clarify the product goal, constraints,… → Identify technical domains and required… → Decide whether ISO/risk/governance…
- ISO 38500-aligned planning recommendations
- SKILL.md covers Scheduling, Structural Flow, Logical Operations and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Oma Pm is an agent skill from first-fluke/oh-my-agent. Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `resources/error-playbook.md`, `resources/examples.md` and `resources/execution-protocol.md`).
It sits in Agent Workflows, covering Task breakdown and Prioritization frameworks. The repository describes itself as: Mechanical verification for AI coding agents — skills pack or full harness (stop-hook gates, artifact checks, independent judges). The licence is MIT.
When your agent uses it
- ISO 38500-aligned planning recommendations
- Tasks that involve Task breakdown
- Tasks that involve Prioritization frameworks
Example prompts
- “/oma-pm”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Clarify the product goal, constraints, and target deliverables.
- Identify technical domains and required contracts.
- Decide whether ISO/risk/governance framing is relevant.
What it can do on your machine
Read from SKILL.md and the folder at commit b364119. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Oma Pm loads about 1.7k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 695 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from first-fluke/oh-my-agent at commit b364119, republished under its MIT licence (© first-fluke). 695 words, ~1,718 tokens.
Download SKILL.mdSave it as
.claude/skills/oma-pm/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- oma-pm
- description
- Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.
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/
Dependencies
resources/execution-protocol.md, examples, task template, and ISO planning guide- Shared API contract references and project context-loading rules
- Downstream specialist skills for implementation
Control-flow features
- Branches by ambiguity, dependency structure, risk level, and whether standards/governance framing is needed
- Produces planning artifacts rather than code
- Optimizes for parallelizable specialist-agent execution
Structural Flow
Entry
- Clarify the product goal, constraints, and target deliverables.
- Identify technical domains and required contracts.
- Decide whether ISO/risk/governance framing is relevant.
Scenes
- PREPARE: Gather requirements, constraints, and context.
- REASON: Decompose work, identify dependencies, risks, and API/data contracts.
- ACT: Produce JSON plan and task-board-compatible output.
- VERIFY: Check task atomicity, acceptance criteria, security/testing coverage, and dependency shape.
- FINALIZE: Save plan artifacts and summarize execution path.
Transitions
- If requirements are ambiguous, clarify before decomposition.
- If tasks are tightly coupled, refine contracts or sequencing.
- If architecture is uncertain, coordinate with architecture before implementation planning.
- If the user needs automated execution, hand off to orchestrator after plan approval.
Failure and recovery
- If scope is too broad, split into phases.
- If acceptance criteria are vague, rewrite them into testable outcomes.
- If dependencies block parallel execution, surface sequencing explicitly.
Exit
- Success: plan is actionable, testable, prioritized, and compatible with orchestrator execution.
- Partial success: unresolved assumptions or dependencies are explicit.
Logical Operations
Actions
| 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 |
Show full SKILL.md (277 more words)Show less
Tools and instruments
- Task template, examples, ISO planning guide, shared API contracts
- Local filesystem for result artifacts
Canonical workflow path
1. Define API/data contracts.
2. Decompose tasks with agent, title, priority, dependencies, and acceptance criteria.
3. Save `.agents/results/plan-{sessionId}.json` and `.agents/results/current-plan.md`.Resource scope
| Scope | Resource target |
|---|---|
MEMORY | Requirements, assumptions, dependencies |
LOCAL_FS | .agents/results/plan-{sessionId}.json, .agents/results/current-plan.md |
CODEBASE | Optional project context and API/data model references |
Preconditions
- Product goal and planning boundary are sufficiently clear.
- Required implementation domains can be identified.
Effects and side effects
- Creates plan artifacts and task boards.
- Influences downstream agent assignments and execution order.
- Does not directly implement code.
Guardrails
- API-first design: define contracts before implementation tasks
- Every task has: agent, title, acceptance criteria, priority, dependencies
- Minimize dependencies for maximum parallel execution
- Security and testing are part of every task (not separate phases)
- Tasks should be completable by a single agent
- Output JSON plan + task-board.md for orchestrator compatibility
- When relevant, structure plans using ISO 21500 concepts, risk prioritization using ISO 31000 thinking, and responsibility/governance suggestions inspired by ISO 38500
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
References
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.
Vendor-specific execution protocols are injected automatically by oma agent:spawn.
Source files live under ../_shared/runtime/execution-protocols/{vendor}.md.
- 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
© first-fluke, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files in benchmarks/runs/oma/.agents/skills/oma-pm of first-fluke/oh-my-agent.
- SKILL.md
- resources/error-playbook.md
- resources/examples.md
- resources/execution-protocol.md
- resources/iso-planning.md
- resources/plan-phase-protocol.md
- resources/task-template.json
Open the folder on GitHubat commit b364119
Compare with similar skills
Oma Pm next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Oma Pm this skillfirst-fluke/oh-my-agent | 1.3k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Multi-Role Spec and Task Breakdownmylukin/agent-foreman | 250 | — | ~5.1k | Automated safety check: Notes | None | |
| Scope KnifeMAGA2010/hackathon-run | 390 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Wayfinder Planning Mapsrengwu/wayfinder-maps | 138 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Roadmap Generatoralirezarezvani/claude-cto-team | 117 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Autospec Tasksariel-frischer/autospec | 144 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Scope Knife
MAGA2010/hackathon-run
Forces a KEEP, CUT, or DEFER decision on every feature when scope is too large, no MVP consensus exists, or time is running out.
Wayfinder Planning Maps
rengwu/wayfinder-maps
Plans work too big for one agent session as a shared map of investigation tickets, resolved one at a time until the route to the destination is clear.
Roadmap Generator
alirezarezvani/claude-cto-team
Generate phased implementation roadmaps with Epic/Story/Task breakdown, effort estimates, and validation checkpoints.
Autospec Tasks
ariel-frischer/autospec
Generate YAML task breakdown from implementation plan. An agent skill from ariel-frischer/autospec.
Plan
softspark/ai-toolkit
Breaks features/goals into phased plans with task lists, agent assignments, dependencies.
More from first-fluke/oh-my-agent
All 57 skills in this repoOMA Multi-Agent Orchestration
first-fluke/oh-my-agent
Decomposes a complex feature into tasks, dispatches parallel specialist agents with durable state, and supervises verification, QA review and retries.
OMA Multi-Agent Orchestrator
first-fluke/oh-my-agent
Splits a complex feature into prioritized tasks, spawns specialist CLI subagents in parallel, tracks them through shared memory and verifies each result.
Architecture Decisions and ADRs
first-fluke/oh-my-agent
Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.
OMA Backend Agent
first-fluke/oh-my-agent
Backend specialist for APIs, database work, authentication and migrations that follows clean architecture with router, service and repository layers.
oma Bootstrap
first-fluke/oh-my-agent
Installs or checks the oma CLI and its runtimes (bun, uv, serena) in a fresh workspace so that oma-* skills can run their commands.
Design-First Brainstorm
first-fluke/oh-my-agent
Explores intent, constraints and alternative approaches before any planning, working through questions one at a time and saving an approved design for later steps.
Related
Questions about Oma Pm
What does Oma Pm do?
Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Oma Pm is an agent skill from first-fluke/oh-my-agent. Product manager that decomposes requirements into actionable tasks with priorities and dependencies.
When should I use Oma Pm?
Oma Pm fits situations like: ISO 38500-aligned planning recommendations; tasks that involve Task breakdown; tasks that involve Prioritization frameworks.
How do I install Oma Pm in Claude Code?
Run `npx skills add first-fluke/oh-my-agent --skill oma-pm -a claude-code`. Or copy the skill folder (benchmarks/runs/oma/.agents/skills/oma-pm in first-fluke/oh-my-agent) into .claude/skills/oma-pm in your project. Claude Code loads it when a task matches its description.
How do I install Oma Pm in Codex?
Run `npx skills add first-fluke/oh-my-agent --skill oma-pm -a codex`. Or copy the skill folder (benchmarks/runs/oma/.agents/skills/oma-pm in first-fluke/oh-my-agent) into .agents/skills/oma-pm in your project. Codex loads it when a task matches its description.
Can I use Oma Pm in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add first-fluke/oh-my-agent --skill oma-pm -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oma-pm, .gemini/skills/oma-pm, .github/skills/oma-pm and .opencode/skills/oma-pm in your project.
What does Oma Pm need to run?
SKILL.md names no scripts, command-line tools or credentials: Oma Pm is instructions for the agent only.
Does Oma Pm access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Oma Pm safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Oma Pm use?
Oma Pm is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Oma Pm use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Oma Pm?
Skills that share tags, products or a category with Oma Pm: Multi-Role Spec and Task Breakdown (mylukin/agent-foreman, 250 stars), Scope Knife (MAGA2010/hackathon-run, 390 stars), Wayfinder Planning Maps (rengwu/wayfinder-maps, 138 stars) and Roadmap Generator (alirezarezvani/claude-cto-team, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Oma Pm?
first-fluke (a GitHub organization) maintains it in first-fluke/oh-my-agent, which has 1,338 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on October 9, 2026.
Source: first-fluke/oh-my-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.