How many questions does Flow Interview typically ask?

For complex features, the skill is designed to be extremely thorough, often asking over 40 questions to ensure no edge case or dependency is missed.

Does it work with local documentation files?

Absolutely. You can point it to a file path like docs/spec.md, and it will read the contents, interview you, and then rewrite the file with refined, actionable details.

How do I trigger the interview process?

You can use commands like '/flow:interview', 'interview me', or 'flesh out this spec' followed by a file path or task ID.

What does the Flow Interview skill do?

It conducts a thorough technical interview to help you flesh out specs, refine requirements, and clarify feature details before you begin the implementation phase.

Can it update my project management tools?

Yes, it integrates with 'beads' IDs to fetch and update task descriptions, create subtasks, and manage dependencies directly from the Claude Code interface.

Flow Interview

Name: Flow Interview
Author: gmickel

bygmickel

•

356

Productivity & Workflow

Conducts deep technical interviews to extract exhaustive implementation details and refine feature specifications before coding.

About

Flow Interview is a high-rigor requirement gathering skill for Claude Code that acts as a technical interviewer and spec refiner. It prevents development drift and architectural errors by subjecting new feature ideas or vague specifications to intense questioning—often exceeding 40 queries—to uncover edge cases, technical dependencies, and precise acceptance criteria. By integrating directly with local markdown files or task management systems via the 'beads' protocol, it automatically updates your documentation or project board with refined, actionable implementation plans.

Key Features

Direct integration with 'beads' task management for updating epics and subtasks
356 GitHub stars
Automated specification rewriting for local markdown files
Automatic dependency mapping and acceptance criteria generation
Deep questioning engine that asks 40+ targeted technical questions
Structured data extraction using the AskUserQuestion tool for clean interactions

Use Cases

Fleshing out a vague feature idea into a production-ready technical specification
Decomposing high-level epics into granular, actionable subtasks with clear dependencies
Refining complex task requirements before starting an autonomous coding session

About

Key Features

Direct integration with 'beads' task management for updating epics and subtasks
356 GitHub stars
Automated specification rewriting for local markdown files
Automatic dependency mapping and acceptance criteria generation
Deep questioning engine that asks 40+ targeted technical questions
Structured data extraction using the AskUserQuestion tool for clean interactions

Use Cases

Fleshing out a vague feature idea into a production-ready technical specification
Decomposing high-level epics into granular, actionable subtasks with clear dependencies
Refining complex task requirements before starting an autonomous coding session