prompts!
Browse
Back to prompts
Research
Any model

Competitive Feature Research

Summarize how others solve this problem and what we should borrow or avoid.

Prompt
Copy the prompt, then replace the placeholders with your own context.
Research how comparable products solve [feature/problem]. Structure: 1. 3–5 reference products or patterns 2. What works well for users 3. What to avoid (complexity, lock-in, privacy) 4. Implications for our constraints (stack, team size, timeline) 5. Recommended MVP scope Cite sources. No marketing fluff — focus on mechanics users feel.

Related prompts

More prompts with similar tags or categories.

Research
Claude
Summarize approaches from docs and threads to inform an architecture decision.
143 copies

Summarize research to inform a decision on [topic]. Include: - Common approaches and when each fits - Tradeoffs (complexity, cost, operability) - What our codebase already assumes - Recommendation with reversible vs one-way door flagged Link to official docs where possible. Mark uncertain claims.

research
architecture
by prompts!
View
Research
Any model
Walk from incident symptom to systemic fix with the five whys.
154 copies

Analyze this incident using five whys. Output: 1. Timeline of events 2. Five whys chain from symptom to root cause 3. Contributing factors (not just one root) 4. Corrective actions (immediate vs systemic) 5. What we should monitor to detect recurrence Blameless tone. Focus on process and systems.

incident
postmortem
by prompts!
View
Research
Any model
Explore unknowns in a fixed timebox and report options with a recommendation.
198 copies

Run a timeboxed technical spike (assume 2–4 hours of work). Deliverable: 1. Questions we needed to answer 2. What you tried and what you learned 3. Options compared (pros/cons/constraints) 4. Recommendation with confidence level 5. Follow-up tasks if we proceed Do not productionize spike code — prototypes are disposable unless stated otherwise.

spike
architecture
by prompts!
View