>- Take a fuzzy idea (or an existing thing you want to improve) through a disciplined funnel — explore → pressure-test → converge — and produce one 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.
npx skills add https://github.com/nelsonwerd/idea-to-ship-skills --skill ideate
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take nelsonwerd/ideate from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.