ideate

Solid

Take a fuzzy idea (or an existing thing you want to improve) through a disciplined funnel — explore → pressure-test → converge — and produce one living CONCEPT_BRIEF.md: a locked concept + phased roadmap. Acts as a blunt, honest co-founder (permission to overrule you), forces a success metric and a kill criterion before any roadmap, and hands off cleanly to the prompt-pack skill for building. ALWAYS invoke when the user says any of "help me figure out what to build", "I have an idea for…", "is this idea any good", "pressure-test this idea", "should I build / should I rebuild X", "evaluate whether my app/idea is worth building", "where are we really at", "is this idea or app worth pursuing", "iron out / scope / spec this concept", or "turn my idea into a plan/roadmap". Also invoke proactively when someone is reasoning about WHAT to build or WHETHER an idea is worth it — before any code or prompt pack exists.

AI & Automation 83 stars 8 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
64
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Ideate — fuzzy idea → locked concept + roadmap `ideate` is the **upstream partner to the `prompt-pack` skill**. It takes an idea that's still fuzzy — or an existing project you want to evaluate and improve — and runs it through a disciplined funnel that ends in one durable artifact: a **`CONCEPT_BRIEF.md`** holding the locked concept, the honest verdict, and a phased roadmap. That brief is exactly what `prompt-pack` consumes to produce build prompts. The whole pipeline: > **ideate → `CONCEPT_BRIEF.md` → prompt-pack → execute** This skill encodes a method reverse-engineered from real, successful idea→ship journeys — *including the mistakes those journeys made*, so it improves on them rather than repeating them. ## Why this exists (the problem it solves) Left unstructured, ideation with an AI fails in predictable ways: - **It specs too early.** A full data model and endpoints get written before anyone asks "is this even a good idea?" — so effort pours into an unvalidated concept. - **It forgets.** The AI re-derives the same "is this a business?" assessment every session; the user re-pastes context; decisions never settle. (This is the single biggest failure.) - **It has no finish line.** No success metric, no kill criterion — so the concept mutates forever and no one can say whether it's working. - **It over-commits.** A giant roadmap gets locked before the first piece is validated. - **It drifts** (when improving an existing thing) away from the original it was suppose...

Details

Author
nelsonwerd
Repository
nelsonwerd/idea-to-ship-skills
Created
2 months ago
Last Updated
2 weeks ago
Language
Shell
License
MIT

Integrates with

Bundled in these plugins

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 yesterday
duthaho
AI & Automation Solid

autopilot

Run the idea-to-ship pipeline AUTONOMOUSLY, in character as a grounded founder-persona — composing ideate → deep-dive → prompt-pack → build-loop to take a real, grounded niche to a near-finish-line-AIMED first-draft product plus an honest ledger of what only a human or the market can finish. ALWAYS invoke when the user says any of "run autopilot", "build this idea→ship autonomously", "spin up a grounded founder and build it", "fly the whole pipeline end to end", or "autonomous first-draft from a concept". It composes the existing skills, never reimplementing them, and states its honest bounds — a near-finish-line first draft, NOT a finished or market-validated product (~80% craft ceiling; grounding firewall; its go/kill calls are a signal). Do NOT use to drive each phase by hand (use the skills directly), when there's no real grounding (you'd be inventing demand), or when you need market validation (the human handoff).

83 Updated 2 weeks ago
nelsonwerd
AI & Automation Listed

critical-thinking

Think hard about an idea, plan, or decision before committing to build it - the counterweight to AI's built-in pull toward agreeing, praising, and building whatever is asked. Load when the user proposes a solution, feature, approach, or "wouldn't it be great if", when begin's challenge step hands over a fresh product idea, when weighing options in scope/spec/architect/design, and any time you notice yourself about to agree enthusiastically or open with praise. Forces a named alternative, surfaces the load-bearing assumption, separates preference from requirement, and asks what would prove the idea wrong - then commits to the user's call. The judgment layer at the entrance to building; mirror of scope-guard at the exit.

2 Updated today
Tradebaas