Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured validation framework that scores product ideas. Use when evaluating problem severity, willingness-to-pay, or founder-market fit. For market intelligence, see market-research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
| Tool | Purpose |
|---|---|
firecrawl_search | Validate market signals, demand indicators |
firecrawl_extract | Pull data from market reports, forums |
Get from the user (or from completed Phase 0 deliverables):
Each dimension scored 1-5. Total score determines recommendation.
| Score | Criteria |
|---|---|
| 1 | Nice-to-have. Users tolerate current solutions fine. |
| 2 | Mild annoyance. Users complain but don't switch. |
| 3 | Real pain. Users actively search for alternatives. |
| 4 | Hair-on-fire. Users lose money/time daily without a solution. |
| 5 | Mission-critical. Business cannot function without solving this. |
Validate with:
firecrawl_search: "{problem_statement} pain point frustrated"
firecrawl_search: "site:reddit.com {target_user} struggling with {problem}"
| Score | Criteria |
|---|---|
| 1 | Users expect free. No existing paid solutions. |
| 2 | Users pay reluctantly. < $10/mo willingness. |
| 3 | Established paid market. $10-50/mo common. |
| 4 | Users budget for this. $50-200/mo normal. |
| 5 | Enterprise budgets. $200+/mo, multi-seat deals. |
Validate with:
firecrawl_search: "{category} pricing SaaS"
firecrawl_search: "{competitor} pricing plans"
| Score | Criteria |
|---|---|
| 1 | Market is saturated or declining. |
| 2 | Market exists but growth is flat. |
| 3 | Growing market with room for new entrants. |
| 4 | Emerging market with strong tailwinds (AI, regulation, etc.). |
| 5 | Category creation opportunity — no one owns this yet. |
| Score | Criteria |
|---|---|
| 1 | No domain expertise, no network, no unfair advantage. |
| 2 | Some interest but learning from scratch. |
| 3 | Adjacent experience. Understand the user but not the domain deeply. |
| 4 | Direct experience. Have felt this pain personally. |
| 5 | Deep domain expertise + network + distribution advantage. |
| Score | Criteria |
|---|---|
| 1 | Requires team of 10+, $1M+, regulatory approval. |
| 2 | Needs specialized skills the founder lacks. |
| 3 | Achievable solo with AI tools in 3-6 months. |
| 4 | MVP shippable in 30-60 days with existing tools. |
| 5 | Can validate in a weekend with no-code or AI agents. |
# Idea Validation Scorecard: {Idea Name}
| Dimension | Score | Evidence |
|-----------|-------|----------|
| Problem Severity | X/5 | {one-line justification} |
| Willingness to Pay | X/5 | {one-line justification} |
| Market Timing | X/5 | {one-line justification} |
| Founder-Market Fit | X/5 | {one-line justification} |
| Execution Feasibility | X/5 | {one-line justification} |
| **TOTAL** | **XX/25** | |
## Recommendation
- 20-25: **STRONG GO** — Execute immediately.
- 15-19: **CONDITIONAL GO** — Proceed but validate {weakest dimension} first.
- 10-14: **PAUSE** — Significant risks. Pivot or de-risk before investing.
- 5-9: **NO GO** — Fundamental problems. Explore different ideas.
Regardless of score, flag these as deal-breakers:
Save to BRAINIAC/0. Idea/VALIDATION_SCORECARD.md
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured competitor teardown skill. Use when scraping competitor sites, extracting pricing/features/positioning, or analyzing strategic gaps. For general research, see market-research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates an llms.txt file from scratch based on repository structure. Use when configuring LLM discovery files. For updating existing configurations, see update-llms.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans ./ directory files and creates a README.md file for the project. Only used when creating a new repository. or when the README.md file is missing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Standardizes git operations, branch management, and disaster recovery. Use when committing, branching, or resolving conflicts. For commit formatting, see conventional-commits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.