flow-interview

Interview users to refine implementation specs with explicit next steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams need a complete, implementable specification but lack a precise starting point, this skill guides a thorough, staged inquiry to surface all requirements, constraints, and decisions.

Core Features & Use Cases

  • Conducts in-depth interviews to extract missing details and convert them into a refined spec.
  • Documents edge cases, acceptance criteria, and dependencies.
  • Works with both bead IDs and file paths to anchor the interview in existing artifacts.

Quick Start

Begin an interview to uncover all requirements and produce a concrete, actionable spec with next steps.

Frequently Asked Questions about flow-interview

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

FAQPage Schema
How do I turn a rough idea into a complete implementation spec?

To turn a rough idea into a complete implementation spec, you conduct an in-depth interview to extract missing details, constraints, and edge cases. This structured inquiry surfaces all requirements and converts them into a refined, actionable specification.

What is interview-driven design for requirements planning?

Interview-driven design for requirements planning is a staged inquiry process that identifies and refines implementation specs. It systematically uncovers undocumented edge cases, acceptance criteria, and dependencies to produce a structured actionable spec.

How do I refine requirements when I only have a basic concept?

You refine requirements when starting with a basic concept by applying a thorough, staged inquiry to surface all constraints and decisions. This fleshes out the initial concept into a precise implementation spec with explicit next steps.

Can I use existing artifacts like bead IDs or file paths to anchor the requirements interview?

Yes, you can anchor the requirements interview using existing artifacts by providing bead IDs or file paths. This grounds the inquiry in your current project context to ensure the refined spec aligns with existing documentation.

What is the best way to document edge cases and acceptance criteria for a new feature?

The best way to document edge cases and acceptance criteria for a new feature is through a structured interview that uncovers all constraints. This approach systematically records dependencies and decisions within a comprehensive implementation spec.