skills.rest
izmailovilya
izmailovilyaCOMMUNITY
Explore all skills by this author →
GitHub

interviewed-team-feature

Coordinate an adaptive interview workflow and generate a feature brief.

41|10|Updated Jan 21, 2026
Search Tags:#automation#workflow#interview#adaptive#product-management#brief#team-feature
One-click install
npx skills add https://github.com/izmailovilya/ilia-izmailov-plugins --skill interviewed-team-feature
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interviewed-team-feature
Source: https://github.com/izmailovilya/ilia-izmailov-plugins/tree/main/plugins/agent-teams/skills/interviewed-team-feature
Command: npx skills add https://github.com/izmailovilya/ilia-izmailov-plugins --skill interviewed-team-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates an adaptive, short interview to capture user intent and business context, then compiles a precise feature brief and handoffs it to the /team-feature workflow.

Core Features & Use Cases

  • Adaptive interview: 2-6 questions to surface intent, goals, and constraints.
  • Phase-driven workflow: project study, question sequence, optional AI-generated follow-ups, and final brief compilation.
  • Handoff to /team-feature: saves the brief to the repository and triggers the build with no-research mode when appropriate.

Quick Start

Start the adaptive interview to capture intent and generate a ready-to-build feature brief.

Frequently Asked Questions about interviewed-team-feature

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

FAQPage Schema
How do I generate a feature brief from vague product ideas?▼

An adaptive interview captures vague product ideas through 2-6 targeted questions, surfacing intent and constraints, then compiles the responses into a ready-to-build feature brief for engineering handoff.

What is an adaptive interview workflow for product management?▼

An adaptive interview workflow automates product requirement gathering through phase-driven question sequences, optional AI follow-ups, and metadata generation, producing a structured .briefs file for team handoff.

How do I hand off a feature brief to engineering without extra research?▼

Save the compiled .briefs file to your repository and invoke the team-feature workflow with the no-research flag, triggering the build process directly without conducting additional upfront research cycles.

Can I use this workflow for both design and engineering projects?▼

Yes, this workflow supports product, design, and engineering projects by processing both vague and detailed user inputs, capturing business context, and generating feature briefs applicable across cross-functional teams.

What's the best way to capture business context before building a feature?▼

Use an adaptive interview to capture business context by answering 2-6 intent-focused questions, leveraging optional AI-generated follow-ups to extract goals and constraints, resulting in a structured .briefs file.

Related Skills

Explore More Product & Management Skills→
bketelsenbketelsen
1

create-prd

Generate a lightweight Product Requirements Document defining vision, user problems, and success metrics.

Community
Basic
ReidondReidond

product-brief

Create structured product briefs with UX copy and implementation notes.

Community
Advanced
Andy-HNUAndy-HNU

writing-specs-designs

Create technical specs, feature specs, and design briefs with YAML frontmatter.

Community
Intermediate
JohannesKoningsJohannesKonings
9

to-spec

Synthesize active conversation context into structured technical specifications and project requirements.

Community
Intermediate