Priori Dev

Appearance

A_Research ​

1. _RESEARCH Folder ​

Define features.

Likely multiple md files

Deep research similar applications. Compile the documents into a repository.

Knowledge File ​

` # Application & Industry Deep Research Prompt

** START PROMPT **

Instructions ​

You are an expert product analyst, UX researcher, and competitive intelligence specialist. Your task is to conduct a comprehensive deep-dive analysis of [APPLICATION NAME] within the [INDUSTRY] space.

Produce a highly detailed markdown document that serves as a living knowledge base. This document will be used to understand, evaluate, recreate, and improve features in the future. Do not summarize where detail is needed. Be exhaustive in feature documentation, user sentiment, and competitive positioning.

If you run out of space, divide the output into clearly labeled parts without losing information or context. If any part of this request is unclear, ask for clarification before proceeding.

Report Structure ​

1. Application Overview ​

  • What it is: One-sentence description of the application.
  • Core offer: What is the main product or service delivered to customers? (Summarize in a short phrase, then expand with a full paragraph.)
  • How it works: Step-by-step explanation of the user journey from sign-up/purchase through ongoing use.
  • Business model: How does the application make money? (Subscription tiers, freemium, one-time purchase, marketplace fees, etc.)

2. Target Market & Users ​

  • Primary audience: Who are the core users? Describe their demographics, roles, goals, pain points, and decision-making factors.
  • Secondary audiences: Are there other user segments the application serves?
  • User context: What situation or trigger drives someone to seek out this application? What motivates them to take action?

3. Problem & Value Proposition ​

  • Core problem solved: What specific, known problem does the target market face that this application addresses?
  • Emotional and practical motivators: Why do users care enough to act? What's at stake if they don't?
  • Key benefits: List and describe the top outcomes and advantages users experience. Be specific — not "saves time" but how it saves time and how much.
  • Unique differentiators: What sets this application apart from competitors? Describe the unique qualities, features, positioning, or experience that make it stand out.

4. Feature Inventory (CRITICAL SECTION — Be Exhaustive) ​

For every identifiable feature the application offers, document the following:

FieldDescription
Feature NameClear, descriptive name
What It DoesDetailed explanation of functionality
How It WorksStep-by-step mechanics from the user's perspective
User Problem It SolvesWhat specific need or pain point does this feature address?
Relationship to Other FeaturesHow does this feature connect to, depend on, or enhance other features?
StrengthsWhat users like about this feature (based on reviews, forums, industry commentary)
WeaknessesWhat users complain about, find frustrating, or wish was different
Improvement OpportunitiesSpecific, actionable suggestions for how this feature could be better — including what the improved version would look like and do

Organize features into logical groups/categories (e.g., Core Functionality, User Management, Analytics, Integrations, Communication, etc.).

5. Feature Relationship Map ​

Describe how the application's features work together as a system:

  • Which features are dependent on others? (Feature B requires Feature A to function.)
  • Which features enhance others? (Feature C becomes more powerful when used with Feature D.)
  • Are there gaps in the feature ecosystem? (A feature that logically should exist to connect two others, but doesn't.)
  • What is the core feature loop? (The primary cycle of actions that drives ongoing user engagement.)

6. User Sentiment Analysis ​

Based on available reviews, forums, social media, and industry commentary:

  • What users love: Top praised aspects, with specific examples and patterns.
  • What users dislike: Top complaints, frustrations, and unmet expectations.
  • Most requested features or changes: What do users consistently ask for that doesn't exist yet?
  • Churn reasons: Why do users leave? What causes them to switch to a competitor or abandon the solution entirely?

7. Competitive Landscape ​

  • Top competitors: List the primary competitors and briefly describe each.
  • Feature comparison: For each major feature category, note which competitors offer comparable, superior, or inferior versions.
  • Competitor advantages: What do competitors do better?
  • Competitor weaknesses: Where does the analyzed application win?
  • Market gaps: What does NO current player in this space do well, or at all?

8. Ideal User Experience & Feature Roadmap ​

Based on everything above, define:

  • What the end user truly wants: Synthesize user needs, complaints, and requests into a clear picture of the ideal experience.
  • What would solve their problems: Specific features, improvements, or changes that would directly address the most critical pain points.
  • What would elevate their experience: Beyond fixes — what innovations, enhancements, or new capabilities would make users enthusiastic advocates?
  • Priority recommendations: Rank the above by impact and feasibility (high impact + easy to implement → do first).

Output Requirements ​

  • Format: Markdown
  • Tone: Professional, analytical, precise
  • Detail level: Exhaustive — do not over-summarize or omit details for brevity
  • If referencing specific claims about user sentiment or market positioning, note the basis for the claim (e.g., "commonly reported in G2 reviews," "noted in industry analysis")
  • At the end, include a "Key Takeaways" section with a brief executive summary of the most critical findings

** END PROMPT **

lock

Enter PIN to continue