groom

Clarify early-stage product ideas through Socratic fork-point questions.

3|Updated May 11, 2026
One-click install
npx skills add https://github.com/nadyshalaby/hackify --skill groom-nadyshalaby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: groom
Source: https://github.com/nadyshalaby/hackify/tree/main/skills/groom
Command: npx skills add https://github.com/nadyshalaby/hackify --skill groom-nadyshalaby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Groom helps turn an early, uncertain idea into a clear build direction before any work-doc is created. It is designed for moments when the user wants to explore possibilities, tradeoffs, and scope rather than jump straight into implementation.

Core Features & Use Cases

  • Socratic idea refinement: Runs an interactive conversation with 1 or 2 fork-point questions per turn to uncover the real decision behind the request.
  • Reflection-first guidance: Mirrors the user's last message before asking the next question, keeping the conversation aligned and reducing misreads.
  • Build-intent graduation: Detects when the user is ready to move from exploration to execution, then distills the discussion and hands off to the main hackify workflow.
  • Use case: A user says they are "thinking about" a feature but are unsure about scope, tradeoffs, or implementation path; groom helps clarify the direction before planning starts.

Quick Start

Ask groom to help explore the idea and clarify the key fork in the decision before moving into build mode.

Frequently Asked Questions about groom

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

FAQPage Schema
How do I refine early-stage product ideas before starting development?

To refine early-stage product ideas, you can use a Socratic conversation workflow that surfaces the real decision forks in your scope before implementation begins. It mirrors your input and asks targeted questions to clarify tradeoffs and fluid requirements.

What is the best way to explore scope and tradeoffs for an uncertain feature request?

Exploring scope and tradeoffs for an uncertain feature requires reflection-first questioning that uncovers the core decision before building. Interactive idea refinement helps distill open-ended prompts into a clear build direction by limiting questions to one or two per turn.

How does idea refinement transition into actual software build execution?

Idea refinement transitions into software build execution through build-intent graduation, which detects when you are ready to move from exploration to implementation. It then distills the discussion and hands off the clarified scope to the main workflow.

Can I use this Socratic workflow for open-ended prompts where requirements are still fluid?

Yes, you can use this Socratic workflow for open-ended prompts where requirements are still fluid. It is specifically designed for pre-build scope exploration and tradeoff discussions, applying limited question counts per turn to prevent overwhelming the user.

When should I not use pre-build scope discovery for product planning?

You should not use pre-build scope discovery when your build intent is already clear and requirements are fixed. If your product direction is solidified and does not require exploring possibilities or tradeoffs, you can skip idea refinement and proceed directly to the main workflow.