spec-interview

Name: spec-interview
Availability: InStock
Author: sato-dev1234

Refine product specifications through structured ticket-based user interviews.

Updated Aug 27, 2026

Search Tags:#workflow #specification #requirements #interview #ticket #task-create #askuserquestion

Ready to run

npx skills add https://github.com/sato-dev1234/claude-code-sample --skill spec-interview-sato-dev1234

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-interview
Source: https://github.com/sato-dev1234/claude-code-sample/tree/main/skills/spec-interview
Command: npx skills add https://github.com/sato-dev1234/claude-code-sample --skill spec-interview-sato-dev1234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams refine product specifications by guiding a structured interview process that clarifies requirements and resolves ambiguities early.

Core Features & Use Cases

Guided interviewing prompts with AskUserQuestion to elicit technical requirements, UI/UX considerations, and potential edge cases.
Ticket-driven workflow: accepts a provided TICKET_ID or prompts the user to select a ticket and reads the relevant requirements.md to gather context.
End-to-end task orchestration: structures the interview steps, updates the ticket with refined requirements, regenerates knowledge references, and creates downstream tasks such as design work.

Quick Start

Start by providing a TICKET_ID or asking to list tickets to begin.

Frequently Asked Questions about spec-interview

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

FAQPage Schema

How do I refine product specifications through structured interviews?▼

Refining product specifications through structured interviews involves guided questioning to extract detailed technical, UI/UX, and risk requirements, updating the ticket with refined requirements, and creating downstream design tasks.

What is the best way to extract technical and UI/UX requirements from a ticket?▼

Extracting technical and UI/UX requirements from a ticket uses guided interviewing prompts to elicit details, reads the relevant requirements.md for context, and updates the ticket with the clarified specifications.

How do I start a requirements interview when I only have a ticket ID?▼

Starting a requirements interview with a ticket ID involves passing the identifier to the workflow, which reads the ticket's requirements.md to gather context and initiates structured questioning to resolve ambiguities.

Can I automate creating downstream design tasks after finalizing requirements?▼

Automating downstream design tasks after finalizing requirements is supported by the end-to-end task orchestration, which updates the ticket, regenerates knowledge references, and creates subsequent design work automatically.

Does guided questioning work for resolving edge cases in product workflows?▼

Guided questioning works for resolving edge cases in product workflows by systematically interviewing users to uncover potential risks and ambiguities early, ensuring the updated specifications cover all constraints.

What limitations exist when updating ticket requirements during an interview?▼

Updating ticket requirements during an interview operates strictly within a ticket-driven workflow, requiring a valid TICKET_ID or ticket selection to read the requirements.md and execute the specification refinement process.