idea-refine

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

5|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/PHenrique07/Sementis-IFSP-Pirituba --skill idea-refine-phenrique07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: idea-refine
Source: https://github.com/PHenrique07/Sementis-IFSP-Pirituba/tree/main/.github/skills/idea-refine
Command: npx skills add https://github.com/PHenrique07/Sementis-IFSP-Pirituba --skill idea-refine-phenrique07

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Raw ideas often stay vague, untested, or over-scoped, leading teams to commit to plans built on hidden assumptions. This Skill turns fuzzy concepts into sharp, validated directions before any building begins. ## Core Features & Use Cases - Structured Three-Phase Ideation: 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 Surfacing: Explicitly names dealbreaker assumptions, what could kill the idea, and how to validate each risk before committing. - 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 confirmation. - Use Case: A founder with a vague startup concept invokes the skill, answers sharpening questions about target users and constraints, explores six variations, and walks away with a focused MVP plan and explicit trade-offs. ## Quick Start Ask the agent to help you refine your idea by describing the concept you want to ideate on or stress-test.

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 startup or product idea?▼

Invoke the skill with your raw idea and it restates it as a How Might We problem statement, asks 3-5 sharpening questions about users and constraints, then generates 5-8 variations using lenses like inversion, simplification, and audience shift before converging on a direction.

What is the output of an idea refinement session?▼

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

Can idea refinement work inside an existing codebase?▼

Yes. When run inside a project, the skill scans the codebase with Glob, Grep, and Read to ground idea variations in existing architecture, patterns, and constraints, referencing specific files when relevant.

How does the skill stress-test ideas before committing?▼

Each direction is evaluated against user value, feasibility, and differentiation using the refinement-criteria rubric. Hidden assumptions are explicitly named as dealbreakers, important, or nice-to-have, along with what could kill the idea.

When should I not use structured ideation?▼

Avoid it when the idea is already well-defined with validated assumptions and you just need execution planning. The skill is designed for vague concepts and pre-commitment stress-testing, not implementation task breakdown.