Back to list
ilandahan

pre-prd-research

by ilandahan

AID - AI Development process - Complete methodology for AI-assisted full-stack software development. E2E process from raw ideas to deploy.

7🍴 1📅 Jan 22, 2026

SKILL.md


name: pre-prd-research description: 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.

Pre-PRD Research Skill

Core Belief

Every great product starts with deep understanding. Fall in love with the problem, not the solution.

The 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?

Research Activities Flow

ACTIVITY A: UNDERSTAND -> ACTIVITY B: EXPLORE -> ACTIVITY C: DEFINE
Problem Analysis          Ideation & Exploration   Strategic Synthesis
Stakeholder Map           Root Cause Hunt          Validation
Market Research

Traceability

ID Format

[Project]-[Activity]-[Type]-[Number]
Examples:
PROJ-A-INT-001 = Interview finding #1
PROJ-B-IDEA-003 = Idea #3
PROJ-C-OPP-002 = Opportunity #2

Traceability Matrix

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

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

Stated Problem: [Initial statement]
Why 1: -> [Answer]
Why 2: -> [Answer]
Why 3: -> [Answer]
Why 4: -> [Answer]
Why 5: -> [Root Cause]
Validation Method: [How to verify]

Problem Severity

DimensionRating (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

Stakeholder Power/Interest Matrix

            INTEREST
            Low     High
      High | Satisfy | Manage Closely |
POWER Low  | Monitor | Keep Informed  |

Competitive Analysis

CompetitorTargetFeaturesPricingStrengthsWeaknesses

Key Questions

  • Gap in market?
  • Overserved needs?
  • Underserved needs?
  • Emerging trends?

Jobs-to-be-Done

When [situation] I want to [progress] So I can [outcome]

Related: 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)

Idea Capture

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

Cluster: [Theme Name]
Insights: [List]
Pattern: [Common thread]
Opportunity: [What to do]

ACTIVITY C: DEFINE

Blue Ocean Strategy

Four Actions Framework

FactorELIMINATEREDUCERAISECREATE
[Factor]

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

CriterionWeightOption AOption B
User Value30%
Feasibility25%
Strategic Fit20%
Time to Value15%
Risk Level10%

Assumption Mapping

AssumptionImpactCertaintyValidation Method
[Critical]HighLow[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/

Score

Total Score

70/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon