idea-to-ship-skills

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).

build-loop

Drive a build to actually-works, near-finish-line craft by looping build → see → exercise → check → critique → rebuild over the agent's existing tools (bash build/test, headless screenshot + vision, Playwright, axe/Lighthouse) until acceptance criteria pass or an explicit stop-condition fires — no infinite thrash. ALWAYS invoke when the user says any of "tighten this build", "iterate until it passes", "self-verify the UI", "make it actually work, not just compile", "loop until the core flows pass", or "drive this to near-finish-line". Also invoke proactively after a scaffold or feature lands and before handing a draft to a human. Composition-first over existing tools, not a new program; it states its own honest bounds — objective craft only, taste self-graded, ~80% ceiling, market validation out of scope. Do NOT use to decide WHAT to build (that's ideate) or whether a design/strategy is sound (deep-dive).

deep-dive

Rigorous multi-agent deep-dive analysis for complex investigative tasks — auditing codebases, evaluating strategies or systems, validating designs, doing open-ended research. Deploys 4–6 specialist agents in parallel across distinct lanes, then synthesis, then adversarial red-team review, then optional patching — producing structured markdown research files plus a plain-English executive briefing with honest 1–10 confidence ratings. ALWAYS invoke when the user says any of "deep dive", "thorough audit", "rigorous analysis", "comprehensive review", "audit this codebase", "analyze the strategy", "evaluate this design", "review this thoroughly", or "research deep dive". Also invoke proactively for any open-ended investigative task involving a codebase, strategy, system design, or research question that warrants 30+ minutes of structured analysis — even when the user doesn't use these exact phrases.

ideate

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.

prompt-pack

Author and execute "prompt packs" — a big job broken into a sequence of self-contained, independently-shippable prompts, each run in its own fresh chat so a single change never dies to a context/token limit. Also writes paste-ready handoff briefings to resume a dying chat or relay work to another tool (e.g. Codex). ALWAYS invoke when the user says any of "make a prompt pack", "turn this into prompts", "break this into phases", "prompts I can run in separate chats", "I'm running out of tokens/context", "write me a handoff", "a prompt I can paste into a new chat", "this is too big for one chat", "build plan I can hand off", or "execute Pxx / phase X from the pack". Also invoke proactively when a requested change is too large or too risky to finish safely in one session and should be decomposed into ordered, verifiable steps.

Quality Score: 62/100

Stars 20%

Recency 20%

Manifest 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Details

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

Listed in marketplaces