Product Research

---
name: product-research
description: Run the product-research phase for one workspace — mine the product's own artifacts into the three copy-shaped files a writer uses, on a channel isolated from market research. TRIGGER when the owner cannot supply the product facts and a workspace needs them before strategy or writing. DO NOT TRIGGER to research the market and its buyers (market-research) or to interview the owner for stated facts (setup).
---

# Product Research

One Process: produce the product's copy-shaped facts by running research-product on the product's own artifacts. This owns the phase; research-product owns the mining and the file shapes, never restated here.

## 1. Mine the product on an isolated channel

Run research-product against the product's own artifacts only. It organizes what it finds into the three copy-shaped files — the problems the product solves, its features with their user-visible outcomes, and the step-by-step processes it runs, boundaries woven per feature.

## 2. Keep the channel isolated

This phase runs isolated. Its output NEVER feeds market research — no product capability reaches buyer discovery, problem mining, or their reviewers, where a leaked capability biases every market agent toward solution-shaped problems. The product meets the market landscape only later, at strategy.

## Owner boundary

The phase stops at the product-facts boundary. It produces the three files and nothing downstream. The owner may review them before strategy runs.

## Verification

`research/product/problems.md`, `research/product/features.md`, and `research/product/processes.md` exist, each traced to the product's own artifacts, with no market or competitor record mixed in.