CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/spec-driven-development

Spec-driven workflow covering requirement gathering, spec authoring, implementation review, and verification — with skills, rules, and evaluation scenarios.

96

1.19x
Quality

90%

Does it follow best practices?

Impact

98%

1.19x

Average score across 9 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-3/

Requirements Interview: Webhook System

Problem Description

A startup is building a webhook delivery system. The CTO has described the feature:

"We need webhooks. When things happen in our system — like a user signs up or a payment succeeds — we should be able to notify external URLs. Customers configure their webhook URLs in the dashboard."

The engineering team needs to prepare their requirements interview. They have no existing specs for this feature.

Your task is to produce the interview preparation document the team will use when they sit down with the CTO. This is preparation only — you are NOT conducting the interview.

Output Specification

Produce a file named webhook-interview-prep.md containing:

  1. Scope assessment — what's reasonably in scope based on the CTO's description, and what's unclear
  2. Gap list — numbered list of every ambiguous or unspecified area
  3. Interview questions — an ordered sequence of questions, ONE per item, that the team should ask. Each question must be self-contained (not "follow-up to Q3"). Order them from most critical (scope/core behavior) to least critical (edge cases/nice-to-haves).

Constraints

  • Do NOT write a spec — this is pre-interview preparation
  • Do NOT propose technical solutions or architecture
  • Do NOT create any source code files

README.md

tile.json