-
Notifications
You must be signed in to change notification settings - Fork 1
Fix: Define Ideal Customer Profile #147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
naga-k
wants to merge
2
commits into
main
Choose a base branch
from
fix/soulcaster-1766333455
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| # Product Strategy: Ideal Customer Profile & Use Cases | ||
|
|
||
| ## 1. Ideal Customer Profile (ICP) | ||
|
|
||
| **Target Audience:** Software Engineering Teams & Open Source Maintainers | ||
| **Industry:** SaaS, Developer Tools, Open Source Software | ||
| **Company Stage:** Early-stage startups to mid-sized engineering organizations (where resources are tight and triage load is high). | ||
|
|
||
| ### Roles | ||
| * **The Overwhelmed Maintainer:** Maintains popular open-source projects or internal libraries. Drowning in GitHub Issues and duplicates. Needs help separating signal from noise and clearing the backlog. | ||
| * **The Tech Lead / Senior Engineer:** Responsible for product quality but stuck doing low-value maintenance work. Wants to focus on architecture and features, not minor bug fixes. | ||
| * **The "DevOps" Minded Developer:** Cares about automation and efficiency (CI/CD, self-healing systems). | ||
|
|
||
| ### Pains | ||
| * **Triage Fatigue:** Spending hours manually reviewing, labeling, and deduplicating bug reports across multiple channels (GitHub, Sentry, Reddit). | ||
| * **Context Switching:** Constant interruptions from minor bugs prevent deep work on core features. | ||
| * **Slow Feedback Loops:** User reports a bug, it sits in a backlog for weeks because it's "low priority," leading to user churn. | ||
| * **Fragmentation:** Feedback is scattered across Reddit threads, Sentry logs, and GitHub issues, making it hard to see the "big picture" of what's broken. | ||
|
|
||
| ## 2. Primary Use Cases | ||
|
|
||
| ### A. Automated Bug Triage & Resolution (The "Self-Healing" Loop) | ||
| * **Scenario:** A runtime error occurs in production (captured by Sentry) or a user files a bug report on GitHub. | ||
| * **Action:** Soulcaster ingests the report, checks if it matches existing clusters (deduplication), and if it's actionable, the AI agent attempts to reproduce and fix it in a sandboxed environment. | ||
| * **Benefit:** The engineer wakes up to a PR fixing the bug instead of an alert notification. | ||
|
|
||
| ### B. Community Feedback Aggregation | ||
| * **Scenario:** Users are complaining about a specific UI glitch or workflow friction on a subreddit or community forum. | ||
| * **Action:** Soulcaster polls the subreddit, identifies the cluster of negative sentiment/bug reports, summarizes the core issue, and prepares a fix or a detailed spec for the developer. | ||
| * **Benefit:** Proactive community management; users feel heard without the team manually scouring forums. | ||
|
|
||
| ### C. Backlog Grooming & Janitorial Work | ||
| * **Scenario:** A project has hundreds of stale issues. | ||
| * **Action:** Soulcaster analyzes the backlog, clusters duplicates, identifies "wontfix" items, and proposes fixes for low-hanging fruit. | ||
| * **Benefit:** Reduces technical debt and cleans up the project hygiene. | ||
|
|
||
| ## 3. MVP Scope (Current State) | ||
|
|
||
| * **Ingestion:** | ||
| * Reddit (Polling specific subreddits) | ||
| * Sentry (Webhooks) | ||
| * GitHub Issues | ||
| * Manual Entry | ||
| * **Intelligence:** | ||
| * Vector-based Clustering (Gemini Embeddings + Upstash) to group similar feedback. | ||
| * LLM Summarization for cluster titles and descriptions. | ||
| * **Execution:** | ||
| * AI Coding Agent (running in E2B sandboxes) that can read code, write patches, and run tests. | ||
| * GitHub Integration to open PRs directly from the user's account. | ||
| * **Interface:** | ||
| * Next.js Dashboard for human-in-the-loop review (approve fixes, view clusters). | ||
|
|
||
| ## 4. Key Messaging Bullets | ||
|
|
||
| * **"Turn Noise into Code":** Don't just log bugs—fix them. | ||
| * **"Your AI Junior Engineer":** Handles the triage and minor fixes so you can focus on the hard stuff. | ||
| * **"Unified Feedback Stream":** See what users are saying on Reddit, GitHub, and Sentry in one prioritized view. | ||
| * **"One-Click Fixes":** Move from problem identification to Pull Request in a single click. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion | 🟠 Major
Fix markdown list indentation.
Nested list items use 4-space indentation instead of 2 spaces. Per markdownlint (MD007), this should be corrected for consistency and markdown compliance.
🔎 Proposed indentation fix
📝 Committable suggestion
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
40-40: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
41-41: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
42-42: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
43-43: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
45-45: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
46-46: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
48-48: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
49-49: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
51-51: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
🤖 Prompt for AI Agents