Automated summary
This skill conducts an in-depth interview with the user to produce a detailed specification.
Strengths
- Covers all project aspects (technical, UX, etc.)
- Asks non-obvious questions to avoid oversights
- Iterates until a complete document is achieved
Limitations
- Requires the user to have time to answer questions
- Can be lengthy for complex projects
Use this skill when you need to formalize a complex idea or a project that requires an exhaustive specification.
Do not use it for simple or already well-defined tasks, as the interview would be unnecessary.
Security analysis
SafeThe skill uses only AskUserQuestion and Write tools, which do not pose execution risks. It conducts interviews and writes spec files, with no destructive commands, exfiltration, or privilege escalation.
No concerns found
How this analysis is madeExamples
/interview Interview me to create a detailed specification for a new REST API for an e-commerce platform./interview Interview me in depth to design a database schema for a social media application./interview Help me specify the architecture and interfaces for a microservices-based system.create a skill /interview that does this Full prompt:
"""
argument-hint: [instructions] description: Interview user in-depth to create a detailed spec allowed-tools: AskUserQuestion, Write
Follow the user instructions and interview me in detail using the AskUserQuestionTool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. but make sure the questions are not obvious. be very in-depth and continue interviewing me continually until it's complete. then, write the spec to a file. <instructions>$ARGUMENTS</instructions>
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/in-depth-interview-for-specifications-mm5t8ain/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/in-depth-interview-for-specifications-mm5t8ain' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/in-depth-interview-for-specifications-mm5t8ain/download' --output '.skill-downloads/in-depth-interview-for-specifications-mm5t8ain/SKILL.md.part' && mv '.skill-downloads/in-depth-interview-for-specifications-mm5t8ain/SKILL.md.part' '.skill-downloads/in-depth-interview-for-specifications-mm5t8ain/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/in-depth-interview-for-specifications-mm5t8ain/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.