spec-interview

Interview spec authors to resolve ambiguities and gaps in specification files.

5|2|Updated Jan 16, 2012

Search Tags:#documentation #software development #specification #product management #interview #requirements gathering

Ready to run

npx skills add https://github.com/asonas/dotfiles --skill spec-interview-asonas

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the ambiguity and incompleteness often found in technical specification documents, ensuring clarity before implementation begins.

Core Features & Use Cases

Ambiguity Detection: Identifies gaps, inconsistencies, and missing details in spec files.
Iterative Interviewing: Conducts multi-round Q&A sessions with the spec author to resolve all uncertainties.
Use Case: A product manager has drafted a new feature spec. This Skill will meticulously review it, ask the PM detailed questions about every aspect (data models, error handling, edge cases, etc.), and update the spec iteratively until it's ready for engineering.

Quick Start

Use the spec-interview skill to refine the specification document located at '/path/to/feature_spec.md'.

Frequently Asked Questions about spec-interview

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

FAQPage Schema

How do I identify ambiguities and gaps in a software specification document?▼

An exhaustive specification interview systematically reviews data models, architecture, security, and scope through iterative questioning to detect ambiguities and gaps in a spec file before implementation begins.

What is the best way to refine product requirements before handing a spec to engineering?▼

The best way to refine product requirements is conducting an iterative Q&A session with the spec author to meticulously review edge cases, error handling, and integration points, updating the spec until it requires no further clarification.

Does this specification interview process automatically update the spec file?▼

Yes, the specification interview process can read and edit the spec file iteratively, using bash commands and web searches to resolve missing details, ensuring the final document is complete enough for implementation without further clarification.

Can I use this approach to review all technical aspects of a feature specification?▼

Yes, you can use this approach to review all technical aspects of a feature specification, as it systematically evaluates data models, architecture, behavior, integration, security, operations, and scope to ensure comprehensive coverage.

When do I need an iterative interview process for my documentation?▼

You need an iterative interview process for your documentation when a specification contains ambiguities or missing details, requiring multi-round Q&A to thoroughly resolve edge cases and error handling before development starts.

What are the limitations of using an automated interview to refine requirements?▼

A limitation of using an automated interview is that it requires active participation from the spec author to answer detailed questions across multiple rounds, meaning it cannot independently invent missing domain logic or make product decisions on its own.