本文へ移動
cccskills
無料GitHub で公開

pre-prd-research

Pre-PRD Research methodology combining Business Analysis, Creative Problem-Solving, Brainstorming, and Innovation Strategy. Use before writing any PRD for problem validation, market research, competitive analysis, stakeholder interviews, ideation, root cause analysis.

インストール方法を見る

含まれるファイル(7)

  • SKILL.md6.1 KB
  • references/brainstorming-techniques.md14.6 KB
  • references/competitive-analysis.md12.1 KB
  • references/interview-guide.md8.4 KB
  • references/strategic-frameworks.md23.6 KB
  • references/traceability-guide.md17.8 KB
  • SKILL.extended.md29.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Applies before any PRD exists: problem validation, market/competitive research, stakeholder interviews, ideation, root cause analysis. Does not apply once the PRD is being written.

Core belief: fall in love with the problem, not the solution.

Four Pillars

PillarFocusKey Question
Business AnalysisEvidence & RequirementsWhat do we know for certain?
Creative Problem-SolvingRoot Causes & SystemsWhat's really going on?
BrainstormingPossibilities & IdeasWhat could we do?
Innovation StrategyValue & PositioningWhy would anyone care?

Flow

ACTIVITY A: UNDERSTAND (problem analysis, stakeholder map, market research) -> ACTIVITY B: EXPLORE (ideation, root cause hunt) -> ACTIVITY C: DEFINE (strategic synthesis, validation)

Traceability

ID format: [Project]-[Activity]-[Type]-[Number]

  • PROJ-A-INT-001 = Interview finding #1
  • PROJ-B-IDEA-003 = Idea #3
  • PROJ-C-OPP-002 = Opportunity #2

Traceability matrix columns:

Research IDFindingSourcePRD RequirementUser Story
PROJ-A-INT-001Users frustrated by XInterviewREQ-001US-001

Details: references/traceability-guide.md

Entry & Exit Criteria

Entry: initial idea/request/problem exists; stakeholders available; time allocated (minimum 2-3 sessions).

Exit (Gate to PRD):

  • Problem validated with multiple stakeholders
  • Root causes identified and verified
  • Market/competitive landscape understood
  • Solution space explored
  • Strategic positioning defined
  • Assumptions explicit and tested
  • Go/No-Go decision justified

ACTIVITY A: UNDERSTAND

5 Whys Analysis

Emit: Stated Problem: [Initial statement]; Why 1..Why 5 each -> [Answer] with Why 5 -> [Root Cause]; Validation Method: [How to verify].

Problem Severity

Rate each dimension 1-10: Frequency, Impact, Reach, Urgency, Strategic. Score = (Frequency x Impact x Reach) + (Urgency x 2) + (Strategic x 3)

Stakeholder Interview Structure

  1. Opening (5 min): Purpose, permission
  2. Context (15 min): Workflow, frustrations, magic wand
  3. Problem Exploration (20 min): Recent occurrence, actions, feelings, workarounds
  4. Impact (10 min): Time/money cost, others affected
  5. Solution Space (10 min): What tried, ideal solution
  6. Closing (5 min): Missing questions, who else to talk to

Questions: references/interview-guide.md

Stakeholder Power/Interest Matrix

Interest LowInterest High
Power HighSatisfyManage Closely
Power LowMonitorKeep Informed

Competitive Analysis

Table columns: Competitor, Target, Features, Pricing, Strengths, Weaknesses. Key questions: Gap in market? Overserved needs? Underserved needs? Emerging trends? Method: references/competitive-analysis.md

Jobs-to-be-Done

When [situation] I want to [progress] So I can [outcome]. Also capture emotional job, social job.

ACTIVITY B: EXPLORE

Brainstorming Techniques

  1. Classic: How Might We... (10 min)
  2. SCAMPER: Substitute, Combine, Adapt, Modify, Put to use, Eliminate, Reverse
  3. Crazy 8s: 8 ideas in 8 minutes
  4. Worst Possible Idea: generate terrible solutions, then reverse
  5. Six Thinking Hats: White(facts), Red(emotion), Black(risks), Yellow(benefits), Green(creative), Blue(process)

Facilitation: references/brainstorming-techniques.md

Idea Capture

Emit per idea: Idea: [Title]; ID: [PROJECT]-B-IDEA-[XXX]; One-Liner: [Explain in one sentence]; User Value: [Why would someone want this?]; Wild Rating: 1-5.

Root Cause Investigation

Systems Map: system boundaries; feedback loops (reinforcing/balancing); leverage points (small changes, big effects); unintended consequences.

Theory of Constraints:

  1. IDENTIFY the constraint
  2. EXPLOIT it (maximize output as-is)
  3. SUBORDINATE everything else
  4. ELEVATE the constraint (increase capacity)
  5. REPEAT (find new constraint)

Insight Clustering

Emit per cluster: Cluster: [Theme Name]; Insights: [List]; Pattern: [Common thread]; Opportunity: [What to do].

ACTIVITY C: DEFINE

Frameworks in depth: references/strategic-frameworks.md

Blue Ocean Strategy

Four Actions Framework — per factor, decide: ELIMINATE, REDUCE, RAISE, CREATE.

Value Proposition Canvas

Customer Profile: Jobs (Functional, Emotional, Social); Pains — [Pain]: Severity (1-10); Gains — [Gain]: Importance (1-10). Value Map: Products & Services; Pain Relievers; Gain Creators.

Opportunity Scoring

CriterionWeight
User Value30%
Feasibility25%
Strategic Fit20%
Time to Value15%
Risk Level10%

Score each option (Option A, Option B, ...) per criterion.

Assumption Mapping

Table columns: Assumption, Impact, Certainty, Validation Method. Example row: [Critical] | High | Low | [How to test].

Quick Reference

ModeTriggerToolsOutput
Business AnalystNeed evidenceInterviews, 5 Whys, JTBDProblem statement, stakeholder map
BrainstormingNeed ideasSCAMPER, Crazy 8s, Six HatsIdea backlog, opportunities
Problem-SolverNeed root causesSystems Map, TOC, TRIZRoot cause analysis
Innovation StrategistNeed positioningBlue Ocean, Value PropStrategic positioning

Common Pitfalls

PitfallFix
Solution BiasWrite assumptions, try to disprove
Confirmation SeekingAssign devil's advocate
Sampling BiasCover stakeholder matrix
Analysis ParalysisTime-box, define "good enough"
Idea AttachmentGenerate 10+ alternatives first

Minimum Viable Research (1 week)

  1. Day 1-2: 3-5 stakeholder interviews
  2. Day 3: Competitive scan (2 hours)
  3. Day 4: 90-minute brainstorm
  4. Day 5: Synthesis and recommendation

Output Location

docs/research/YYYY-MM-DD-[project]/
  research-report.md
  traceability-matrix.md
  interviews/
  analysis/
  ideation/
  opportunities/

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

aid-prd

無料

AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.

日本語の概要は準備中です。原文の説明を表示しています。

ilandahan/AID102026年9月23日 更新

ilandahan のスキルをすべて見る

このスキルの問題を報告する