skills.rest
Emrebener
EmrebenerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ss-sdd-discovering-requirements

Guides four-phase interactive requirement discovery for SDD pipeline runs.

Updated May 19, 2026
Search Tags:#specification#pipeline orchestration#sd d#requirements discovery#coverage checklist#interactive interviews#adr candidates
One-click install
npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-sdd-discovering-requirements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ss-sdd-discovering-requirements
Source: https://github.com/Emrebener/Sublime-Skills/tree/main/skills/spec-driven-development/ss-sdd-discovering-requirements
Command: npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-sdd-discovering-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ss-sdd-discovering-requirements helps you turn a rough idea into a shared, complete understanding of what to build—without jumping to specs too early or writing any artifacts during discovery.

Core Features & Use Cases

  • Four-phase interactive discovery that walks from context to framing probes, then through a coverage checklist, and finally into a structured synthesis for the coordinator.
  • Strict safety gates that prevent skipping framing probes, advancing before approvals, or proceeding with missing coverage answers.
  • Structured end-of-stage summary produced for the coordinator, while ensuring no files are written to disk in this stage.

Quick Start

Use the ss-sdd-discovering-requirements skill during your SDD pipeline discovery stage after ss-sdd-preflight and before ss-sdd-writing-specs to align your team on the exact requirements to spec next.

Frequently Asked Questions about ss-sdd-discovering-requirements

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

FAQPage Schema
How do I conduct interactive interviews for requirements discovery in software engineering?▼

Interactive interviews for requirements discovery are conducted through a four-phase conversation that walks from context to framing probes, then a coverage checklist, and finally a coordinator-ready summary.

What is requirements discovery for SDD pipeline orchestration and when do I need it?▼

Requirements discovery for SDD pipeline orchestration is a structured alignment process needed before spec writing to ensure consistent framing and dimension-by-dimension coverage for feature or fix planning.

How do I structure requirements alignment before writing specifications?▼

Structure requirements alignment before writing specifications by gating interactive approvals across purpose, users, scope, success, entities, edge cases, constraints, and integration dimensions.

Can I use SDD discovery to generate coverage checklists without writing files to disk?▼

Yes, SDD discovery generates a structured end-of-stage summary for the coordinator while strictly ensuring no files are written to disk during the discovery stage.

What are the limitations of conversational requirements discovery in pipeline orchestration?▼

Conversational requirements discovery is limited by strict constraints: one question per message, no on-disk artifacts, gating against unapproved sections, and mandatory stated answers across all coverage dimensions.

Related Skills

Explore More Software Engineering Skills→
amdamd
154

quark-env-preflight

Collect OS, Python, GPU, and accelerator facts for Quark installation readiness.

Official
Intermediate
aaronbassettaaronbassett
4

spec-writer:specs-workflow

Generate implementation-ready feature specifications with structured SPEC.md files.

Community
Advanced
AustinZ21AustinZ21
4

speckit-implement

Execute spec-kit implementation task plans with dependency and checklist validation.

Community
Advanced
thepriceisrightthepriceisright

prd

Generate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.

Community
Advanced