Skip to content

gracefullight/pkgs / .agents/skills/oma-pm

oma-pm

Verified

Turn product requirements into scoped tasks with dependencies and acceptance criteria. Use for implementation planning and prioritization.

resources/iso-planning.md

View on GitHub
# PM Agent - ISO 21500 / 31000 / 38500 Guide

Use this file when the user wants standards-based planning, enterprise delivery structure, risk-aware prioritization, or governance-oriented recommendations.

## Positioning

- **ISO 21500**: project management structure and planning lens
- **ISO 31000**: risk management lens
- **ISO 38500**: governance, accountability, and decision-rights lens

Do not turn these into ceremony for simple tasks. Use them when they improve clarity, accountability, or delivery confidence.

## 1. ISO 21500 for PM Work

Use ISO 21500 thinking to strengthen:

- scope definition
- stakeholder identification
- dependency mapping
- schedule and sequencing
- roles and responsibilities
- deliverable clarity

Practical PM outputs:

- explicit scope and exclusions
- task decomposition with dependencies
- owner assignment
- milestone or phase structure
- acceptance criteria and deliverables

## 2. ISO 31000 for Risk-Aware Planning

Use ISO 31000 thinking to improve:

- risk identification
- impact/likelihood discussion
- prioritization
- treatment / mitigation planning
- residual risk visibility

Practical PM outputs:

- top risks list
- mitigation tasks
- contingency tasks
- release blockers vs monitored risks
- decision points for escalation

## 3. ISO 38500 for Governance

Use ISO 38500 lightly for:

- decision ownership
- approval boundaries
- accountability
- oversight expectations
- alignment between business intent and technical execution

Practical PM outputs:

- approver or decision owner
- who must be informed
- what needs explicit sign-off
- where governance review is needed

## 4. When to Apply

Apply these standards when:

- the project is enterprise or regulated
- many teams or stakeholders are involved
- risk is material
- decision rights are unclear
- the user asks for formal planning or governance

Avoid overusing them when:

- the task is a small feature or bug
- standards language would slow delivery without adding control

## 5. Output Pattern

When relevant, add a short section like:

```md
## Standards-Aligned Planning Notes

### ISO 21500
- Scope:
- Stakeholders:
- Major dependencies:

### ISO 31000
- Top risks:
- Mitigations:
- Residual risks:

### ISO 38500
- Decision owner:
- Required approvals:
- Governance checkpoints:
```

## 6. Guardrails

- Keep recommendations actionable, not ceremonial
- Do not claim formal compliance
- Tie each standards suggestion to planning, risk reduction, or decision clarity
- Keep technical execution delegated to specialist agents
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall