flow-next-interview

Capture implementation details from Flow epic IDs, task IDs, or file paths through structured questions.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/tiendung/flow-next --skill flow-next-interview-tiendung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-next-interview
Source: https://github.com/tiendung/flow-next/tree/main/skills/flow-next-interview
Command: npx skills add https://github.com/tiendung/flow-next --skill flow-next-interview-tiendung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Flow interview skill solves the challenge of capturing comprehensive, unambiguous implementation details by guiding a thorough, multi-round questioning process. It ensures every relevant epic, task, or spec file is interrogated to elicit complete requirements, constraints, and acceptance criteria.

Core Features & Use Cases

  • Structured, deep questioning workflow that yields high-quality specs for Flow epics, tasks, and files.
  • Uses the AskUserQuestion tool to gather information and groups related questions to accelerate the interview.
  • Writes refined results back into Flow (epics/tasks) or updates target files, enabling seamless planning and execution.

Quick Start

Start the interview by invoking /flow-next:interview with a Flow ID or a file path to begin capturing and refining requirements.

Frequently Asked Questions about flow-next-interview

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

FAQPage Schema
How do I gather complete requirements for an epic or spec file?

Gather complete requirements by running a structured interview that asks grouped questions across multiple rounds, capturing implementation details and acceptance criteria to produce a refined spec.

What is structured requirements gathering and how does it refine specs?

Structured requirements gathering is a multi-round questioning process that elicits complete constraints and acceptance criteria, refining specs by interrogating epics or tasks to eliminate ambiguity and capture missing implementation details.

How do I start an interview with a Flow epic ID or task file path?

Start an interview by invoking the skill with a Flow epic ID, task ID, or file path, which identifies the target, asks grouped questions, and writes refined results directly back to Flow or the target file.

Does the requirements interview work with existing Flow tasks and files?

Yes, the requirements interview works with existing Flow tasks and files by accepting Flow epic IDs, task IDs, or file paths as input, interrogating the target across multiple rounds, and updating the source with refined specs.

What is the best way to capture unambiguous implementation details for epic planning?

The best way to capture unambiguous implementation details is a deep questioning workflow that groups related inquiries, ensuring every epic, task, or spec file is thoroughly interrogated to yield high-quality specs.

Why does spec refinement require multiple rounds of questions?

Spec refinement requires multiple rounds of questions to ensure comprehensive, unambiguous implementation details are captured, as single-pass interviews often miss constraints, so grouping related questions across rounds elicits complete requirements.