refine-plan

Deep interview for gathering requirements to refine the current plan (user)

⭐4stars🔀1forks📁View on GitHub🕐Updated Jan 3, 2026⬇️1downloads

When & Why to Use This Skill

The refine-plan skill automates the critical discovery and requirements-engineering phase of any project. By conducting an iterative, deep-probing interview, it helps users move beyond surface-level ideas to uncover hidden technical complexities, edge cases, and architectural tradeoffs, ensuring that the final plan is robust, scalable, and well-defined.

Use Cases

  • Technical Discovery: Use this skill at the start of a development cycle to identify performance bottlenecks, security implications, and integration points before writing a single line of code.
  • UI/UX Requirement Refinement: Deep-dive into user mental models, error recovery paths, and specific user flows to ensure the interface meets actual user needs and handles edge cases gracefully.
  • Risk Mitigation & Edge Case Analysis: Systematically explore 'what-if' scenarios and failure modes to build more resilient systems and avoid costly mid-project pivots.
  • Architectural Tradeoff Evaluation: Facilitate a structured discussion on the pros and cons of different technical approaches, focusing on long-term maintenance and scalability.
namerefine-plan
descriptionDeep interview for gathering requirements to refine the current plan (user)

Refine Plan

Conduct an in-depth interview to gather requirements using the AskUserQuestion tool.

Topics to Cover

  • Technical implementation details
  • UI & UX considerations
  • Concerns and edge cases
  • Tradeoffs and alternatives

Question Guidelines

Ask non-obvious, probing questions - not surface-level questions:

  • Edge cases, failure modes, and integration points
  • Non-obvious implications of design decisions
  • "What if" scenarios
  • Performance, scalability, and maintenance concerns
  • Assumptions that might be hiding complexity
  • User mental models and expectations
  • Error states and recovery paths
  • Security implications and attack surfaces
  • Data lifecycle and cleanup
  • UI/UX specifics and user flows
  • Tradeoffs between approaches

Interview Loop

  1. Ask 1-4 probing questions at a time using AskUserQuestion
  2. Incorporate answers into your understanding
  3. Repeat until you have comprehensive understanding
  4. Do NOT stop interviewing prematurely - thorough exploration is important

Important

  • Do NOT create any spec files or other files
  • Just conduct the interview and provide context
  • Let the caller decide what to do with the gathered information