idea-refine

Refines raw ideas into actionable one-pagers through structured divergent and convergent thinking.

Updated May 21, 2026
One-click install
npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill idea-refine-nicorevo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: idea-refine
Source: https://github.com/nicorevo/AI-SDLC-Template/tree/main/.opencode/skills/idea-refine
Command: npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill idea-refine-nicorevo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Raw ideas are often vague, untested, and anchored on the first solution that comes to mind. This Skill turns fuzzy concepts into sharp, validated directions by forcing structured exploration, honest stress-testing, and explicit assumption surfacing before any building begins. ## Core Features & Use Cases - Three-Phase Ideation Dialogue: Guides you through divergent expansion (5-8 idea variations using lenses like inversion and simplification), convergent evaluation (stress-testing against user value, feasibility, and differentiation), and sharpening into a final artifact. - Assumption Auditing: Explicitly surfaces hidden assumptions, kill risks, and what you are choosing to ignore, with validation strategies for each. - Markdown One-Pager Output: Produces a concrete document with problem statement, recommended direction, MVP scope, and a "Not Doing" list, saved to docs/ideas/ after your confirmation. - Use Case: You have a vague idea like "help restaurants compete with delivery apps." Invoke the skill, answer a few sharpening questions, review generated variations, and walk away with a focused one-pager defining the riskiest assumption to test first. ## Quick Start Ask the agent to help you refine or stress-test your idea by describing it in one or two sentences.

Frequently Asked Questions about idea-refine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refine a vague product idea before building it?▼

Invoke the skill with your idea and it guides you through three phases: restating the problem as a How Might We statement, generating 5-8 variations using lenses like inversion and simplification, then stress-testing the strongest directions against user value, feasibility, and differentiation.

What is the best way to stress-test assumptions in a new idea?▼

The skill's Phase 2 surfaces hidden assumptions for each direction, categorizing them as dealbreakers, important, or nice-to-have. Each assumption gets a concrete validation strategy, and the final one-pager lists them as checkboxes to test before building.

Can this ideation skill work inside an existing codebase?▼

Yes. When run inside a project, it uses Glob, Grep, and Read to scan existing architecture, patterns, and constraints. Idea variations are grounded in what actually exists, referencing specific files and patterns when relevant.

What output does an ideation session produce?▼

The session ends with a markdown one-pager containing a problem statement, recommended direction, key assumptions to validate, MVP scope, a Not Doing list, and open questions. It is saved to docs/ideas/ only after you confirm.

When should I not use structured ideation for an idea?▼

Skip it when the idea is already well-defined with validated assumptions and a clear user, or when you need immediate implementation rather than exploration. The skill is designed for the fuzzy front end, not execution planning.