Product OS

Product OS gives product teams a clear path from raw user signal to a decision. It installs connected homes for feedback, interviews, requests, pain points, discovery, strategy, specs, competitors, and team input, so agents can synthesize evidence while keeping source links visible and projects in the issue tracker.

What folder structure does Product OS install?

product-os/                       # One shared home for product work├── README.md                     # The product index and starting point├── user-feedback/                # Raw feedback and the patterns found across it│   ├── feedback/                 # Short user comments and observations│   ├── user-interviews/          # Longer customer conversations│   ├── feature-requests/         # Explicit asks│   ├── painpoints/               # Recurring pain points linked to evidence│   └── index.html                # A filterable feedback dashboard├── discovery/                    # Open questions and learning plans├── strategy/                     # Durable claims about how the product wins├── specs/                        # Paste-ready product briefs├── competitors/                  # Capability-focused competitor profiles├── team-input/                   # Roadmap input and dated team recaps├── documentation/                # Product overview and shared terminology└── .agents/commands/             # Feedback, synthesis, spec, and upkeep workflows

• Linked product evidence keeps raw feedback, interviews, requests, and pain points traceable instead of becoming a pile of quotes.
• A feedback dashboard makes signal easy to filter by company, type, sentiment, and tag.
• A path from signal to decision connects discovery, strategy, and specs to their sources.
• Built-in workflows capture feedback, find patterns, draft specs, and review the system.

How do you bring in the product context you already have?

Say "set me up," then start with the material your product team already uses:

• Use a connected source such as Palette's Context Library to bring in company, team, and active-work context.
• Drop product briefs, research exports, feedback folders, interview notes, and existing strategy documents into _inbox/.
• Use a built-in copy-and-paste prompt to bring useful context over from ChatGPT, Claude, Notion, or another tool.
• Answer one short round of questions about the product, users, team, and feedback sources.

Your agent sorts that material into the right product folders, keeps the source links visible, and confirms gaps before replacing the template. Palette Desktop creates a checkpoint before installation, so you can restore the folder if you want to start over.

How does Product OS work with different AI agents?

Product OS keeps feedback, research, discovery, strategy, specs, competitors, and team input in ordinary Markdown files that Claude Code, Codex, Gemini, and other supported agents can read. Shared instructions help each agent work from the same product evidence instead of starting from a summary trapped in one chat.

That means you can switch agents without rebuilding the product brief. An agent can trace a question back to raw feedback, connect it to existing strategy, and help with the next piece of product work while your issue tracker remains the home for projects and tasks.

What can you ask once Product OS is set up?

Once the product context is in place, any supported agent can work from the same evidence, strategy, and past decisions:

• "Help me bring our product brief, research, and feedback into this workspace."
• "What are customers repeatedly saying about onboarding, and what evidence supports it?"
• "Draft a product spec grounded in our feedback, discovery, and strategy."

company-os/├── accounts/       # customers, relationship health├── gtm/            # brand, playbooks, active work├── product/        # strategy, specs, feedback├── engineering/    # architecture, decisions, runbooks├── ops/            # finance, hiring, admin└── people/         # teammate context

gtm-os/├── accounts/       # customers, prospects├── foundations/    # brand, market, strategy├── playbooks/      # sales, content, launches├── work/           # campaigns, projects├── team/           # per-person context└── log/            # decisions, history

project-os/├── overview.html   # generated status dashboard├── context/        # brief, goals, stakeholders├── meetings/       # notes and follow-ups├── decisions/      # numbered decision records├── deliverables/   # milestones, project outputs└── team/           # onboarding, ways of working