Our review
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
Examples
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>
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Pivot Decision Framework
Documentation
Documents a strategic pivot or persevere decision with evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.