phuryn/pm-skills

brainstorm-ideas-new

Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/phuryn/pm-skills --skill brainstorm-ideas-new

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Brainstorm Product Ideas (New Product)

Multi-perspective ideation for initial product discovery of a new product. Generates specific feature ideas from PM, Designer, and Engineer viewpoints.

Context

You are supporting initial product discovery for a new product: $ARGUMENTS.

If the user provides files (market research, competitive analysis), read them first. Use web search to understand the market if needed.

Domain Context

Initial Discovery vs Continuous Discovery: Initial Discovery focuses on vision, business model, and market validation — you're testing whether the product should exist. Continuous Discovery runs in parallel with delivery — you're constantly learning and iterating on a live product. This skill is for initial discovery.

Instructions

The user will describe their target segment, opportunity, and desired outcomes. Work through these steps:

  1. Understand the opportunity: Confirm the product concept, target market segment, and what the users want to achieve.
  1. Ideate from three perspectives — generate 5 specific feature ideas each from:
  • Product Manager: Focus on market fit, value creation, and competitive advantage
  • Product Designer: Focus on user experience, onboarding, and engagement
  • Software Engineer: Focus on technical innovation, API integrations, and platform capabilities
  1. Prioritize the top 5 ideas across all perspectives. For a new product, weight heavily toward:
  • Core value delivery (does it solve the primary problem?)
  • Speed to validate (can we test this quickly?)
  • Differentiation potential
  1. For each prioritized idea, provide reasoning and key assumptions to test.

Think step by step. Save substantial output as a markdown document.


Further Reading

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
phuryn
コミュニティ

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

1時間の導入数
2
GitHub Stars
2.8万
更新日
10月29日
phuryn
コミュニティ

create-prd

Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

1時間の導入数
4
GitHub Stars
2.8万
更新日
10月29日
phuryn
コミュニティ

outcome-roadmap

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

1時間の導入数
2
GitHub Stars
2.8万
更新日
10月29日
phuryn
コミュニティ

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

1時間の導入数
2
GitHub Stars
2.8万
更新日
10月29日