flow-next-interview
Facilitates technical interviews to document feature requirements using flowctl for state management.
Install
mkdir -p .claude/skills/flow-next-interview && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8214" && unzip -o skill.zip -d .claude/skills/flow-next-interview && rm skill.zipInstalls to .claude/skills/flow-next-interview
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Interview user in-depth about a spec, 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-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2) or file paths.Key capabilities
- →Conducts guided interviews to gather technical specifications
- →Validates requirement completeness through iterative questioning
- →Tracks task state via local.flow/ files
- →Auto-generates acceptance criteria from user responses
How it works
Runs an interactive prompt loop to extract implementation details, writing results to local storage using the bundled flowctl script.
Inputs & outputs
When to use flow-next-interview
- →Refining feature specifications
- →Clarifying technical requirements
- →Drafting task implementation plans
About flow-next-interview
Acts as a technical interviewer to help users flesh out requirements for new features or tasks. It stores state exclusively using flowctl, ensuring all implementation details are documented and tracked.
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-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2) or file paths.
When not to use it
- →When the task is already fully defined and documented
- →For simple one-off code fixes that do not require tracking
Prerequisites
Limitations
- →Strictly relies on the bundled flowctl tool, which cannot be installed globally
- →High degree of user interaction required for long-form interviews
How it compares
It enforces structured state tracking via a dedicated CLI tool rather than ad-hoc document editing.
Compared to similar skills
flow-next-interview side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| flow-next-interview (this skill) | 0 | 3mo | Review | Intermediate |
| create-plan | 36 | 9mo | Review | Beginner |
| project-planner | 32 | 11mo | Review | Intermediate |
| system-design | 19 | 10mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by gmickel
View all by gmickel →You might also like
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
sparc-methodology
ruvnet
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
spec-workflow
TencentCloudBase
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.