skills.rest
ClipboardHealth
ClipboardHealthOFFICIAL
Explore all skills by this author →
Website𝕏@ClipboardEngGitHub

interview-feature

Guide iterative requirement interviews and automated research to produce detailed feature tickets.

66|9|Updated Aug 5, 2024
Search Tags:#research#interview#requirement gathering#feature clarification#ticket writing
One-click install
npx skills add https://github.com/ClipboardHealth/core-utils --skill interview-feature
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-feature
Source: https://github.com/ClipboardHealth/core-utils/tree/main/plugins/core/skills/interview-feature
Command: npx skills add https://github.com/ClipboardHealth/core-utils --skill interview-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams accurately understand feature requirements by guiding interviews, research, and clarification, reducing misunderstandings and scope creep.

Core Features & Use Cases

  • Interactive interview guidance: Follows a structured loop to assess knowledge gaps and ask targeted questions.
  • Research dispatching: Automatically conducts codebase, monitoring, and data research to gather relevant information before questioning the user.
  • Use Case: A product manager needs to write a detailed feature ticket; this Skill ensures comprehensive understanding by combining user input with automated research, leading to well-structured tickets.

Quick Start

Ask the skill to clarify a feature requirement before writing a ticket.

Frequently Asked Questions about interview-feature

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

FAQPage Schema
How do I clarify feature requirements before writing a product ticket?▼

Feature requirement clarification uses guided interviews and automated research to identify knowledge gaps, ensuring product teams produce detailed and accurate tickets while reducing misunderstandings and scope creep.

What is the best way to gather requirements for a new product feature?▼

Gathering requirements for a new product feature is best handled by combining structured questioning with automated codebase and data research, which helps teams articulate detailed needs and produce accurate tickets.

How does automated research help with requirement gathering for engineering teams?▼

Automated research helps with requirement gathering by dispatching queries across codebases, monitoring, and data sources to collect relevant information before questioning users, ensuring accurate feature documentation.

Can I use this for requirement articulation across product and design teams?▼

Yes, you can use this for requirement articulation across product, engineering, and design teams, as it applies structured questioning and documentation to ensure clarity and completeness for feature development.

How do I stop scope creep when defining feature requirements?▼

To stop scope creep when defining feature requirements, this Skill applies iterative requirement gathering and targeted clarification questions, reducing misunderstandings by ensuring all details are accurately documented.

Related Skills

Explore More Product & Management Skills→
trevorbyrumtrevorbyrum
1

project-questions

Interview users to define project scope, assumptions, and constraints.

Community
Intermediate
Olino3Olino3
1

sprint

Break a ROADMAP phase into granular tickets and create sprint artifacts.

Community
Intermediate
Clouder0Clouder0

error-recovery

Handle subagent failures with retry strategies and escalation patterns.

Community
Advanced
ROU-TechnologyROU-Technology

angular-forms

Automate reactive Angular form construction with Signal Forms for v21+ projects.

Official
Intermediate