| name | idea-interview |
| description | Conducts an interactive conversation to flesh out a vague or half-formed idea into something specific and actionable. Asks clarifying questions, suggests tags and first steps, and updates the idea in idea.log. Use when you have a rough concept that needs development. |
Interview an Idea Into Shape
Works with idea.log. Get it on the App Store.
When to Use
- You captured a quick idea and want to develop it further
- An idea is too vague to act on and needs structure
- You want help identifying the right first step for an idea
- You're not sure how to tag or categorize an idea
How It Works
- User specifies which idea to interview (by name or search term)
- Search for the idea with
search_ideas and fetch full details with get_idea
- Ask the user 3-5 targeted questions about the idea's scope, motivation, and constraints
- Based on answers, draft an improved description, suggest tags, and propose a first step
- Confirm changes with the user, then apply with
update_idea
- Add a comment with
add_comment summarizing the interview outcome
Interview Framework
Questions to Ask
Adapt based on the idea's domain, but draw from:
- Motivation โ "What problem does this solve? Who would use it?"
- Scope โ "Is this a weekend project or something bigger? What's the minimum viable version?"
- Prior art โ "Have you seen anything similar? What would you do differently?"
- Constraints โ "Any tech stack preferences? Timeline? Dependencies on other work?"
- First step โ "If you had 30 minutes right now, what would you do first?"
Don't ask all five if the idea is already partially fleshed out. Read the existing content, comments, and tags first, and skip questions that are already answered.
Tag Suggestions
Based on the interview, suggest tags from common categories:
| Category | Example Tags |
|---|
| Type | app, tool, library, blog-post, experiment, refactor |
| Domain | web, mobile, cli, api, data, devops, design |
| Effort | quick-win, weekend, multi-week, ongoing |
| Priority | high, medium, low, someday |
Example
Input:
Interview my "dotfile manager" idea
Conversation:
Agent: I see your idea "dotfile manager tool" โ currently just the title with no first step
or tags. Let me ask a few questions.
What's the main problem you're trying to solve? Are you managing dotfiles
across multiple machines, or is this more about version control for configs?
User: Both โ I have 3 machines and I always forget which one has the latest zshrc.
Agent: Got it. Are you thinking a CLI tool, a GUI, or something that hooks into
an existing tool like chezmoi or GNU stow?
User: CLI. I've used stow but I want something that also handles secrets
and machine-specific overrides.
Agent: Makes sense. Here's what I'd suggest:
Updated description: "CLI tool for managing dotfiles across multiple machines.
Handles symlinking, secrets management, and machine-specific config overrides.
Differentiator vs stow/chezmoi: unified secrets + per-machine profiles."
Tags: cli, tool, devops, multi-week
First step: "Survey chezmoi and stow feature sets, list gaps for secrets
and machine profiles"
Want me to save these updates?
User: Yes
Agent: Done. Updated the idea and added a comment noting the interview.
Checklist
Idea Interview:
- [ ] Found and reviewed the target idea
- [ ] Asked 2-5 clarifying questions
- [ ] Drafted improved description
- [ ] Suggested relevant tags
- [ ] Proposed a concrete first step
- [ ] Confirmed changes with user before saving
- [ ] Added interview summary as a comment
Learn More
