Idea Sprint Skill for Claude

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.

1.3k tokens

context cost

SKILL.md, read when the skill is used

files

instructions only

copies elsewhere

how many repositories repackaged it

105

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/solanabr/solana-ai-kit --skill idea-sprint

The instruction itself

12 sections, as written by the author

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.

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.

3. Exactly 3 candidates

Generate three diverse candidates (different mechanisms/markets, not three flavors of one idea). For each:

One-line pitch + target user
Winner case — what's true in 18 months if it works
Bear case — the most likely way it dies

Seed from datasets + live landscape (below), then combine with fresh research. Datasets are inspiration, not constraints.

4. Score /15

Each candidate, 0–3 per dimension (full anchors: scoring-rubric.md):

| Dimension | 3 means |

|-----------|---------|

| Founder fit | unfair advantage |

| MVP speed | shippable in under a week |

| Distribution | first ten users are obvious |

| Market pull | people already paying for bad alternatives |

| Revenue path | clear monetization story |

5. Validate + go/no-go

Check demand signals against customer-signal-rubric.md — manual workarounds, active forks, bounties, on-chain activity = real; likes and "cool idea" replies = noise. Sprint structure: validation-framework.md.

≥ 8/15 → go. Write idea.md, suggest /scaffold next.
6–7 → conditional: name the one dimension to de-risk first.
< 6 → strong no-go. Every no-go gets a pivot suggestion — use pivot-or-persist.md.

6. Write `.claude/context/idea.md`

Chosen idea, wedge, scores table, demand evidence, bear case, next step.

Idea datasets (inert JSON, ~515 entries)

In ../ext/solana-new/skills/data/ideas/:

web3-ideas-combined.json — master list (summary)
a16z-big-ideas-2025.json, a16z-state-of-crypto-2025.json
yc-requests-for-startups.json, yc-crypto-companies.json
alliance-ideas.json, superteam-ideas.json
rwa-defi-2026-ideas.json, yash-defi-2024-ideas.json

Idea-source guides (markdown commentary on the same sources): ../ext/solana-new/skills/data/guides/ — plus source-map.md and research-playbook.md for where/how to research live.

Live hackathon landscape

ext/colosseum — 5,400+ Colosseum submissions for crowdedness checks, winner patterns, and gap analysis (requires COLOSSEUM_COPILOT_PAT).

Output format

Report spec (3 ranked candidates, scores, decision): output-spec.md.

Other skills for the same job

different authors, same section of the catalogue

Demand Intake

by anthropics

vendor

Pre-drafting context gathering for a demand letter — parties, facts, basis, leverage, BATNA, and privilege filters — written to a structured intake.md the demand-draft skill reads. Use when the user wants to prep a demand letter, run intake before drafting, or capture context for a payment demand, breach/cure notice, cease-and-desist, employment separation, or preservation demand.

3.2k tokens

Fintech Agreement Drafting Stephane Boghossian

by lawve-ai

An end-to-end method for drafting and finalising a complex, multi-pillar regulated fintech agreement — from intake to signature. Authored from a senior fintech lawyer's manual: a licensed payment-services provider engaging a counterparty across agent cash-in/cash-out, QR payments, wallet e-payments, and a marketplace, each with its own regulatory profile. Runs five phases and fourteen steps: regulatory mapping (activity-to-licence matrix, grey-zone classification gates), architecture (framework-plus-sub-agreement structure, ring-fenced marketplace), the regulatory–commercial balance (what flexes vs what cannot), core drafting (authority, float mechanics, hard-coded regulator caps, liability — all tracking control), execution-blocker triage, and a pre-signature check closing open blockers as conditions precedent. It refuses to invent licence-specific values or draft a representation as true without executed evidence. Use it to structure, draft, negotiate, or review any regulated payments contract.

7.7k tokens

Webflow Mcp:cms Collection Setup

by webflow

Create a new CMS collection in Webflow with specified fields and relationships. Use when setting up blog posts, products, team members, portfolios, or other content types with custom fields.

8.1k tokens

Writing Bots

by ComeOnOliver

Write a bot to continuously listen and respond to events on a public blockchain network.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens

Test Driven Development

by w95

×9

Use when implementing any feature or bugfix, before writing implementation code

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens