idea-refine

Refine raw ideas into problem statements, directions, and MVP scopes.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/alissonpef/copilot-agent-skills --skill idea-refine-alissonpef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idea-refine
Source: https://github.com/alissonpef/copilot-agent-skills/tree/main/.github/skills/idea-refine
Command: npx skills add https://github.com/alissonpef/copilot-agent-skills --skill idea-refine-alissonpef

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps turn vague, unstructured ideas into clear, actionable concepts by guiding structured divergence, evaluation, and convergence before anyone commits to building.

Core Features & Use Cases

  • Sharpen the problem: Reframe a rough concept into a precise problem statement that is easier to reason about.
  • Explore multiple directions: Generate several meaningful variations using lenses like inversion, simplification, audience shift, and combination.
  • Stress-test assumptions: Surface hidden bets, feasibility risks, and differentiation gaps before moving forward.
  • Produce a decision-ready artifact: Create a concise markdown one-pager with recommended direction, assumptions to validate, MVP scope, and explicit not-doing tradeoffs.
  • Use case: A founder, product manager, or team lead can use it to refine a feature idea, startup concept, or workflow improvement into something specific enough to validate or build.

Quick Start

Tell the assistant your rough idea and ask it to help refine it into a clear problem statement, promising directions, and a focused MVP.

Frequently Asked Questions about idea-refine

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

FAQPage Schema
How do I turn a rough product idea into a clear MVP scope?

To turn a rough product idea into a clear MVP scope, you need structured divergent and convergent thinking to reframe the concept into a precise problem statement, explore multiple directions, and define explicit not-doing tradeoffs.

What is the best way to stress-test hidden assumptions during ideation?

Stress-testing hidden assumptions during ideation involves surfacing feasibility risks and differentiation gaps by applying lenses like inversion, simplification, and audience shift to evaluate potential bets before committing to build.

How do I frame a problem statement from a blank slate feature concept?

Framing a problem statement from a blank slate feature concept requires interactive ideation to sharpen the vague premise into a specific, actionable direction that is easier to reason about and validate.

Can I use structured ideation for workflow improvements inside a codebase?

Yes, you can use structured ideation for workflow improvements inside a codebase, as the process supports teams exploring new features, processes, or modifications from an existing codebase or starting entirely from scratch.

What does a decision-ready artifact for concept validation look like?

A decision-ready artifact for concept validation is a concise markdown one-pager containing the recommended direction, assumptions to validate, focused MVP scope, and explicit not-doing tradeoffs to guide building.