Intent → Decisions → Commitments → Execution → Outcomes → Learning
Give your coding agent the product judgment, methods, and professional context behind serious product work.
Paste into Claude Code, Codex or Cursor. Your agent will guide setup.
Download ZIP · Installation guide · GitHub
Product Org OS is the open-source edition of the licensed ProductBeacon AI Agentic Workforce. It includes the PBAW harness and product team. The harness selects roles, loads their methods and knowledge, and guides the work. PBAW's additional specialist teams are not included in this free edition.
11 product roles • 125 methods and controls • 117 knowledge files • four governed workflows
What's New in v6.2.0 | Based on Vision to Value: A Blueprint for Product Organizations
Uses the Decision Provenance Standard to keep recommendations, evidence, ownership, and human acceptance distinct.
For product professionals at any level who want to drive outsized impact. Use the governed harness, apply proven product methods, and build institutional memory.
CPO, VP Product, Directors, PMs, PMMs, BizOps, and more. Each role has a bounded remit, declared methods, and professional knowledge.
Create a PRD, roadmap, business case, GTM strategy, pricing model, launch plan, and more through repeatable operating instructions.
Accepted decisions, feedback, documents, and learnings can persist in your repository, where your team can inspect and control them.
Built-in validation for ownership, customer value, collaboration, and scalability. Catch issues before they become problems.
From strategic intent to learning loop. Six phases covering every stage of the product lifecycle with appropriate skills.
Junior PM? Get senior guidance. CPO? Amplify your reach. Works at every level and adapts to your context.
Install once in your repo. Everyone with repo access can use it through their AI coding assistant.
Invoke the harness, not a role handle. It plans substantial work, selects the right product specialists, audits evidence, and preserves accepted learning.
Describe the outcome in ordinary language. The harness automatically selects the product roles, skills, and knowledge packs the request needs at runtime.
/pbaw to challenge our pricing. Would a free tier help the customers we want?
/pbaw to help us choose what matters most.
/pbaw to sharpen who this is for and why they'd choose us.
Use a proportionate written plan for non-trivial work. Scope, assumptions, decisions, recovery boundaries, and verification become visible before execution.
/plan the strategy update around this board feedback.
/plan how we turn this vision into a roadmap.
/plan how we explore the options.
Audit a plan or completed result against evidence. Then preserve accepted decisions, feedback, assumptions, and learning in local context.
/audit this proposal against what customers actually asked for.
/context-harvest the decisions and why.
/audit it against our plan and research.
An illustrative conversation: bring the context, ask for help, and hear the product perspectives together.
Our strategy is to grow with enterprise customers. They keep asking for webhooks, while developers want a better SDK. We can only prioritise one. I want /pbaw to help me think it through.
I'd start with the enterprise goal. Webhooks sound closer to it, but I want to see which customer workflows are blocked before we call this a priority.
I want to compare the customer evidence with the engineering work. If the SDK is blocking adoption, that could change the choice. Let's check both before committing.
I can see an enterprise story for webhooks. I'd test that story with the customers asking for them and keep the claims tied to what we can demonstrate.
Six interconnected phases that transform strategic intent into business outcomes, feeding learning back into strategy.
Establish the strategic context and market understanding that informs all downstream decisions.
Make critical business decisions that determine commercial viability and positioning. Not all initiatives pass this gate.
Convert decisions into commitments: roadmaps, GTM plans, and requirements that the organization will execute.
Execute the plan with cross-functional coordination. Marketing campaigns, sales enablement, and launch readiness.
Realize the promised value and track outcomes. Are customers getting what we promised?
Extract learnings, validate assumptions, and feed insights back into Phase 1. The organization gets smarter.
Each role declares its remit, core skills, mandatory workflows, knowledge packs, and delegation patterns in structured metadata.
Executive product strategy, organization design, portfolio decisions, and board communication.
Product vision, roadmap accountability, pricing strategy, and org structure guidance.
Roadmap governance, team coordination, requirements processes, and delivery planning.
GTM strategy, positioning, competitive intelligence, and launch coordination.
Feature specs, user stories, delivery planning, and backlog management.
Campaigns, collateral, customer research, and sales enablement materials.
Business cases, financial analysis, KPI tracking, and QBR preparation.
Success metrics, ROI analysis, adoption tracking, and customer outcomes.
Competitor analysis, win/loss analysis, market research, and trend monitoring.
Partnership strategy, market expansion, deal structuring, and ecosystem plays.
Process optimization, launch coordination, tooling, and cross-team facilitation.
The verified public inventory includes product roles, governed workflows, methods, and supporting controls. The selected methods below show the breadth of the shipped package.
Skills explain what to do. Knowledge packs supply the professional methods and reference material needed to do it credibly. Product roles declare the packs they load for a task.
Build local institutional memory that remains inspectable and under your control. Recall only what a task needs, then preserve accepted outcomes after review.
Track decisions with options, rationale, and success criteria
Explicit bets with assumptions and checkpoints
Testable assumptions with validation methods
Organizational insights with application guidance
Customer feedback with full metadata and analysis
PRDs, roadmaps, and strategic docs tracked by type
Retain useful interaction summaries locally when the operating workflow calls for them.
The installer creates an empty context/ structure in your workspace. Product Org OS does not ship a remote memory service or require your business material to leave that workspace.
Load only the decisions and evidence relevant to the assignment
Separate an agent recommendation from a human-owned decision
Save accepted decisions, assumptions, feedback, and learning
Every skill and agent operates within these principles from the Vision to Value Operating System.
Product org accountable from strategy through customer outcomes.
Organizational design follows strategic priorities, not the reverse.
The core metric for product leadership effectiveness.
Right people, right inputs, right time - but decisions need single owners.
GTM is integral to product strategy, not an afterthought.
Leaders stay engaged through delivery, not just planning.
What worked at one stage must evolve as the organization grows.
Systematic capture and application of learnings from real results.
Copy this prompt into Claude Code, Codex or Cursor. Your coding agent will help you choose a project, download Product Org OS, preview the changes, and verify setup. You can start before downloading anything.
Help me set up Product Org OS in my project. Start by reading https://yohayetsion.github.io/product-org-os/INSTALL-AND-ONBOARD.md and https://yohayetsion.github.io/product-org-os/agent-guide.md.
Ask which project folder I want to use and check my coding-agent environment and prerequisites. Download Product Org OS v6.2.0 from https://github.com/yohayetsion/product-org-os/archive/refs/tags/v6.2.0.zip and extract it into a separate local source folder.
Follow the guide to preview installation, show me the proposed changes, and get my confirmation before installing with a backup. Preserve existing project instructions, skills and context. Verify the installed files and that I can access the four workflows in this environment, explaining any limitations.
Then ask what product work I want help with and suggest a useful first /pbaw request.
The guide covers Claude Code and Codex directly. Cursor can discover the same installed workflows. Your agent will check the setup in your environment.