# Ideation First

Use before planning a new feature or greenfield refactor whose requirements aren't yet...

- Repository: https://github.com/ccplugins/awesome-claude-code-plugins (991 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-08-12
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ccplugins/awesome-claude-code-plugins --skill ideation-first -g -a claude-code -y`
Codex: `npx skills add ccplugins/awesome-claude-code-plugins --skill ideation-first -g -a codex -y`
Cursor: `npx skills add ccplugins/awesome-claude-code-plugins --skill ideation-first -g -a cursor -y`
Gemini CLI: `npx skills add ccplugins/awesome-claude-code-plugins --skill ideation-first -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add ccplugins/awesome-claude-code-plugins`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.
- **`quick` one-liners**, typo fixes, obvious small edits. Ideation is overhead here.
- **`bugfix`**, bugs get root-cause investigation first via the `debugger`, 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.

The rest: https://github.com/ccplugins/awesome-claude-code-plugins/blob/HEAD/plugins/craftsman/skills/ideation-first/SKILL.md