Automated summary
Interviews the user in-depth to gather requirements and produce a detailed specification document.
Strengths
- Thorough coverage of technical, UX, security, and performance aspects.
- Iterative process with follow-up questions to resolve ambiguities.
- Delivers a structured SPEC.md ready for implementation.
Limitations
- Requires an available and patient user to answer many questions.
- Can be time-consuming for very complex or poorly defined projects.
- Does not replace real user validation (testing, prototypes).
Best at the start of a project or feature to clarify needs before coding.
Avoid for trivial tasks, simple bugs, or when requirements are already clear and documented.
Security analysis
SafeSkill only asks questions and writes a specification file; no execution of commands or access to sensitive resources.
No concerns found
How this analysis is madeExamples
I want to build a new login feature for our web app. Interview me to gather all requirements and write a spec.We're planning a checkout system for our e-commerce site. Please interview me in depth and create a specification document.I need to migrate our legacy database to a new schema. Interview me to capture all requirements, edge cases, and constraints for the migration plan.name: interview description: Interview user in-depth to create a detailed spec. Use when starting a new feature, project, or complex task that needs requirements gathering before implementation. argument-hint: [instructions] allowed-tools: AskUserQuestion, Write
Interview
Interview the user in-depth to create a detailed specification document.
Process
Follow the user instructions provided in <instructions> tags (if any) and interview the user about their requirements.
What to Ask About
- Technical implementation details
- UI and UX considerations
- Edge cases and error handling
- Tradeoffs and constraints
- Dependencies and integrations
- Performance requirements
- Security considerations
- Data models and schemas
- User workflows and journeys
- Acceptance criteria
How to Ask
- Use AskUserQuestion tool for each question
- Be very in-depth - do not ask obvious questions
- Follow up on answers to dig deeper
- Cover multiple angles of each topic
- Continue interviewing until requirements are complete
Interview Strategy
- Start with high-level goals and context
- Drill into specific features one by one
- Explore edge cases and failure modes
- Clarify ambiguities and assumptions
- Confirm understanding before moving on
When Complete
Write the spec to docs/SPEC.md (or the path specified in instructions).
The spec should include:
- Project/feature overview
- Detailed requirements
- Technical approach
- Data models (if applicable)
- UI/UX specifications (if applicable)
- Edge cases and error handling
- Open questions (if any remain)
<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/requirements-interview-mmbizjd1/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/requirements-interview-mmbizjd1' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/requirements-interview-mmbizjd1/download' --output '.skill-downloads/requirements-interview-mmbizjd1/SKILL.md.part' && mv '.skill-downloads/requirements-interview-mmbizjd1/SKILL.md.part' '.skill-downloads/requirements-interview-mmbizjd1/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.
Tools declared by the author (check availability in your agent): AskUserQuestion, Write
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
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/requirements-interview-mmbizjd1/SKILL.md' && test -s '.skill-downloads/requirements-interview-mmbizjd1/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/interview' && cp -R '.skill-downloads/requirements-interview-mmbizjd1' '.claude/skills/interview'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/requirements-interview-mmbizjd1'openskills read 'requirements-interview-mmbizjd1'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual 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/requirements-interview-mmbizjd1/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.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.