AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
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.
| Pillar | Focus | Key Question |
|---|---|---|
| Business Analysis | Evidence & Requirements | What do we know for certain? |
| Creative Problem-Solving | Root Causes & Systems | What's really going on? |
| Brainstorming | Possibilities & Ideas | What could we do? |
| Innovation Strategy | Value & Positioning | Why would anyone care? |
ACTIVITY A: UNDERSTAND (problem analysis, stakeholder map, market research) -> ACTIVITY B: EXPLORE (ideation, root cause hunt) -> ACTIVITY C: DEFINE (strategic synthesis, validation)
ID format: [Project]-[Activity]-[Type]-[Number]
PROJ-A-INT-001 = Interview finding #1PROJ-B-IDEA-003 = Idea #3PROJ-C-OPP-002 = Opportunity #2Traceability matrix columns:
| Research ID | Finding | Source | PRD Requirement | User Story |
|---|---|---|---|---|
| PROJ-A-INT-001 | Users frustrated by X | Interview | REQ-001 | US-001 |
Details: references/traceability-guide.md
Entry: initial idea/request/problem exists; stakeholders available; time allocated (minimum 2-3 sessions).
Exit (Gate to PRD):
Emit: Stated Problem: [Initial statement]; Why 1..Why 5 each -> [Answer] with Why 5 -> [Root Cause]; Validation Method: [How to verify].
Rate each dimension 1-10: Frequency, Impact, Reach, Urgency, Strategic. Score = (Frequency x Impact x Reach) + (Urgency x 2) + (Strategic x 3)
Questions: references/interview-guide.md
| Interest Low | Interest High | |
|---|---|---|
| Power High | Satisfy | Manage Closely |
| Power Low | Monitor | Keep Informed |
Table columns: Competitor, Target, Features, Pricing, Strengths, Weaknesses.
Key questions: Gap in market? Overserved needs? Underserved needs? Emerging trends?
Method: references/competitive-analysis.md
When [situation] I want to [progress] So I can [outcome]. Also capture emotional job, social job.
Facilitation: references/brainstorming-techniques.md
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.
Systems Map: system boundaries; feedback loops (reinforcing/balancing); leverage points (small changes, big effects); unintended consequences.
Theory of Constraints:
Emit per cluster: Cluster: [Theme Name]; Insights: [List]; Pattern: [Common thread]; Opportunity: [What to do].
Frameworks in depth: references/strategic-frameworks.md
Four Actions Framework — per factor, decide: ELIMINATE, REDUCE, RAISE, CREATE.
Customer Profile: Jobs (Functional, Emotional, Social); Pains — [Pain]: Severity (1-10); Gains — [Gain]: Importance (1-10). Value Map: Products & Services; Pain Relievers; Gain Creators.
| Criterion | Weight |
|---|---|
| User Value | 30% |
| Feasibility | 25% |
| Strategic Fit | 20% |
| Time to Value | 15% |
| Risk Level | 10% |
Score each option (Option A, Option B, ...) per criterion.
Table columns: Assumption, Impact, Certainty, Validation Method. Example row: [Critical] | High | Low | [How to test].
| Mode | Trigger | Tools | Output |
|---|---|---|---|
| Business Analyst | Need evidence | Interviews, 5 Whys, JTBD | Problem statement, stakeholder map |
| Brainstorming | Need ideas | SCAMPER, Crazy 8s, Six Hats | Idea backlog, opportunities |
| Problem-Solver | Need root causes | Systems Map, TOC, TRIZ | Root cause analysis |
| Innovation Strategist | Need positioning | Blue Ocean, Value Prop | Strategic positioning |
| Pitfall | Fix |
|---|---|
| Solution Bias | Write assumptions, try to disprove |
| Confirmation Seeking | Assign devil's advocate |
| Sampling Bias | Cover stakeholder matrix |
| Analysis Paralysis | Time-box, define "good enough" |
| Idea Attachment | Generate 10+ alternatives first |
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.
中文简介正在准备中。当前显示原文说明。
AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.
中文简介正在准备中。当前显示原文说明。
AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.
中文简介正在准备中。当前显示原文说明。
AID Phase 2 - Technical Specification. Use for system architecture, API contracts, data models, security architecture, transitioning from PRD to implementation.
中文简介正在准备中。当前显示原文说明。