idea-sprint

Solid

Find and validate what to build in crypto. Use when the user asks "what should I build", "validate this idea", "is this worth building", "find me a startup idea", "crypto idea", or wants blunt feedback on a project concept before writing code.

Code & Development 97 stars 60 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
66
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- Adapted from sendaifun/solana-new (find-next-crypto-idea, validate-idea), MIT © 2026 SendAI and Superteam. Telemetry removed. --> # Idea Sprint Interview → necessity gate → 3 candidates → score → go/no-go. Output is a decision, not a brainstorm. ## Context handoff - At start: read `.claude/context/idea.md` and `.claude/context/build.md` if present — resume from prior state instead of re-interviewing. - On completion: write/update `.claude/context/idea.md` with the chosen idea, scores, validation evidence, and open risks. Downstream skills (pitch-deck, hackathon) read it. ## Workflow ### 1. Blunt interview No flattery. Short, pointed questions, one at a time, until three things are explicit: - **Edge** — what the founder knows/can do that most can't (domain, distribution, tech) - **Constraint** — time, money, team, chain commitments - **Wedge** — the niche entry point, not the end-state vision Push back on vague answers. "DeFi for everyone" is not a wedge. Full question bank: [interview-framework.md](../ext/solana-new/skills/idea/find-next-crypto-idea/references/interview-framework.md). ### 2. Crypto-necessity gate Kill question: **"What gets worse if I remove the blockchain?"** If the answer is vague, aesthetic, or marketing-driven — redirect the idea before scoring it. Pass criteria and redirect patterns: [crypto-necessity-test.md](../ext/solana-new/skills/idea/find-next-crypto-idea/references/crypto-necessity-test.md). ### 3. Exactly 3 candidates Generate ...

Details

Author
solanabr
Repository
solanabr/solana-ai-kit
Created
7 months ago
Last Updated
today
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

ideate

Structured idea generation for a project or a blank-slate problem — ideas worth pursuing, not the first one that sticks. Grounds in the current repo (AGENTS.md/README) or a freeform problem, then diverges across named lenses (adjacent user, removed constraint, inversion, and more) so a run yields range, not ten variations of one idea. Fights premature convergence — nothing judged until the divergence quota is met — then verdicts each idea EXPLORE/PARK/DROP, where DROP is cheap. EXPLORE items become seeds for priorart (is it novel?) or feature (build it); verdicts persist in out/ideate/tracker.md so repeat runs open with what's new. Keyless. Use to generate, brainstorm, or explore ideas or new directions for a project or problem — e.g. "/ideate", "/ideate <topic>", "brainstorm features for X". For whether an idea already exists use priorart; for competitor features use scout; for choosing between named options use verdict.

9 Updated 3 days ago
duthaho
Code & Development Listed

ce-idea-scout

Generate, triage, and rank a shortlist of software/startup ideas — a verdict-rendering funnel (generate → cheap filter → seven-axis score → ranked directions). Opinionated rankings; decision support, not validated fact. Triggers: brainstorm/scout/generate/triage MANY ideas into a ranked shortlist. For ONE idea use /product-discovery:ce-idea-score; for market validation /product-discovery:ce-market-scan.

0 Updated 1 weeks ago
relusion
Code & Development Listed

idea-stress-test

Stress-test a business idea, product hypothesis, or new feature BEFORE building it, to decide whether it is worth your time. Use this skill whenever the user is weighing whether to build, launch, or invest time in an idea — phrases like "should I build", "is this worth it", "I have an idea for", "thinking about a startup/product/feature", "validate my idea", "проверь гипотезу", "стоит ли делать". The skill forces the idea through a fixed gauntlet — who pays, what already solves this pain for free, the cheapest 7-day test, and a pre-committed kill criterion — and ends with a GO / NO-GO / TEST-FIRST verdict. Pushes back on the framing instead of cheerleading. Lean toward triggering this even when the user only hints at evaluating an idea, because the most expensive mistake is skipping validation and building the wrong thing.

0 Updated 3 weeks ago
cheRoma