idea-refine

Generate 3-5 actionable options with tradeoffs and a Not Doing list.

Updated Mar 31, 2026

Search Tags:#scoping #brainstorming #feasibility #options #idea #brief #tradeoffs

Ready to run

npx skills add https://github.com/Saturate/agents --skill idea-refine-saturate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: idea-refine
Source: https://github.com/Saturate/agents/tree/main/skills/idea-refine
Command: npx skills add https://github.com/Saturate/agents --skill idea-refine-saturate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams transform vague ideas into concrete briefs by generating 3-5 options with tradeoffs, verifying feasibility, and clearly defining what is not in scope.

Core Features & Use Cases

Generate 3-5 distinct options with tradeoffs for a given idea.
Check technical feasibility and identify constraints early in the planning process.
Define a clear scope with a "Not Doing" list to prevent scope creep.
Use during brainstorming, refining an idea, scoping a feature, exploring options, or when starting something new without a clear spec.

Quick Start

Provide a vague idea and ask for 3-5 options with tradeoffs plus a Not Doing list to guide scope.

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 vague product idea into an actionable brief?▼

To turn a vague idea into an actionable brief, generate 3-5 concrete options with clear tradeoffs, verify feasibility, and define scope boundaries including a Not Doing list to prevent scope creep.

What is the best way to compare feature scoping options and tradeoffs?▼

Comparing feature scoping options requires evaluating 3-5 distinct approaches against each other to identify technical constraints, verify feasibility, and document tradeoffs for informed decision-making.

How can I prevent scope creep when starting a new project without a clear spec?▼

Preventing scope creep without a clear spec requires defining strict project boundaries by generating a structured brief that explicitly outlines a Not Doing list alongside feasible options.

When do I need to check technical feasibility during brainstorming?▼

You need to check technical feasibility during brainstorming when refining an idea to identify constraints early, ensuring selected options are viable before committing to detailed requirement definition.

Does this approach work for defining requirements across different project scales?▼

Yes, this approach works across various project scales because it standardizes requirement definition by applying feasibility checks and structured scope boundaries to any vague idea or feature.