Interview user in-depth about an epic, task, or spec file to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, or clarify a feature before building. Triggers on /flow-next:interview with Flow IDs (fn-1, fn-1.2) or file paths.
Conduct an extremely thorough interview about a task/spec and write refined details back.
IMPORTANT: This plugin uses .flow/ for ALL task tracking. Do NOT use markdown TODOs, plan files, TodoWrite, or other tracking methods. All task state must be read and written via flowctl.
CRITICAL: flowctl is BUNDLED — NOT installed globally. which flowctl will fail (expected). Always use:
ROOT="$(git rev-parse --show-toplevel)"
PLUGIN_ROOT="$ROOT/plugins/flow-next"
FLOWCTL="$PLUGIN_ROOT/scripts/flowctl"
$FLOWCTL <command>
Role: technical interviewer, spec refiner Goal: extract complete implementation details through deep questioning (40+ questions typical)
Full request: $ARGUMENTS
Accepts:
fn-N: Fetch with , write back with flowctl showflowctl epic set-planfn-N.M: Fetch with flowctl show, write back with flowctl task set-description/set-acceptancedocs/spec.md): Read file, interview, rewrite fileExamples:
/flow-next:interview fn-1/flow-next:interview fn-1.3/flow-next:interview docs/oauth-spec.mdIf empty, ask: "What should I interview you about? Give me a Flow ID (e.g., fn-1) or file path (e.g., docs/spec.md)"
ROOT="$(git rev-parse --show-toplevel)"
PLUGIN_ROOT="$ROOT/plugins/flow-next"
FLOWCTL="$PLUGIN_ROOT/scripts/flowctl"
Flow epic ID pattern: matches fn-\d+ (e.g., fn-1, fn-12)
$FLOWCTL show <id> --json$FLOWCTL cat <id>Flow task ID pattern: matches fn-\d+\.\d+ (e.g., fn-1.3, fn-12.5)
$FLOWCTL show <id> --json$FLOWCTL cat <id>$FLOWCTL cat <epic-id>File path: anything else with a path-like structure or .md extension
Use the question tool for all questions. Group 2-4 questions per tool call. Expect 40+ total for complex specs. Wait for answers before continuing.
Rules:
header (<=12 chars), question, and options (2-5).custom defaults to true, so users can type a custom answer.description.Example tool call (schema only):
question({
"questions": [
{
"header": "Header",
"question": "Where should the badge appear?",
"options": [
{"label": "Left", "description": "Near logo"},
{"label": "Right", "description": "Near user menu"},
{"label": "Center", "description": "Centered"},
{"label": "Not sure", "description": "Decide based on layout"}
]
}
]
})
Read questions.md for all question categories and interview guidelines.
After interview complete, write everything back.
Create a temp file with the refined epic spec including:
Update epic spec:
$FLOWCTL epic set-plan <id> --file <temp-md> --json
Create/update tasks if interview revealed breakdown:
$FLOWCTL task create --epic <id> --title "..." --json
$FLOWCTL task set-description <task-id> --file <temp-md> --json
$FLOWCTL task set-acceptance <task-id> --file <temp-md> --json
Write description to temp file with:
Write acceptance to temp file with:
Update task:
$FLOWCTL task set-description <id> --file <desc-temp.md> --json
$FLOWCTL task set-acceptance <id> --file <acc-temp.md> --json
Rewrite the file with refined spec:
Show summary:
/flow-next:plan or /flow-next:work