菜单
Use when discovery needs evidence about market demand, competitors, pricing pressure, or underserved segments for a new product or expansion idea before feasibility, user research, or requirements are finalized.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a bug, failing test, regression, or unexpected behavior needs a root-cause-first debugging loop before code changes, especially when brownfield seams, recent releases, or historical defect matches make guesswork unsafe.
Use when E2E tests must go beyond shallow happy-path checks — multi-step user journeys, stateful sessions, cross-boundary state consistency, failure-mode edges — or when the suite passes but production still breaks. Platform- and framework-agnostic (web, mobile, desktop; Playwright, XCUITest, Cypress).
Use when discovery has narrowed an idea enough that the team must make a go/no-go, pivot, or scope-down decision based on technical, economic, operational, or timeline viability before requirements, architecture, or major implementation.
The mandatory gateway for all new engineering work. Triage and route new products, apps, features, migrations, tech-debt, or any 'not sure where to start' request to the correct lifecycle path. Use before starting design or implementation. Do not use for ongoing tasks, specific debugging, or PR reviews.
Use when intake has identified the likely lifecycle path but the problem statement, solution direction, or key trade-offs are still too fuzzy for requirements, research, or architecture work to start cleanly
Use when discovery needs evidence about target users, behaviors, and pain points, especially after intake or problem-framing surfaces open questions that must be validated before requirements are written
| name | pc-market-analysis |
| description | Use when discovery needs evidence about market demand, competitors, pricing pressure, or underserved segments for a new product or expansion idea before feasibility, user research, or requirements are finalized. |
| metadata | {"phase":"00-discovery","inputs":[],"outputs":["market-research-report"],"prerequisites":[],"quality_gate":"Market research report reviewed and opportunities ranked by viability","roles":["product-manager"],"methodologies":["all"],"effort":"medium"} |
Understand the market before building the product. Validate that a real opportunity exists.
Market analysis is the first analytical step after intake routes work to the discovery phase.
See context and anti-pattern notes.
I/O contract notes define required inputs and authority.
Identify the target market segment. Be specific -- "project management for freelance designers" not "project management."
Map existing solutions:
For each: note pricing, features, strengths, weaknesses, user reviews.
Where do existing solutions fall short? Look for:
Estimate TAM (Total Addressable Market), SAM (Serviceable Available Market), SOM (Serviceable Obtainable Market). Use bottom-up estimation when possible (number of potential users x willingness to pay).
Rank opportunities by: market size, competition intensity, team capability fit, and time-to-market.
Produce only declared outputs at their documented quality boundary.
