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/plan-phase-protocol.md

View on GitHub
# PLAN Phase Protocol

Execution guide for PLAN Phase (Steps 1-4) in ultrawork workflow. Use `.agents/workflows/ultrawork/resources/phase-gates.md` for canonical criteria and `.agents/workflows/ultrawork.md` for reviewer dispatch; this resource does not start additional reviews.

---

## Step 1: Create Plan

### Tasks
- Define scope, features, architecture
- Resolve material assumptions from context; compare alternatives for unresolved decisions

### Outputs
- Task decomposition (priority tiers: 1 = independent, ascending)
- Agent assignments
- API contracts (if needed)

---

## Step 2: Plan Review (Completeness)

### Review Question
"Is anything missing?"

### Checklist
- [ ] All requirements mapped to plan
- [ ] Dependencies specified
- [ ] Edge cases considered

---

## Step 3: Review Verification (Meta Review)

### Review Question
"Was the review done properly?"

### Checklist
- [ ] The assigned fresh reviewer checks Step 2 findings against plan criteria and evidence
- [ ] Uncovered requirements or unsupported findings are identified
- [ ] The verdict follows the canonical PLAN_GATE and CCR dispatch contract

---

## Step 4: Over-Engineering Check (Simplicity)

### Review Question
"Is this over-engineered?"

### Checklist
- [ ] Asked "Is this needed for MVP?" for each component
- [ ] Speculative features removed
- [ ] No "might need later" code

---

## PLAN_GATE Checklist

Final verification before completing plan:
- [ ] Acceptance criteria have stable IDs and all are covered by relevant `required_checks` argv/cwd declarations
- [ ] Dependencies, replay prompts and retry safety are explicit; any narrowed `inputs` set covers all behavioral dependencies
- [ ] Material assumptions documented
- [ ] Alternatives considered for unresolved major decisions
- [ ] Over-engineering review completed
- [ ] Execution policy applied; existing authorization reused

**Gate failure → Return to Step 1 to revise plan**
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