spec-interview

Interview SPEC.md files to surface edge cases and produce a final SPEC document.

Updated Feb 8, 2026

Search Tags:#documentation #specification #requirements #interview #edge-cases #tradeoffs #final-spec

Ready to run

npx skills add https://github.com/ckallum/calsuite --skill spec-interview-ckallum

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to perform a deep, structured interview to surface hidden decisions, edge cases, and tradeoffs within a spec document, then produce a comprehensive final SPEC.

Core Features & Use Cases

Conducts deep, multi-round interviews to surface non-obvious decisions and edge cases.
Transforms interview outcomes into a definitive final SPEC with clear decisions and open questions.
Works when a SPEC.md exists and needs fleshing out across complex domains.

Quick Start

Supply the SPEC.md file and initiate a multi-round interview to produce the final, fully fleshed specification.

Frequently Asked Questions about spec-interview

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

FAQPage Schema

How do I turn a vague specification into a complete final spec?▼

To turn a vague specification into a complete final spec, you can use a structured, multi-round interview process to surface hidden decisions, edge cases, and tradeoffs, producing a cohesive final SPEC document with clear rationale and next steps.

What is the best way to find edge cases in a SPEC.md file?▼

Finding edge cases in a SPEC.md file is best achieved through a deep, multi-round interview that systematically probes complex domains, forcing non-obvious decisions and tradeoffs to surface before finalizing the specification.

Can I work with multiple spec files during the requirements interview process?▼

Yes, the requirements interview process can handle single or multiple spec files, allowing you to flesh out complex features across different domains and consolidate them into one cohesive final SPEC document.

How do I document tradeoffs and unresolved questions in a specification?▼

To document tradeoffs and unresolved questions in a specification, conduct a structured interview to extract these elements, then transform the outcomes into a definitive final SPEC that explicitly records decisions, rationale, and open items.

When do I need a structured interview for specification documentation?▼

You need a structured interview for specification documentation when a SPEC.md exists but requires fleshing out across complex features or domains, ensuring all hidden decisions and edge cases are captured before development begins.