OpenClaw Codex PM Skills
5-skill PM toolkit for OpenClaw + Codex agents: discovery foundations, PRD drafting, prioritization, strategy canvas, and structured web-QA reporting with machine-readable JSON output for CI integration.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
openclaw-codex-pm-skills
A community-driven adaptation layer for applying PM skill frameworks (inspired by phuryn/pm-skills) to OpenClaw + Codex-style workflows.
This project is designed for teams who want practical, reusable product-management skills that are:
- portable across environments,
- easy to audit,
- safe for collaborative use,
- and realistic to maintain in open source.
If you need a compact PM reminder to keep repo 4 validator proof and repo 5 scenario-report proof in the same validate-before-push streak, open docs/OPENCLAW_PM_REPO45_SCENARIO_REPORT_VALIDATE_STREAK_NOTE.md.
If you need a compact PM note for the new stakeholder_types scenario-file alias while repo 4 and repo 5 stay in the same phase-one validation loop, open docs/OPENCLAW_PM_REPO45_STAKEHOLDER_TYPES_ALIAS_NOTE.md.
If you need the matching PM note for wrapper-shaped scenario files that still carry stakeholder_types, open docs/OPENCLAW_PM_REPO45_STAKEHOLDER_TYPES_WRAPPER_NOTE.md.
If you need a compact PM reminder to keep repo 4 and repo 5 in the same validate-before-push streak while preserving one-line report brevity, open docs/OPENCLAW_PM_REPO45_VALIDATE_STREAK_SHORT_REPORT_NOTE.md.
If you need a compact PM note for replaying one governance-sandbox scenario through proposal_input_markdown_path while keeping the same markdown/html/json report proof lane, open docs/OPENCLAW_PM_REPO45_PROPOSAL_INPUT_MARKDOWN_PATH_NOTE.md.
Fast validation
Suggested PM loop: validate the repo first, update the prompt or evidence surface in a small slice, then rerun the validator before proposing handoff wording.
Use the repository smoke check before proposing README, example, or validator changes:
python3 -m unittest tests/test_validate_web_qa_report.py tests/test_validate_web_qa_report_cli.py
This keeps documentation tweaks and validation-rule changes tied to the same replay-readiness contract.
For broader validator or fixture rewrites, run python3 -m unittest discover -s tests before opening the PR so the full replay-readiness surface stays green.
If the workstream touches governance-sandbox scenario files or markdown/html report proof, use docs/GOVERNANCE_SANDBOX_SCENARIO_REPORT_PROOF_LOOP.md before merging so scenario-input evidence and report-output evidence stay coupled.
If you need the shortest scenario-file -> JSON/Markdown/HTML replay path before the fuller proof loop, open docs/GOVERNANCE_SANDBOX_SCENARIO_REPORT_QUICKSTART.md first.
If you need a compact reminder to keep one scenario import tied to one JSON/Markdown/HTML report bundle, open docs/GOVERNANCE_SANDBOX_SCENARIO_REPORT_STACK_NOTE.md.
If you need a compact PM note for keeping scenario-file support and markdown/html report generation at the front of the queue, open docs/GOVERNANCE_SANDBOX_SCENARIO_REPORT_PRIORITY_LANE.md.
If you need a compact PM reminder that the same repo-5 phase-one pair still starts with JSON/YAML scenario-file input and one regenerated JSON/Markdown/HTML report bundle, open docs/GOVERNANCE_SANDBOX_SCENARIO_JSON_YAML_PRIORITY_NOTE.md.
If you need a compact PM note that repo-5 phase one should stay scenario-file -> markdown/html/json report bundle before trait presets or web demo polish, open docs/GOVERNANCE_SANDBOX_DELIVERY_LADDER_NOTE.md.
If you need a compact PM note for keeping the phase-one lane explicit as scenario file -> report bundle -> presets/demo, open docs/OPENCLAW_PM_GOVERNANCE_PHASE_ONE_ALIAS_NOTE.md.
If you need a compact PM replay note for the current repo-5 phase-one lane, open docs/OPENCLAW_PM_GOVERNANCE_PHASE_ONE_REPLAY_LANE.md.
If you need a compact PM note for carrying repo-5 report bundle naming through report_output_key while repo 4 and repo 5 stay in the same validation-first pass, open docs/OPENCLAW_PM_REPO45_REPORT_OUTPUT_KEY_ALIAS_NOTE.md.
If you need a compact PM note for carrying repo-5 report bundle naming through report_output_handle while repo 4 and repo 5 stay in the same validation-first pass, open docs/OPENCLAW_PM_REPO45_REPORT_OUTPUT_HANDLE_ALIAS_NOTE.md.
If you need a one-screen PM reminder for the current governance-sandbox build order, open docs/GOVERNANCE_SANDBOX_SCENARIO_REPORT_PHASE_ONE_CHECK.md.
If you need a compact maintainer loop for the current phase-one priority, open docs/GOVERNANCE_SANDBOX_SCENARIO_REPORT_PHASE_ONE_LOOP.md.
If you need a compact PM status cue that keeps repo-1 handoff wording aligned with the repo-5 phase-one order, open docs/GOVERNANCE_SANDBOX_PHASE_ONE_STATUS_LINE_NOTE.md.
If you need a compact PM reminder to validate the smallest repo-level slice before push, open docs/OPENCLAW_PM_VALIDATE_THEN_PUSH_NOTE.md.
If you need a compact PM note for keeping one small validated improvement visible across all five active repos while governance-sandbox still stays scenario-file/report-first, open docs/GOVERNANCE_SANDBOX_FIVE_REPO_ACTIVE_SLICE_NOTE.md.
If you need a compact PM reminder to keep every repo active in the same five-repo pass while preserving the one-line report gate, open docs/OPENCLAW_PM_FIVE_REPO_ACTIVE_CHECK_NOTE.md.
If you need a compact PM rule for keeping the repo order visible while each line still names the validation state and commit/push hold reason, open docs/OPENCLAW_PM_FIVE_REPO_STATUS_LINE_ORDER_GATE.md.
If you need a compact PM note for keeping governance-sandbox scenario-file/report-first progress paired with the same active five-repo slice, open docs/GOVERNANCE_SANDBOX_SCENARIO_REPORT_PROGRESS_NOTE.md.
If you need an even shorter PM note for keeping each pass to one validated scenario/report-first slice, open docs/GOVERNANCE_SANDBOX_SCENARIO_REPORT_SMALL_SLICE_NOTE.md.
If you need the matching one-line status cue for scenario-file import plus report refresh, open docs/GOVERNANCE_SANDBOX_SCENARIO_REPORT_SHORT_STATUS_NOTE.md.
If you need a compact PM cue that repo-5 phase one may also surface the same report basename through report_bundle_alias, open docs/OPENCLAW_PM_REPO45_SCENARIO_REPORT_ALIAS_LANE.md.
If you need a compact PM bridge that keeps repo-1 wording tied to the same repo-5 phase-one slice, open docs/GOVERNANCE_SANDBOX_SCENARIO_REPORT_PHASE_ONE_STATUS_BRIDGE.md.
If you need a compact phase-one status reminder that keeps one scenario-file replay tied to one validated JSON/Markdown/HTML report bundle, open docs/GOVERNANCE_SANDBOX_SCENARIO_FILE_REPORT_PHASE_ONE_STATUS_NOTE.md.
If you need a compact PM reminder to treat report.output_label as a stable governance-sandbox bundle-naming alias before widening web-demo scope, open docs/GOVERNANCE_SANDBOX_REPORT_OUTPUT_LABEL_ALIAS_NOTE.md.
If you need a compact PM reminder to keep the repo-4/repo-5 phase-one handoff aligned with the same report.output_slug alias, open docs/OPENCLAW_PM_REPO45_REPORT_OUTPUT_SLUG_ALIAS_NOTE.md.
If you need a compact PM reminder that repo-4/repo-5 phase-one handoff may also carry the shared basename as report_output_ref, open docs/OPENCLAW_PM_REPO45_REPORT_OUTPUT_REF_ALIAS_NOTE.md.
If you need a compact PM reminder that the same repo-4/repo-5 phase-one handoff may also name the shared bundle via report_output_code, open docs/OPENCLAW_PM_REPO45_REPORT_OUTPUT_CODE_ALIAS_NOTE.md.
If you need a compact PM reminder that the same repo-4/repo-5 phase-one handoff may also name the shared bundle via report_output_key or nested report.outputs.output_key, open docs/OPENCLAW_PM_REPO45_REPORT_OUTPUT_KEY_ALIAS_NOTE.md.
If you need a compact PM reminder that the same repo-4/repo-5 phase-one handoff may also name the shared bundle via report_output_handle or nested report.outputs.output_handle, open docs/OPENCLAW_PM_REPO45_REPORT_OUTPUT_HANDLE_ALIAS_NOTE.md.
If you need a compact PM reminder that the same repo-4/repo-5 phase-one handoff may also name the shared bundle via report_output_tag, open docs/OPENCLAW_PM_REPO45_REPORT_OUTPUT_TAG_ALIAS_NOTE.md.
If you need a compact PM reminde
// HOW IT'S BUILT
TECHNOLOGY STACK
This skill is built with python, markdown..
KEY FILES