Ideate

• How does a user discover this?
• What's the happy path?
• What does success look like?

4. Constraints

• Any technical constraints?
• Timeline or scope limits?
• Dependencies on other systems?

Output Format

After brainstorming, produce a Feature Description ready for speckit:

## Feature: [Name]

### Problem
[1-2 sentences describing the problem]

### Solution
[1-2 sentences describing the solution]

### User Stories
1. As a [user], I want to [action] so that [benefit]
2. ...

### MVP Scope
- [ ] Feature 1
- [ ] Feature 2
- [ ] Feature 3

### Out of Scope (v2+)
- Feature X
- Feature Y

### Constraints
- [Any technical/business constraints]

Handoff to Spec-Kit

Once the feature description is complete, hand off to spec-kit-skill:

1. Install spec-kit-skill (if not already):

   /plugin marketplace add feiskyer/claude-code-settings
   /plugin install spec-kit-skill
   

2. Run spec-kit workflow:

   • The spec-kit-skill auto-triggers when you mention "spec-kit" or reference .specify/
   • It guides through: specify → clarify → plan → tasks

3. Continue to execution:

   • Once tasks.md is ready, the execute skill handles autonomous implementation

Example Session

User: "I have an idea for a CLI tool that helps manage dotfiles"

Claude (with ideate skill):

1. Asks about core value: "What pain point does this solve?"
2. Asks about features: "What are the must-have capabilities?"
3. Asks about users: "Who is this for - beginners or power users?"
4. Produces feature description
5. Suggests: "Ready to create the PRD? Run /speckit.specify with this description."