Ideation First
Use before planning a new feature or greenfield refactor whose requirements aren't yet...
Install
npx skills add ccplugins/awesome-claude-code-plugins --skill ideation-first -g -a claude-code -y- Repository
- ccplugins/awesome-claude-code-plugins991
- Category
- Engineering
- Updated
- 3mo ago
- License
- Apache-2.0
- Context cost
- Lightabout 864 tokens
- Runs scripts
- No, instructions only
What it does
Use before planning a new feature or greenfield refactor whose requirements aren't yet pinned down, clarifies intent through a few questions and ends with a short scope brief the planner can build on.
Ideation First
Overview
Planning against guessed requirements wastes work. The planner turns a request into ordered steps, but if the request itself is vague, every step is built on a guess, and the further the pipeline runs, the more expensive that guess is to unwind. This skill settles the what before anyone plans the how.
Core principle: clarify the what before planning the how.
When this applies
A request for a new capability, feature, or greenfield refactor whose requirements aren't pinned down, the goal, the boundaries, or the success criteria are open to interpretation. Signals: "build a … screen", "add … support", "let users …", "we need something that …" with no spec.
When to skip
- Well-specified requests, the goal, inputs, and done-condition are already unambiguous. Don't interrogate when the ask is clear; go straight to planning.
quickone-liners, typo fixes, obvious small edits. Ideation is overhead here.bugfix, bugs get root-cause investigation first via thedebugger, not requirements clarification. The "what" is already defined (make the broken thing work).
If you find yourself asking questions whose answers you already have, stop, you're past the point this skill is for.
The process
Keep it lightweight. The value is a locked scope, not ceremony.
