Portfolio PM Audit

PM Agent and Portfolio Framework Review

Prepared 2026-06-06 11:50 EDT for Jeremy review.

Executive summary

The PM cycle that ran earlier was too narrow: it refreshed the active queue and selected a development target, but it did not rigorously audit the full GitHub portfolio against Jeremy's morning requirements. I created a new required portfolio-pm-audit skill and wired PM cycles to use it before selecting development work.

Recommendation: pause broad development until a full PM portfolio audit completes and updates Hub/issue gaps. Development can resume on a single target only after the audit produces an explicit handoff.

What improved

Created skills/portfolio-pm-audit/SKILL.md.
Updated HEARTBEAT.md and AGENTS.md so PM cycles must use the audit checklist.
Added Human ToDo delegation gate requirements.
Clarified that GitHub issues are durable PM memory and PRs are development artifacts.

Still missing

Agent Overview page requested for the Hub is not published yet.
Portfolio audit should be run as a first-class PM report, not just a queue refresh.
No separate PM/Development agents are configured in OpenClaw; current sessions are prompt-scoped rather than agent-isolated.
Several local worktrees are dirty or behind and need classification before development.

Morning requirements checklist

Done: Hub Human ToDos now use linked repo + issue/PR format and explicit @jwildfire wording.
Done: Linked Human ToDo artifacts received explicit @jwildfire clarification comments.
Done: Project issue type exists in Hub labels; active P004/P007 Project issues exist.
Partial: Requirements and Tasks exist for P004/P007, but the audit needs to verify parent/sub-issue linkage and stale tracker issues across repos.
Partial: Hub roadmap/homepage improved, but Agent Overview page has only a task issue, not a published page.
Partial: Orchestrator/delegation rules are in local instructions, but dedicated PM/Dev agent configuration is not yet real.
Done: Telegram formatting/truncation skills hardened.

Current Project / Requirement / Task snapshot

Hub repo open portfolio issues

#16 Project: P004 SafetyGraphics renderer modernization
#17 Project: P007 Refactor development framework for increased autonomy
#4 Requirement: P004 autonomous SafetyGraphics renderer modernization standard
#14 Requirement: P007 PM visibility and human ToDo tracking
#18 Requirement: P007 GitHub-native memory and work artifacts
#21 Task: create Agent Overview page for current autonomous agents

safety-agent open PM/development issues

#5 Task: promote P004 renderer migration standard
#6 Task: reconcile Safety Histogram implementation and evidence PRs
#7 Task: define P004 testing agent GitHub App implementation path
#3 legacy/full renderer migration tracker lacks current type/status labels and should be reconciled or closed/superseded.

Dirty worktree and branch drift risks

Development cycles should use fresh worktrees or explicitly selected clean branches until these are classified.

autonomous-issue6-safety-histogram — ## issue6-reconcile-pr1
gsm.safety — ## codex/ae-explorer-report-scaffold...origin/codex/ae-explorer-report-scaffold [behind 10]
obot-claw.github.io — ## main...origin/main [behind 46]
safety-agent — ## p004-requirements-testing-framework
safety-histogram — ## test-driver/safety-histogram-trial...origin/test-driver/safety-histogram-trial [behind 4]

Framework improvements recommended

PM portfolio report every cycle: PM should produce an HTML/Markdown audit artifact before development starts.
Deterministic audit helper: add a script that queries GitHub issues/PRs/labels and outputs Project/Requirement/Task gaps.
Hub sync gate: PM cycle should fail closed if Hub homepage/roadmap/ToDos are stale relative to GitHub issues.
Agent capability page: publish the missing Hub Agent Overview page with Main/PM/Development/Testing agents, responsibilities, and escalation rules.
Dedicated agent configuration: create actual PM and Development agent configs/sessions or documented launch prompts, not just conceptual roles.
Research loop: PM audit should inspect current GitHub labels, issue templates, sub-issue support, project pages, and recent comments before making recommendations.

Proposed next PM cycle contract

Run portfolio-pm-audit.
Inventory live repos, issues, PRs, labels, Hub pages, Human ToDos, and dirty worktrees.
Classify gaps as PM-fix-now, Development-handoff, Testing-handoff, New-agent-needed, or Jeremy-decision.
Make safe issue/Hub updates.
Only then choose a single development target with exact handoff instructions.

Immediate next actions

Run full PM portfolio audit using the new skill and publish its findings.
Create/publish the missing Hub Agent Overview page from issue #21.
Decide whether to configure real isolated PM/Development agents or maintain prompt-scoped cycles for now.
After audit, restart development only if the selected target remains highest priority.