interview

To elicit clear requirements, this Skill conducts a structured interview asking targeted questions in batches to surface edge cases and acceptance criteria. It transforms vague feature ideas into a documented discovery brief before development begins.

The best way to gather testable acceptance criteria is through a structured stakeholder interview. This Skill guides the process by asking focused questions and summarizing learnings to produce a formal discovery brief with clear constraints and criteria.

You create a discovery brief by running a structured interview process that captures problem statements, users, inputs, outputs, integrations, and open questions. The resulting document is saved directly to docs/specs/<feature-slug>/brief.md.

Yes, you can use a structured interview to document problem statements and integrations. This Skill systematically guides the conversation to capture all necessary technical and business details into a comprehensive markdown brief.

Yes, this requirements discovery process works effectively for complex startup concepts. It applies targeted questioning batches to clarify scale, identify missing edge cases, and produce a concrete feature brief for development teams.